Re: [gentoo-user] Systemd-boot not compiling

2019-04-09 Thread Peter Humphrey
On Tuesday, 9 April 2019 17:36:04 BST Mike Gilbert wrote:

> The above log snippet is fairly useless. In the future, please make
> sure to include the relevant log snippet, or attach/pastebin the
> entire build log if in doubt.

I had all the logs etc ready to send; I wanted first to see if it was a common 
problem or just mine.

> The most important part of the log on bug 682908 was this:
> 
> Call stack:
>  ebuild.sh, line 124:  Called src_compile
>environment, line 2145:  Called die
>  The specific snippet of code:
>   patchelf --remove-rpath bootctl || die
> 
> That tells me that the patchelf call in src_compile was failing and
> gives a much better starting point than some cryptic "stat" error.

Indeed, but I didn't get that in my log. I'd have come to the same conclusion 
if I had.

-- 
Regards,
Peter.






Re: [gentoo-user] Systemd-boot not compiling

2019-04-09 Thread Mike Gilbert
On Mon, Apr 8, 2019 at 9:14 AM Peter Humphrey  wrote:
>
> Hello list,
>
> Is anyone else having trouble emerging systemd-boot-241? This machine has a
> small rescue system as an alternative boot, and I get a mysterious error when
> I emerge the package. The end of the log shows this:
>
> [248/248] x86_64-pc-linux-gnu-gcc  -o bootctl 'bootctl@exe/
> src_boot_bootctl.c.o' -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro -Wl,-
> z,now -Wl,--gc-sections -O2 -march=haswell -pipe -Wl,-O1 -Wl,--as-needed -
> Wl,--start-group src/shared/libsystemd-shared-241.a src/libsystemd/
> libsystemd_static.a src/basic/libbasic.a /usr/lib64/libblkid.so -lrt /usr/
> lib64/libcap.so /usr/lib64/libmount.so -lrt -lm -Wl,--end-group -pthread '-
> Wl,-rpath,$ORIGIN/src/shared:$ORIGIN/src/libsystemd:$ORIGIN/src/basic' -Wl,-
> rpath-link,/var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-boot-241-
> build/src/shared:/var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-
> boot-241-build/src/libsystemd:/var/tmp/portage/sys-boot/systemd-boot-241/work/
> systemd-boot-241-build/src/basic
> stat: No such file or directory
>  * ERROR: sys-boot/systemd-boot-241::gentoo failed (compile phase):
>  *   (no error message)
>
> But it compiles just fine on the main system.
>
> Perhaps something is missing from the rescue system and hasn't been caught by
> the ebuild, but I can't think of what. If 'stat' had said what file or
> directory wasn't present, I'd be able to dig a bit deeper to find the problem.
>
> I see the same behaviour on another machine. Both are 64-bit, but only this
> one is ~amd64; the other one has a KEYWORD to enable systemd-boot.

The above log snippet is fairly useless. In the future, please make
sure to include the relevant log snippet, or attach/pastebin the
entire build log if in doubt.

The most important part of the log on bug 682908 was this:

Call stack:
 ebuild.sh, line 124:  Called src_compile
   environment, line 2145:  Called die
 The specific snippet of code:
  patchelf --remove-rpath bootctl || die

That tells me that the patchelf call in src_compile was failing and
gives a much better starting point than some cryptic "stat" error.



Re: [gentoo-user] Systemd-boot not compiling

2019-04-09 Thread Peter Humphrey
On Tuesday, 9 April 2019 14:34:19 BST J. Roeleveld wrote:
> On Tuesday, April 9, 2019 11:11:42 AM CEST Peter Humphrey wrote:
> > On Tuesday, 9 April 2019 06:56:02 BST J. Roeleveld wrote:
> > > if you search for "stat" in the build-log and/or makefile(s), does it
> > > show
> > > which file(s) it is checking?
> > 
> > Looking into the work directory I find this little surprise:
> > 
> > # ls -l
> > /var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-boot-241-build
> > [...]
> > lrwxrwxrwx  1 portage portage   22 Apr  9 09:26 libnss_myhostname.so ->
> > libnss_myhostname.so.2 lrwxrwxrwx  1 portage portage   22 Apr  9 09:26
> > libnss_mymachines.so -> libnss_mymachines.so.2 lrwxrwxrwx  1 portage
> > portage   19 Apr  9 09:26 libnss_resolve.so -> libnss_resolve.so.2
> > lrwxrwxrwx  1 portage portage   19 Apr  9 09:26 libnss_systemd.so ->
> > libnss_systemd.so.2 lrwxrwxrwx  1 portage portage   15 Apr  9 09:26
> > libsystemd.so -> libsystemd.so.0 lrwxrwxrwx  1 portage portage   20 Apr  9
> > 09:26 libsystemd.so.0 -> libsystemd.so.0.25.0 [...]
> > 
> > Konsole shows all these in red, indicating nonexistence of the links'
> > targets, and indeed they don't exist, either there or anywhere else in the
> > system. On the other hand, after ebuild ... compile on the main system,
> > which succeeds, I get the same nonexistent links. So that can't be the
> > problem.
> > 
> > "find . -name Makefile -exec grep '-lw' 'stat' {} +" returns a blank.
> > 
> > I'm close to getting out of my depth here.
> > 
> > (This is an openrc box.)
> 
> I just tested the compile on my system and I get the exact same error.
> This is on my primary desktop, so would expect most build-dependencies to be
> present.
> 
> I also noticed the following bug on b.g.o.:
> https://bugs.gentoo.org/682908

Ah. That must have been posted after I looked.

> For your current issue, you could try version 239, which does compile on my
> system. I am not going to test installing it as that risks not being able to
> boot my desktop.

Yes, 239 is fine here too. I'll leave the boxes that can compile 241 alone for 
the time being.

Thanks for your help.

-- 
Regards,
Peter.






Re: [gentoo-user] Systemd-boot not compiling

2019-04-09 Thread J. Roeleveld
On Tuesday, April 9, 2019 11:11:42 AM CEST Peter Humphrey wrote:
> On Tuesday, 9 April 2019 06:56:02 BST J. Roeleveld wrote:
> > if you search for "stat" in the build-log and/or makefile(s), does it show
> > which file(s) it is checking?
> 
> Looking into the work directory I find this little surprise:
> 
> # ls -l
> /var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-boot-241-build
> [...]
> lrwxrwxrwx  1 portage portage   22 Apr  9 09:26 libnss_myhostname.so ->
> libnss_myhostname.so.2 lrwxrwxrwx  1 portage portage   22 Apr  9 09:26
> libnss_mymachines.so -> libnss_mymachines.so.2 lrwxrwxrwx  1 portage
> portage   19 Apr  9 09:26 libnss_resolve.so -> libnss_resolve.so.2
> lrwxrwxrwx  1 portage portage   19 Apr  9 09:26 libnss_systemd.so ->
> libnss_systemd.so.2 lrwxrwxrwx  1 portage portage   15 Apr  9 09:26
> libsystemd.so -> libsystemd.so.0 lrwxrwxrwx  1 portage portage   20 Apr  9
> 09:26 libsystemd.so.0 -> libsystemd.so.0.25.0 [...]
> 
> Konsole shows all these in red, indicating nonexistence of the links'
> targets, and indeed they don't exist, either there or anywhere else in the
> system. On the other hand, after ebuild ... compile on the main system,
> which succeeds, I get the same nonexistent links. So that can't be the
> problem.
> 
> "find . -name Makefile -exec grep '-lw' 'stat' {} +" returns a blank.
> 
> I'm close to getting out of my depth here.
> 
> (This is an openrc box.)

I just tested the compile on my system and I get the exact same error.
This is on my primary desktop, so would expect most build-dependencies to be 
present.

I also noticed the following bug on b.g.o.:
https://bugs.gentoo.org/682908

For your current issue, you could try version 239, which does compile on my 
system. I am not going to test installing it as that risks not being able to 
boot my desktop.

--
Joost





Re: [gentoo-user] Systemd-boot not compiling

2019-04-09 Thread Peter Humphrey
On Tuesday, 9 April 2019 06:56:02 BST J. Roeleveld wrote:

> if you search for "stat" in the build-log and/or makefile(s), does it show
> which file(s) it is checking?

Looking into the work directory I find this little surprise:

# ls -l /var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-boot-241-build
[...]
lrwxrwxrwx  1 portage portage   22 Apr  9 09:26 libnss_myhostname.so -> 
libnss_myhostname.so.2
lrwxrwxrwx  1 portage portage   22 Apr  9 09:26 libnss_mymachines.so -> 
libnss_mymachines.so.2
lrwxrwxrwx  1 portage portage   19 Apr  9 09:26 libnss_resolve.so -> 
libnss_resolve.so.2
lrwxrwxrwx  1 portage portage   19 Apr  9 09:26 libnss_systemd.so -> 
libnss_systemd.so.2
lrwxrwxrwx  1 portage portage   15 Apr  9 09:26 libsystemd.so -> libsystemd.so.0
lrwxrwxrwx  1 portage portage   20 Apr  9 09:26 libsystemd.so.0 -> 
libsystemd.so.0.25.0
[...]

Konsole shows all these in red, indicating nonexistence of the links' targets,
and indeed they don't exist, either there or anywhere else in the system. On
the other hand, after ebuild ... compile on the main system, which succeeds, I
get the same nonexistent links. So that can't be the problem.

"find . -name Makefile -exec grep '-lw' 'stat' {} +" returns a blank.

I'm close to getting out of my depth here.

(This is an openrc box.)

-- 
Regards,
Peter.






Re: [gentoo-user] Systemd-boot not compiling

2019-04-09 Thread Peter Humphrey
On Tuesday, 9 April 2019 06:56:02 BST J. Roeleveld wrote:

> if you search for "stat" in the build-log and/or makefile(s), does it show
> which file(s) it is checking?

The log has four occurrences of "stat". The first is during the initial 
checks: Program stat found: YES (/usr/bin/stat)

Line 148 appears to be x86_64-pc-linux-gnu-gcc compiling ../systemd-241/src/
basic/stat-util.c

Line 167 shows x86_64-pc-linux-gnu-ar csrD src/basic/libbasic.a with a list of 
about 80 .o files.

Then the last line, 248, is followed immediately by the error message "stat: 
No such file or directory".

I don't have the source files at the moment; I'll look into those when I can.

-- 
Regards,
Peter.