Subject: Re: Re: Re: Re: -2.0.1 makes bad binaries ?
To: Joel CARNAT <joel@carnat.net>
From: Quentin Garnier <cube@cubidou.net>
List: netbsd-users
Date: 01/25/2005 23:53:44
--aZ/0/p6gSDXwzas7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 25, 2005 at 11:10:48PM +0100, Joel CARNAT wrote:
[...]
> Program Headers:
[...]
>   INTERP         0x0000f4 0x080480f4 0x080480f4 0x00013 0x00013 R   0x1
>       [Requesting program interpreter: /usr/lib/libc.so.1]

Now *that*'s one broken *static* binary :-)

What happens is that bash Makefile does more or less this:

cc -static -o bash my_objs.o /usr/lib/intl.so -lmylibs

which is nonsense, but the main bug is that pkgsrc should automatically
correct this from the wrappers.

Please send a PR for that issue.

As for the pkgfind package, it's obviously broken right now, I'll dig a
bit more about the exact reasons that lead someone use ${COMPILE.c} to
compile _and_ link a binary.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"Commala-come-five! / Even when the shadows rise!
To see the world and walk the world / Makes ya glad to be alive."
Susannah's Song, The Dark Tower VI, Stephen King, 2004.

--aZ/0/p6gSDXwzas7
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iQEVAwUBQfbN+NgoQloHrPnoAQLPkAf6A1IW/1ZFbFmG2gen3L6KhZnx8J230mnR
i/t52u3TvxcP1fGmI4+ThqdrUOyb94CRG72bbZtLeYW+9cFiorikc4b6TdHEnbfU
gj3kNpy9R1BfBxSq0BTt70rwCSY6Y8Q8q5LHKR13aG6qjyauG1J/cYQGz5FeudFh
qujJ8aDJaAjMXTOhREqH4+cbUJvr1tPVPQ7YiXkIK7gm+HbKwdRgL0H5nu87mWv/
G2xuhxy8yNxcBLfnP3TRnK5y9qgpDkDt8Ot/I1Wmer/pdaNXp9VC+AYLU0VuvScS
4iL6dbO5VELb56WyWfkHzeWujKHslceBfV25eHUgQ0oQNaAhtZeAcw==
=XiBW
-----END PGP SIGNATURE-----

--aZ/0/p6gSDXwzas7--