libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FYI: libtool--devo--1.0--patch-200


From: Ralf Wildenhues
Subject: Re: FYI: libtool--devo--1.0--patch-200
Date: Thu, 23 Sep 2004 15:16:12 +0200

* Gary V. Vaughan wrote on Thu, Sep 23, 2004 at 03:08:55PM CEST:

Applied to HEAD.

* looking for address@hidden/libtool--devo--1.0--patch-199 to compare with
* comparing to address@hidden/libtool--devo--1.0--patch-199
M  ChangeLog
M  Makefile.am
*snip*
M  m4/libtool.m4
*snip*

* modified files
Index: Changelog
from Gary V. Vaughan <address@hidden>
        Since defs can change (path to grep for example) when it is made
        for a different host, it can't be shipped.  That also means that
        defs will always be generated in the build tree, so each test case
can have the srcdir discovery factored away into tests/defs.in:
--- orig/m4/libtool.m4
+++ mod/m4/libtool.m4
@@ -2726,6 +2726,12 @@
   symcode='[[ABCDGIRSTW]]' ;;
 esac
+# If we're using GNU nm, then use its standard symbol codes.
+case `$NM -V 2>&1` in
+*GNU* | *'with BFD'*)
+  symcode='[[ABCDGIRSTW]]' ;;
+esac
+
 # Transform an extracted symbol line into a proper C declaration.
 # Some systems (esp. on ia64) link data and code symols differently,
 # so use this general approach.

This looks awfully like a merge error, since the GNU nm case is doubled
now. star-merge at fault?
Regards,
Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]