On 12/20/06, Joe Ciccone <[EMAIL PROTECTED]> wrote:
> I've been playing around with libtool for the past 3 days and have not come up with something working yet. This little script is so complex, it is such a pain to modify or even figure out what the heck it's doing. I just hope this doesn't take as long as it did to figure out the locales.
Joe, I was reading the libtool archives today, and I think I have an idea how they work now and might have an idea for a working hack. Anyway, configure and ltmain.sh work together to generate the libtool script at build time. ltmain.sh is generated by libtoolize and libtool.m4 by the developer. But, you can patch it at build time like Makefile.in. That way, you can force in options that libtool would otherwise not know how to handle, like --sysroot. For instance: sed -i.bak 's%compiler_flags=$%&"--sysroot=/foo/bar"%' ltmain.sh That would make the first empty compiler_flags have --sysroot instead. For my boring old native compiler, it made things break, but you can see that the option got in there. /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o libpaco-log.la -rpath /usr/lib libpaco_log_la-log.lo -ldl gcc -shared .libs/libpaco_log_la-log.o -ldl --sysroot=/foo/bar -Wl,-soname -Wl,libpaco-log.so.0 -o .libs/libpaco-log.so.0.0.0 Does that help at all? -- Dan _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
