[Top][All Lists]

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

Re: Problem with LT_PATH_NM

From: Peter Rosin
Subject: Re: Problem with LT_PATH_NM
Date: Wed, 14 Jan 2009 22:38:16 +0100
User-agent: Thunderbird (Windows/20081209)

Den 2009-01-14 20:24 skrev Peter Rosin:
Den 2009-01-14 14:29 skrev Peter Kjellerstedt:
* the second is that my /usr/bin/link should not be used as NM
  since it obviously does not support the options required (as
  it is the wrong program).

Can't argue about that, but you should never end up looking for
"link" if you have nm on your path, so that's a red herring in
my opinion. If the nm locator code is fixed, this is a non-issue.
Further, if nm is not on $PATH, it doesn't make any sense to
set NM=nm.

Here's a patch that makes the configure check a bit more picky
about what it recognizes as "dumpbin". As it happens, the MS
dumpbin outputs:

Microsoft (R) COFF/PE Dumper Version x.yy.zzzzz.www

as its first line of output, so I'm triggering on *COFF*

With this patch, the old fallback (NM=nm) should kick in and
save you.

Does this help?

(But it just papers over the real bug IMHO)

diff --git a/libltdl/m4/libtool.m4 b/libltdl/m4/libtool.m4
index b7b566d..5f5a131 100644
--- a/libltdl/m4/libtool.m4
+++ b/libltdl/m4/libtool.m4
@@ -3156,7 +3156,21 @@ if test "$lt_cv_path_NM" != "no"; then
   # Didn't find any BSD compatible name lister, look for dumpbin.
-  AC_CHECK_TOOLS(DUMPBIN, ["dumpbin -symbols" "link -dump -symbols"], :)
+  if test -n "$DUMPBIN"; then
+    # Let the user override the test.
+  else
+    AC_CHECK_TOOLS(DUMPBIN, [dumpbin "link -dump"], :)
+    case `$DUMPBIN -symbols /dev/null 2>&1 | sed '1q'` in
+    *COFF*)
+      DUMPBIN="$DUMPBIN -symbols"
+      break
+      ;;
+    *)
+      DUMPBIN=:
+      break
+      ;;
+    esac
+  fi
   if test "$DUMPBIN" != ":"; then

reply via email to

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