|
From: Scott M. <sm...@no...> - 2005-03-22 18:18:02
|
Thx Jeremy,
Would -rpath be a parameter for the make/build of the target program then?
Before we get a chance to upgrade (we're still running < 2.2.0), is there
anyway I can 'unset' -rpath without rebuilding the target program?
Cheers,
Scott.
-----Original Message-----
From: Jeremy Fitzhardinge [mailto:je...@go...]
Sent: Tuesday, March 22, 2005 1:11 PM
To: Mills, Scott [CAR:2V62:EXCH]
Cc: val...@li...
Subject: Re: [Valgrind-users] RE: Question about valgrind's libpthread
Scott Mills wrote:
> Can anyone confirm/deny my suspicions and provide insight on what the
> - -Wl,-rpath,/lib -L/lib flags are and how they are used?
>
-rpath sets the runtime linkers search path, and it takes precident over
all other path settings, including LD_LIBRARY_PATH (which is what
Valgrind 2.2.0 relies on to substitute its own libpthread).
This is all moot now, since Valgrind 2.4.0 doesn't have its own
libpthread anymore, in faviour of using the system libpthread.
J
|
|
From: Scott M. <sm...@no...> - 2005-03-23 19:23:58
|
Thx, that gives us some things to try! As an update, it's starting to look like the reason valgrind is using the wrong libpthread is related to rtldi. Are there any known Valgrind workarounds involving libs set by rtldi? Thx again all, Scott. -----Original Message----- From: Paul Pluzhnikov [mailto:ppl...@gm...] Sent: Tuesday, March 22, 2005 8:31 PM To: Mills, Scott [CAR:2V62:EXCH] Cc: val...@li...; Jeremy Fitzhardinge Subject: Re: [Valgrind-users] RE: Question about valgrind's libpthread On Tue, 22 Mar 2005 15:56:04 -0800, Jeremy Fitzhardinge <je...@go...> wrote: > Scott Mills wrote: > > > Before we get a chance to upgrade (we're still running < 2.2.0), is > > there anyway I can 'unset' -rpath without rebuilding the target > > program? > > I don't think so; it's embedded in the .so files you generate. There sure is: load the exe/DSO into emacs, invoke hexl-mode, edit rpath away (replacing the first character of the string with NUL character should do the trick). Cheers, |
|
From: Jeremy F. <je...@go...> - 2005-03-22 23:56:14
|
Scott Mills wrote:
> Would -rpath be a parameter for the make/build of the target program then?
>
Yes, the -Wl,-rpath option you mentioned.
> Before we get a chance to upgrade (we're still running < 2.2.0), is
> there anyway I can 'unset' -rpath without rebuilding the target program?
>
I don't think so; it's embedded in the .so files you generate.
J
|
|
From: Paul P. <ppl...@gm...> - 2005-03-23 01:31:09
|
On Tue, 22 Mar 2005 15:56:04 -0800, Jeremy Fitzhardinge <je...@go...> wrote: > Scott Mills wrote: > > > Before we get a chance to upgrade (we're still running < 2.2.0), is > > there anyway I can 'unset' -rpath without rebuilding the target program? > > I don't think so; it's embedded in the .so files you generate. There sure is: load the exe/DSO into emacs, invoke hexl-mode, edit rpath away (replacing the first character of the string with NUL character should do the trick). Cheers, |
|
From: Sergey V. <vs...@al...> - 2005-03-23 17:59:09
|
On Tue, 22 Mar 2005 17:31:06 -0800 Paul Pluzhnikov wrote: > On Tue, 22 Mar 2005 15:56:04 -0800, Jeremy Fitzhardinge <je...@go...> wrote: > > Scott Mills wrote: > > > > > Before we get a chance to upgrade (we're still running < 2.2.0), is > > > there anyway I can 'unset' -rpath without rebuilding the target program? > > > > I don't think so; it's embedded in the .so files you generate. > > There sure is: load the exe/DSO into emacs, invoke hexl-mode, edit > rpath away (replacing the first character of the string with NUL > character should do the trick). There is a small utility to do this: http://www.tux.org/pub/X-Windows/ftp.hungry.com/chrpath/ |