make check passes in Solaris 10 x86

[Chris Wilkes]

On Sun, Nov 27, 2005 at 05:19:25PM -0500, David Relson wrote:
> On Sun, 27 Nov 2005 14:05:18 -0800
> Chris Wilkes wrote:
> 
> > one weird thing I noticed was that if /usr/ccs/bin wasn't in the PATH the
> >   ./configure  --with-libdb-prefix=/usr/local/BerkeleyDB.4.2/
> > wouldn't complain about not being able to find "ar" (which is in the
> > /usr/ccs/bin directory).  Its a little confusing as make tries do so a
> > " cru ..." on something (should be "ar cru ...") and it fails, not being
> > able to find the "cru" program.
> > 
> 
> The auto-tools are within Matthias' area of expertise.  I'm a rookie
> where they're involved.  None-the-less, here's some info:
> 
> In configure.ac is the following line:
> 
>    AC_CHECK_TOOL(AR, ar)
> 
> and ./configure is generated from that.
> 
> With a quick test, file config.log contained the following:
> 
> ## ----------- ##
> ## Core tests. ##
> ## ----------- ##
> 
> configure:1268: checking build system type
> configure:1286: result: i686-pc-linux-gnu
> configure:1294: checking host system type
> configure:1308: result: i686-pc-linux-gnu
> configure:1316: checking target system type
> configure:1330: result: i686-pc-linux-gnu
> configure:1386: checking for ar
> configure:1402: found /usr/bin/ar
> configure:1412: result: ar

Here's my environment:

# echo $PATH
/usr/sbin:/usr/bin:/usr/local/bin
# which ar
no ar in /usr/sbin /usr/bin /usr/local/bin
# file /usr/ccs/bin/ar
/usr/ccs/bin/ar:        ELF 32-bit LSB executable 80386 Version 1,
  dynamically linked, stripped
# which gcc
/usr/local/bin/gcc
# which make
/usr/local/bin/make


However I do not use that make and instead use the one under
/usr/ccs/bin


And here are the lines from config.log:

configure:2634: checking for style of include used by make
configure:2662: result: GNU
configure:2690: checking dependency style of gcc
configure:2780: result: gcc3
configure:2838: checking for ar
configure:2867: result: no
configure:2917: checking for ranlib
configure:2944: result: :


> Unless Matthias asks for more info, knowing the "ar" related lines of
> config.log should be sufficient.

Let me know if there's anything else.

Chris