Hello,
I'm working on linux based embedded platforms. To build a complete
platform, we usually compile and install our software packages in a
directory that is specific to each developer, say:
/home/fred/frozen/usr/lib/...
Then, the compiled libraries and executables that must be actua
> I think the DESTDIR patch for ltmain.sh fixes that. At least it did for
> me. I had the problem that relinking was failing with "make prefix=/blah
> install" so I retooled with DESTDIR and with this patch everything seems
> OK.
Thanks for the info. I experience problems with simple program li
> We have this same need when building our software. I've hacked our version of
> libtool to support this feature:
I've applied your patch (by hand), and my compilation line is
transformed like that:
-L/home/fred/external/build/frozen/glib/arm-linux-any-any/usr/lib -lglib-2.0
...becomes..
-L/
Hi,
> The real problem is that ELF platforms shouldn't
> ever relink, because it isn't necessary and it
> causes problems like these. If I get a patch
I must admit I heavily relied on libtool so far. It worked so well
that I never took the time to study the details of what it was
performing.
So
> That can only happen because the linker didn't find a libc in your first -L
> directory. Fix that, that's your real problem.
My first -L directory contains only the glib. The libc is in the
default search path of the compiler. However, adding a -L path to the
libc before the -L/usr/lib does not
