Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] j: broken: binaries missing
@ 2020-02-06 17:02 voidlinux-github
  2020-02-06 23:05 ` voidlinux-github
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: voidlinux-github @ 2020-02-06 17:02 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 254 bytes --]

New issue by leahneukirchen on void-packages repository

https://github.com/void-linux/void-packages/issues/18857

Description:
j-901.e_2 does not contain the j binaries!

```
% xls j |grep lib
/usr/share/j/system/main/stdlib.ijs
```

@xelxebar 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: j: broken: binaries missing
  2020-02-06 17:02 [ISSUE] j: broken: binaries missing voidlinux-github
@ 2020-02-06 23:05 ` voidlinux-github
  2020-02-13 19:22 ` voidlinux-github
  2020-02-13 19:22 ` [ISSUE] [CLOSED] " voidlinux-github
  2 siblings, 0 replies; 4+ messages in thread
From: voidlinux-github @ 2020-02-06 23:05 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

New comment by xelxebar on void-packages repository

https://github.com/void-linux/void-packages/issues/18857#issuecomment-583154770

Comment:
That's bad. `xbps-query -Rf j | grep lib` gives me the same; however, nuking <hostdir>/binpkgs and rebuilding locally, this is what I see and what we want in the repo:

```
$ xls j | grep lib
/usr/lib/j/j64/jconsole
/usr/lib/j/j64/libj.so
/usr/lib/j/j64avx/jconsole
/usr/lib/j/j64avx/libj.so
/usr/lib/j/j64avx2/jconsole
/usr/lib/j/j64avx2/libj.so
/usr/share/j/system/main/stdlib.ijs
```

 I do vaguely remembered that the build scripts exit without error if given the wrong parameters. Setting `jplatform=foo j64x=bar' confirms this.

My guess is that, on the machine/cluster that builds for the main repo, the `do_build` is degrading to a noop. `/usr/lib/j` gets populated from `<wrksrc>/bin`, the latter being where the build outputs reside. This would create an empty `/usr/lib/j` which ends up getting elided in the final packaging phase.

That said, are the build logs still hanging around? Grepping for `no case for those parameters` would confirm the above hypothesis.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: j: broken: binaries missing
  2020-02-06 17:02 [ISSUE] j: broken: binaries missing voidlinux-github
  2020-02-06 23:05 ` voidlinux-github
@ 2020-02-13 19:22 ` voidlinux-github
  2020-02-13 19:22 ` [ISSUE] [CLOSED] " voidlinux-github
  2 siblings, 0 replies; 4+ messages in thread
From: voidlinux-github @ 2020-02-13 19:22 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 156 bytes --]

New comment by leahneukirchen on void-packages repository

https://github.com/void-linux/void-packages/issues/18857#issuecomment-585928655

Comment:
Fixed.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [ISSUE] [CLOSED] j: broken: binaries missing
  2020-02-06 17:02 [ISSUE] j: broken: binaries missing voidlinux-github
  2020-02-06 23:05 ` voidlinux-github
  2020-02-13 19:22 ` voidlinux-github
@ 2020-02-13 19:22 ` voidlinux-github
  2 siblings, 0 replies; 4+ messages in thread
From: voidlinux-github @ 2020-02-13 19:22 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 257 bytes --]

Closed issue by leahneukirchen on void-packages repository

https://github.com/void-linux/void-packages/issues/18857

Description:
j-901.e_2 does not contain the j binaries!

```
% xls j |grep lib
/usr/share/j/system/main/stdlib.ijs
```

@xelxebar 

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-02-13 19:22 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-06 17:02 [ISSUE] j: broken: binaries missing voidlinux-github
2020-02-06 23:05 ` voidlinux-github
2020-02-13 19:22 ` voidlinux-github
2020-02-13 19:22 ` [ISSUE] [CLOSED] " voidlinux-github

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).