[Peeweelinux] RH62 compat. question

[Jonathan Sturges]

Hmmm.  I'm doing it right but it doesn't link properly.  The two variables
defined by the script are set properly and exported, but they don't appear
to affect anything.  BTW, I'm trying to compile nptd-4.2.0.

After playing around, I found that if I set LDFLAGS to "-Xlinker -m -Xlinker
elf_i386_glibc21" (which should accomplish the same results with ld that
setting LDEMULATION does), it does "something" different because linking now
fails when linking the ntpd binary, whereas before it linked it successfully
to the RH8 glibc.

I'll play with it some more, but it's kinda frustrating for now.

thanks for any more tips,
Jonathan


----- Original Message ----- 
From: "Mark Meade" <mark@lakeshoremicro.com>
To: <peeweelinux@adis.on.ca>; "Jonathan Sturges" <jonathan@sprintmail.com>
Sent: Monday, January 05, 2004 7:55 AM
Subject: Re: [Peeweelinux] RH62 compat. question


> On Sunday 04 January 2004 11:31 pm, Jonathan Sturges wrote:
> > My question is, is there any steps other than just running the
> > /usr/i386-glibc21-linux/bin/i386-glibc21-linux-env.sh script before
> > compiling the applications?  When I take this script into my shell with
".
> > /usr/i386-glibc21-linux/bin/i386-glibc21-linux-env.sh", and then do
> > configure/make/etc, the resulting binaries are still linked against the
> > glibc from RH8.  Are there additional env. variables to make gcc/ld find
> > the older libraries?
>
> Hi Jonathan,
>
> I had similar problems, although I was using RH7.2.  Take a look at:
> http://mail.adis.on.ca/pipermail/peeweelinux/2002-April/000569.html
>
> Mark
>
>
> _______________________________________________
> Peeweelinux mailing list
> Peeweelinux@adis.on.ca
> http://mail.adis.on.ca/lists/listinfo/peeweelinux
>