This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: linker errors when compiling and linking with a new glibc


OK, now the error went away =) but I get a segmentation fault =( ... to use gdb with my executable, do I need to do anything special - like tell it where glibc is etc?
If I do "gdb my-exe", then "run", I get that there was an error loading shared libraries: libdl.so.2: cannot open shared obj file: no such file or dir.

Thanks for all the help, I really appreciate it.

Daniel



----- Original Message ----
From: Carlos O'Donell <carlos@systemhalted.org>
To: Daniel De La Zerda <danieldelazerda@gmail.com>
Cc: Ryan Arnold <ryan.arnold@gmail.com>; libc-help@sourceware.org; pasky@suse.cz
Sent: Thursday, March 19, 2009 3:47:58 PM
Subject: Re: linker errors when compiling and linking with a new glibc

On Thu, Mar 19, 2009 at 3:32 PM, Daniel De La Zerda
<ddelazerda007@yahoo.com> wrote:
> The first option doesn't work and neither does the second. With the second option, when I do an "rpm -ivh --prefix=<path to glibc build> <libgcc rpm>" I get the error saying that libgcc is not "relocateable". I also tried copying /lib/libgcc_s.so.1 to <glibc build path> and I keep getting the error that "libgcc_s.so.1 must be installed for pthread_cancel to work".

Instal libgcc_s.so.1 somwhere. Add the path to the list of paths in
the --library-path option passed to ld.so.1 when running the testcase.

Cheers,
Carlos.



      


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]