make check passes in Solaris 10 x86

[David Relson]

On Sun, 27 Nov 2005 14:05:18 -0800
Chris Wilkes wrote:

> Just thought I would share with everyone that "make check" passes on a
> solaris 10 x86 box I have.
> 
> # uname -a
> SunOS sol01 5.10 Generic i86pc i386 i86pc
> 
> >From http://www.sunfreeware.com I installed the following packages:
> 
> * gcc 3.3.2
> * Berkeley 4.2
> * make (although I use the /usr/ccs/bin/make one)
> 
> Make sure to go through the steps on the sunfreeware site to update the
> gcc header files or else you'll get some errors involving "ctid_t"
> 
> 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.
> 
> Putting /usr/ccs/bin in the $PATH fixed that.  I'm not sure how the
> configure program can check for the existance of the "ar" program.
> 
> Let me know if you want to see the config.log file and I'll send it as a
> file attachment (14k gzipped).
> 
> Chris

Hi Chris,

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


What do you have in yours? Likely the line numbers are slightly
different, but that doesn't matter.

If you want to experiment, you can trim down your copy of configure.ac,
then run autogen.sh to regenerate the configure script and see what you
get.

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

Regards,

David