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

[Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost>]

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

From: Jan-Benedict Glaw <jbglaw%lug-owl.de@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 19:07:06 +0100

 --bai2ihk4tmftpslt
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Thu, 2023-03-09 17:20:01 +0000, Taylor R Campbell <riastradh%NetBSD.org@localhost>=
  wrote:
 > From: jbglaw%lug-owl.de@localhost
 > >=20
 > > I *guess* a LD_LIBRARY_PATH with '.' or the $DESTDIR/lib or
 > > something similar sneaked in.
 > =20
 >  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:
 
 As I wrote, nbmandoc is called several times beforehand and all these
 invocations were running perfectly fine. "libc.so.6" is the one on a
 GNU/Linux system.  It starts with libz being build (and nbmandoc links
 with -lz).
 
 >  ++ export LD_LIBRARY_PATH=3D/usr/lib/gcc-snapshot/lib:
 >  ++ LD_LIBRARY_PATH=3D/usr/lib/gcc-snapshot/lib:
 > =20
 >  Is that in your build environment?  What happens if you remove it?
 
 It is!  That's from a little to choose between different compilers
 (ie. a recent GCC snapshot, the "usual" (older) system GCC, some CLANG
 versions.  But that LD_LIBRARY_PATH should in no way enable ld.so to
 pull in some libz (that's a guess) from the destdir, should it?
 
   Just started a build using the sytem compiler (not setting
 anything). I wonder (read: hope!) that the empty path component
 doesn't wrongly resolve to "." ...  (If the next build succeeds, my
 next test would be LD_LIBRARY_PATH=3D"/does_not_exist:"...)
 
 >  [*] 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.
 
 As I guess, it's just mandoc showing the symptom: It's linked against
 -lz and works before libz is build, but as the library emerges, it
 fails by not finding libc.so.12 (which is NetBSD libc.)
 
 MfG, JBG
 
 --=20
 
 --bai2ihk4tmftpslt
 Content-Type: application/pgp-signature; name="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 
 iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCZAogSAAKCRAdvV51g5nh
 uyLiAJ4l06yLnXeYPp72i2rmA8GITDzepACffbfk7jCwVDnlLYdmX+nBAAeQDtM=
 =FWTy
 -----END PGP SIGNATURE-----
 
 --bai2ihk4tmftpslt--