Re: port-amd64/57265: Cross-build broken from Linux amd64 to NetBSD amd64

[Taylor R Campbell <riastradh%NetBSD.org@localhost>]

The following reply was made to PR port-amd64/57265; it has been noted by GNATS.

From: Taylor R Campbell <riastradh%NetBSD.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: port-amd64-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: port-amd64/57265: Cross-build broken from Linux amd64 to NetBSD amd64
Date: Thu, 9 Mar 2023 17:16:15 +0000

 > Date: Thu,  9 Mar 2023 16:10:01 +0000 (UTC)
 > From: jbglaw%lug-owl.de@localhost
 > 
 > I *guess* a LD_LIBRARY_PATH with '.' or the $DESTDIR/lib or
 > something similar sneaked in.
 
 Nothing in the build uses LD_LIBRARY_PATH,[*] and it is unlikely for
 nbmandoc to have been inadvertently linked against a libc that doesn't
 exist yet.  But from your build log, I see:
 
 ++ export LD_LIBRARY_PATH=/usr/lib/gcc-snapshot/lib:
 ++ LD_LIBRARY_PATH=/usr/lib/gcc-snapshot/lib:
 
 Is that in your build environment?  What happens if you remove it?
 
 [*] Exceptions: bsd.test.mk, not relevant here, only in native builds;
     and libexec/httpd/lua/Makefile, for a development-only test
     target, not used automatically as far as I know, and not likely
     relevant to mandoc or libc issues.