On Aug 18, 2007, at 11:27 PM, David Fang wrote:
I'm stlll curious why the tests that fail on darwin actually
*work* on linux and freebsd... After digging through more of
libtool/ltdl's internals, I'm still a bit puzzled how those systems
magically found an uninstalled module's uninstal
On Aug 18, 2007, at 9:47 PM, David Fang wrote:
Can you (or anyone) reproduce my findings with test project 0.0.1?
Am I Doing The Right Thing (TM)?
Hi David,
I reproduced.
Your workaround seems valid to me, -dlopen ../lib/foo does not add
the absolute path to ../lib in the wrapper script
Hi,
Must've missed this message earlier...
> > The executable takes command-line arguments that call lt_dladdsearchpath
> > (option -L) and lt_dlopenext (option -l). The file, ../../lib/mymodule.la
> > has already been built at the time of testing. The executable is invoked
> > with "-L.
> > > It is entirely possible that you've found a bug, Mac OS X should work
> > > the same as linux et.al. in this regard. Does the module itself have any
> > > dependencies that possibly are not being found (check with otool -L
> > > mymodule.0.so)? If that is not the case, please send more info (
> > It is entirely possible that you've found a bug, Mac OS X should work
> > the same as linux et.al. in this regard. Does the module itself have any
> > dependencies that possibly are not being found (check with otool -L
> > mymodule.0.so)? If that is not the case, please send more info (if you
>
On Sat, 2007-08-18 at 16:29 -0400, David Fang wrote:
> > > I'm having a problem testing some libtool (ltdl) modules, but only
> > > on OS X (darwin7 and darwin8, libtool 1.5.22 and .24). My executable
> > > lt_dlopens a .la library in another built directory (during make check
> > > testing), an
> > I'm having a problem testing some libtool (ltdl) modules, but only
> > on OS X (darwin7 and darwin8, libtool 1.5.22 and .24). My executable
> > lt_dlopens a .la library in another built directory (during make check
> > testing), and fails with an lt_dlerror message like:
> >
> > dlopen(../
* Brian Dessent wrote on Fri, Aug 17, 2007 at 09:49:48PM CEST:
> Jason Curl wrote:
>
> > lib -OUT:.libs/libtp.lib version.o
> > ../libtool: line 5973: lib: command not found
>
> I'm not sure why it's trying to use lib here, that seems wrong if you're
> using gcc/binutils. Possibly a configure p
Hello David,
* David Fang wrote on Sat, Aug 18, 2007 at 05:05:13AM CEST:
>
> The executable takes command-line arguments that call lt_dladdsearchpath
> (option -L) and lt_dlopenext (option -l). The file, ../../lib/mymodule.la
> has already been built at the time of testing. The executable is in
