libtoolize.in typo

Self explanatory I hope! Cheers, Patrick Index: libtoolize.in === RCS file: /cvsroot/libtool/libtool/libtoolize.in,v retrieving revision 1.25 diff -u -r1.25 libtoolize.in --- libtoolize.in 14 Oct 2003 22:52:57 - 1.25 ++

Re: libtoolize.in typo

Patrick Welche wrote: Self explanatory I hope! Cheers, Patrick Indeed. Applied. Thanks! Index: libtoolize.in === RCS file: /cvsroot/libtool/libtool/libtoolize.in,v retrieving revision 1.25 diff -u -r1.25 libtoolize.in --- libtoolize

Re: How to know what modules were dlpreopen-ed?

Kevin P. Fleming wrote: Bob Friesenhahn wrote: For the application I support, we use our own directory scanner to look for modules (.la files) to load via a fully-qualified path. It would be useful if this capability was included as part of libltdl. You can pass a directory path to lt_dlforeachfi

[PATCH] set handler->info.name for all modules, not just libtool modules

As a followup to the discussion earlier this week, I'd like to suggest the patch below. This causes ltdl to _always_ set handler->info.name to a canonicalized library name, instead of only doing it for libtool-created modules. The only disadvantage that I can see to doing this is that when lt_dl

host=target, build=host and package behavior

Hi, I sent an email to those mailing lists with an account from the mail15.com spammer. I apologize for the trouble. I post a sum up of my message: I wanted to use the host and target options to compile "native cross" binutils. Namely with --host=i686-pc-linux-gnu and --target=i686-pc-linux-gnu