Re: Solaris 9 build (configure) error's

Pete Naylor <[email protected]> writes:

> Niels, I wonder where your libraries and includes are installed on
> your Solaris system? If they're all installed under /usr/local then
> it may be that GCC is finding them there regardless of your
> configure options - GCC's default path to look for those things is
> /usr/local.

On the Solaris systems I've used, the libraries are installed under
/usr/local/lib, and by default, they are indeed picked up by gcc at
link-time. However, the dynamic loader does *not* by default look in
/usr/local/lib at run-time, so the default library search results in
binaries that link but can't be executed (unless one sets
LD_LIBRARY_PATH, which in general is discouraged), and configure
complains loudly about that.

So I use ./configure --with-lib-path=/usr/local, in order to get lsh:s
configure to add both -L/usr/local/lib and -R/usr/local/lib to
LDFLAGS. Works for me, for what ever that's worth.

One known bug is that I think the --with-lib-path parsing breaks if
you use directory names with whitespace in them, but I suspect you're
seeing some different bug. The config.log from a failing build will be
needed to have any chance to sort it out.

/Niels