Re: Still true at -r333575 : head -r320458 (e.g.) amd64 -> powerpc64 cross build's install32 during installworld: /usr/src/share/mk/bsd.linker.mk tried to use "head" when PATH provided no access (head is missing)

Bryan Drewery <[email protected]> Mon, 14 May 2018 17:04:54 -0700

Newsgroups	gmane.os.freebsd.devel.toolchain,gmane.os.freebsd.devel.ppc
Organization	FreeBSD
Message-ID	<[email protected]>

On 5/13/2018 1:13 AM, Mark Millard wrote:
> Retrying the amd64 -> powerpc64 cross build via a powerpc64-gcc
> this time, combined with WITH_LIB32= , got: "sh: head: not found" and its
> later consequences, like before for installworld (to a directory on the
> amd64 host context). This is from the /usr/src/share/mk/bsd.linker.mk line
> that results in:
> 
> (/usr/local/powerpc64-freebsd/bin/ld --version || echo none) | head -n 1
> 
> but head is not available by default at the time (lib32 context). (I make
> head be available via using LOCAL_ITOOLS=head in order to work around the
> issue.)
> 
> An example of the messages (without having LOCAL_ITOOLS=head) is:
> 
> --- _installlinks ---
> install -l s  ../../libexec/ld-elf32.so.1 /usr/obj/DESTDIRs/xtcgcc-powerpc64-installworld/usr/libexec/ld-elf32.so.1
> cd /usr/src/usr.bin/ldd; PROG=ldd32 . . .
> . . .
> . . . MAKEOBJDIRPREFIX= MK_MAN=no MK_HTML=no  MK_TOOLCHAIN=no   -DLIBRARIES_ONLY  install
> sh: head: not found
> make[4]: "/usr/src/share/mk/bsd.linker.mk" line 47: warning: "(/usr/local/powerpc64-unknown-freebsd12.0/bin/ld --version || echo none) | head -n 1" returned non-zero status
> make[4]: "/usr/src/share/mk/bsd.linker.mk" line 58: warning: Unknown linker from XLD=/usr/local/powerpc64-unknown-freebsd12.0/bin/ld: , defaulting to bfd
> 
> 
> The two "make[4]" lines are consequences of the prior "sh: head: not found"
> issue that leaded to a "non-zero status" independent of the prior "--version"
> and "echo none" material. It then leads to assuming bfd.
> 
> Using LOCAL_ITOOLS=head makes head available and so then the status value
> check works.
> 

Sure but this command being executed never should be executing during
install; Adding 'head' as a tool isn't the right fix.

I have never been able to recreate the problem here. I have an idea I'll
test.

> 
> 
> On 2017-Nov-25, at 4:54 PM, Mark Millard <defunct email address> wrote:
> 
> . . .
> 
> On 2017-Jul-26, at 3:06 AM, Mark Millard <defunct email address> wrote:
> 
> . . .
> 
> ===
> Mark Millard
> marklmi26-fbsd at yahoo.com
> ( dsl-only.net went
> away in early 2018-Mar)
> 
> 
> 
> 
> 
> 


-- 
Regards,
Bryan Drewery

signature.asc (application/pgp-signature, 473 B)