Hi Tim, Kean,
Regarding the AC_PROG_NM issue:
* Ralf Wildenhues wrote on Sat, Nov 05, 2005 at 08:54:26AM CET:
Then AFAICS there's only the /usr/ccs/bin/elf path issue left, and the
$ac_tool_prefix one. Regarding the latter, I should add that CVS
Autoconf has the following description for
nm_to_check=${ac_tool_prefix}nm
[ -n $ac_tool_prefix] nm_to_check=$nm_to_check nm
Space missing before ]: ^
Right :) I was just typing blind to make sure you were OK with
the concept.
Wrong. The original code looked *only* at the first line.
The problem with looking at all lines was
On Tue, 1 Nov 2005, Ralf Wildenhues wrote:
Hi Kean,
* Kean Johnston wrote on Tue, Nov 01, 2005 at 08:34:00AM CET:
[snip]
nm -B /dev/null
on SCO output, by the way? Maybe we can adjust the old scheme to that?
A usage message becuase it doesn't support -B, but it does
support -p.
Hi Kean,
* Kean Johnston wrote on Mon, Oct 31, 2005 at 02:06:10AM CET:
The test for a suitable nm was too restrictive. First, it would only check
for nm with $ac_tool_prefix. But only the GNU version of nm installs itself
that way. This was thwarting finding a non-binutils nm on the path.
Hi Kean,
* Kean Johnston wrote on Tue, Nov 01, 2005 at 08:34:00AM CET:
Erm, are you using --host when configuring? If so, why (are you cross
compiling)? If not, $ac_tool_prefix should be empty. In any case,
It is my habbit to configure everything with:
--host=blah --build=blah
Patch 6 of 10 attached ...
Rationale:
The test for a suitable nm was too restrictive. First, it would only check
for nm with $ac_tool_prefix. But only the GNU version of nm installs itself
that way. This was thwarting finding a non-binutils nm on the path.
Second, added /usr/ccs/bin/elf to the
