Thanks for the bug report. As the one who introduced the
dumpbin support I feel obliged to respond...
Den 2009-01-14 14:29 skrev Peter Kjellerstedt:
I would say that there are two bugs here:
* the first is that the code looking for nm in
"$PATH /usr/ccs/bin/elf /usr/ccs/bin /usr/ucb /bin" (not seen
in the patch above) is not doing its job. My $PATH contains
"...:/usr/bin:.." where nm is installed, but the for loop
does not split the colon separated $PATH correctly and thus
does not find /usr/bin/nm.
My bash splits my $PATH correctly using that construct. Something
else is probably going on, maybe that construct isn't portable?
I should also add that the code added to support dumpbin did not
touch the nm locator code, and the dumpbin code is only entered if
nm is not found.
What shell are you using? (I think it's reported in libtool --help)
What does the below script output for you? (with the ???sh replaced
with whatever you are using for $CONFIG_SHELL)
for i in $PATH /usr/bin /bin; do
If that's working as expected, one wonders what your
$PATH_SEPARATOR is set to in the configure script? Extremely
surprising if it's not :
* 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
I tried to look a libtool's git repository to see if there were
any changes related to this, but I could not find any (please
tell me if there are).
Thankfully I can use "NM=nm configure ..." to circumvent the
problem, but this does not sound like a general solution.
I tend to favour "configure NM=nm ...", but that's a minor point.
Bug-libtool mailing list