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 +++ libtoolize.in 15 Oct 2003 08:56:30 - @@ -574,7 +574,7 @@ func_copy_all_files "$pkgdatadir" "$auxdir" 'config.guess|config.sub|ltmain.sh' func_config_update "$pkgdatadir/config.guess" "$auxdir/config.guess" test -f "$pkgdatadir/config.sub" \ - && func_config_update "$pkgdatadir/config.guess" "$auxdir/config.sub" + && func_config_update "$pkgdatadir/config.sub" "$auxdir/config.sub" fi func_ltmain_update "$pkgdatadir/ltmain.sh" "$auxdir/ltmain.sh" ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
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.in 14 Oct 2003 22:52:57 - 1.25 +++ libtoolize.in 15 Oct 2003 08:56:30 - @@ -574,7 +574,7 @@ func_copy_all_files "$pkgdatadir" "$auxdir" 'config.guess|config.sub|ltmain.sh' func_config_update "$pkgdatadir/config.guess" "$auxdir/config.guess" test -f "$pkgdatadir/config.sub" \ - && func_config_update "$pkgdatadir/config.guess" "$auxdir/config.sub" + && func_config_update "$pkgdatadir/config.sub" "$auxdir/config.sub" fi func_ltmain_update "$pkgdatadir/ltmain.sh" "$auxdir/ltmain.sh" -- ())_. Gary V. Vaughangary@(lilith.warpmail.net|gnu.org) ( '/ Research Scientist http://www.oranda.demon.co.uk ,_()) / )= GNU Hacker http://www.gnu.org/software/libtool \' `& `(_~)_ Tech' Author http://sources.redhat.com/autobook =`---d__/ ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
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_dlforeachfile, which will then call your callback function with extension-stripped filenames that it finds in that directory. Your callback function can then call lt_dlopen or lt_dlopenext, whatever is appropriate. Exactly. I added lt_dlforeachfile specifically to save having to write custom directory walkers... Bob, if you find lt_dlforeachfile is lacking something you require, bring it up on this list, and we'll see about adding it into libltdl. Cheers, Gary. -- ())_. Gary V. Vaughangary@(lilith.warpmail.net|gnu.org) ( '/ Research Scientist http://www.oranda.demon.co.uk ,_()) / )= GNU Hacker http://www.gnu.org/software/libtool \' `& `(_~)_ Tech' Author http://sources.redhat.com/autobook =`---d__/ ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
[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_dlsym is called for a non-libtool module, a spurious lookup for
"modulename_LTX_symbol" will be done, when it wasn't before. I can't see how this would
cause an actual problem for anyone, though, since it's not likely they'd have symbols
named
that way if they're not using libtool to create their libraries.
With this change, lt_dlsym()-ing a symbol from a preloaded library works properly on
my system;
it searches for the symbol with the *_LTX_ prefix, which means I don't have to
forcibly add
that prefix in my code.
--- ltdl.dist Wed Oct 15 07:11:08 2003
+++ ltdl.c Wed Oct 15 07:37:39 2003
@@ -3092,8 +3092,34 @@
assert (base_name && *base_name);
- /* Check whether we are opening a libtool module (.la extension). */
ext = strrchr (base_name, '.');
+
+ /* extract the module name from the file name */
+ name = LT_EMALLOC (char, ext - base_name + 1);
+ if (!name)
+{
+ ++errors;
+ goto cleanup;
+}
+
+ /* canonicalize the module name */
+ {
+size_t i;
+for (i = 0; i < ext - base_name; ++i)
+ {
+ if (isalnum ((int)(base_name[i])))
+ {
+ name[i] = base_name[i];
+ }
+ else
+ {
+ name[i] = '_';
+ }
+ }
+name[ext - base_name] = LT_EOS_CHAR;
+ }
+
+ /* Check whether we are opening a libtool module (.la extension). */
if (ext && strcmp (ext, archive_ext) == 0)
{
/* this seems to be a libtool module */
@@ -3110,31 +3136,6 @@
of libtool */
int installed = 1;
- /* extract the module name from the file name */
- name = LT_EMALLOC (char, ext - base_name + 1);
- if (!name)
- {
- ++errors;
- goto cleanup;
- }
-
- /* canonicalize the module name */
- {
-size_t i;
-for (i = 0; i < ext - base_name; ++i)
- {
- if (isalnum ((int)(base_name[i])))
- {
- name[i] = base_name[i];
- }
- else
- {
- name[i] = '_';
- }
- }
-name[ext - base_name] = LT_EOS_CHAR;
- }
-
/* Now try to open the .la file. If there is no directory name
component, try to find it first in user_search_path and then other
prescribed paths. Otherwise (or in any case if the module was not
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
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 or in others words I wanted to trigger the "cross-tools compilation" behavior of the package with host=target. Would it be wiser to let this behavior triggerable with a special "force-compilation-of-cross-tools" configure option? Of course, I extend the issue to the build=host, aka cross compilation, case. I currently have some free time, then I could implement those features or... am I proposing insane things to do? Sylvain _ Envie de discuter en "live" avec vos amis ? Télécharger MSN Messenger http://www.ifrance.com/_reloc/m la 1ère messagerie instantanée de France ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
