AW: [uClibc] Buildroot Binutils/GCC improperly linked

Mario Premke premke at ess-ag.de
Tue May 11 12:54:16 UTC 2004


Hi, I have Gentoo and problems with dynamic linking uClibc as well. I assume
you give the "target options" variables to the binutil build process? What
variables are needed and why does this problem only occurs to Gentoo?

Thanks,
Mario

-----Ursprungliche Nachricht-----
Von: uclibc-bounces at uclibc.org [mailto:uclibc-bounces at uclibc.org]Im
Auftrag von tom at ceisystems.com
Gesendet: Dienstag, 11. Mai 2004 07:28
An: mjn3 at codepoet.org; jon-anderson at rogers.com
Cc: uclibc at uclibc.org
Betreff: RE: [uClibc] Buildroot Binutils/GCC improperly linked


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,

> -----Original Message-----
> From: uclibc-bounces at uclibc.org
> [mailto:uclibc-bounces at uclibc.org] On Behalf Of Manuel Novoa III
> Sent: Monday, May 10, 2004 12:49 PM
> To: Jon Anderson
> Cc: uclibc at uclibc.org
> Subject: Re: [uClibc] Buildroot Binutils/GCC improperly linked
>
> I'm guessing gentoo with CC set in the default environment?
>
> Manuel
>

Ah, Gentoo strikes again. I really _love_ the distro, I must say. I run
it on every machine I can, which currently totals five. This is actually
exactly what I was talking about in a previous post about adding the
"target options" variable to the _target_ make process in the binutils
and gcc .mk files in the make/ directory of buildroot.  Anyone see any
harm in doing so?  If not, I'll submit a patch (if you want to call it
that) for those files and any others I find in the make/ directory.

- -Tom Cameron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (MingW32)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAkCgZAUACgkQCnk9/RTg1dBtmgCeO8Uw9t0b017GYNgKgkVVk8Tm
6hQAnjvnvf1z5A2JKH5K1/w9yFm0QgC0
=7XHi
-----END PGP SIGNATURE-----





More information about the uClibc mailing list