This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: new libc
- From: "Ryan Arnold" <ryan dot arnold at gmail dot com>
- To: "Polina Dudnik" <pdudnik at cs dot wisc dot edu>
- Cc: libc-help at sourceware dot org
- Date: Thu, 4 Sep 2008 16:17:16 -0500
- Subject: Re: new libc
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=cE0Wl0bLCaa38Czqa6kZvXhO/oEADYpR1u+E8QwZANQ=; b=GxM6Bm6O0kktfsggm95dKnOeX5JGfo6rKI9amKnWynnT9LSWjUbmxq2IkwbaiDFZ57 lT6/BqKgPEUBQu71/RJpJnhpTFQcpHM5RUwRFLKTBS4o71VcDevZ858oDm9hXHz+GrpK vMrZ+u/0s24gK0kNWB1y09/pfeszNt9M8hTmo=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=ctsg3P4LUf0T21VMqG1mCWnv4C5XwzuiX5C+YfWkIaJ8OBDeoDy8VZU/imNykkGgLu 144mTeNq4CrwTsg7Q+TAmq41YeMHpQwJqNLp/fPQ1lYnS6Ow2mGJhVpQlktPahucbZMH 7xsp7u8jaNCc0rMCCsykzOK+IUZgNf5K/p1mY=
- References: <48C04613.3000206@cs.wisc.edu>
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
>