Re: new libc

[Polina Dudnik <pdudnik at cs dot wisc dot edu>]

Hi,

thank you for the prompt reply. I've tried your solution and it didn't 
work. I also tried to call ld directly as follows
ld -d y -o z4 z4.o .libc.so.1 libm.so.2

So, I am manually passing it my newly built libc. However, it still 
refuses to recognize the definitions of the new functions. Why could 
that be?

Polina

Ryan Arnold wrote:
> Polina,
>
> Try the following:
>
> SYSROOT=<path to the GLIBC install directory>
>
> gcc ... \
>   --sysroot=${SYSROOT} \
>   -Wl,--rpath=${SYSROOT}/lib \
>   -Wl,--dynamic-linker=${SYSROOT}/lib/ld.so.1
>
> On Thu, Sep 4, 2008 at 3:33 PM, Polina Dudnik <pdudnik@cs.wisc.edu> wrote:
> > Hi,
> >
> > I build a new libc on OpenSolaris with certain modifications. Specifically,
> > new libc now includes a few new functions. Now I am trying to compile a file
> > with the new libc. To point the compiler to the new libc I use the -R flag.
> > However, what ends up happening is my new binary file depends on both the
> > new and the old libc. So, if I use the new functions the linker gets
> > confused and can't find the definitions for the new functions. How can I fix
> > this? Thank you.
> >
> > Polina