Hello,
I just upgraded our site to autoconf 2.59. I had to make a hand
edit to the autoreconf
perl script. I had to change line 489 from:
mkdir $aux_dir
or error "cannot create $aux_dir: $!";
to:
mkdir $aux_dir, 755
or error "cannot create $aux_dir: $!";
That is the mkdir command
So autoconf depends on perl 5.8 then? We are using 5.0. In 5.0 it is definitely
not optional.
Thanks,
Stan
>>> Andreas Schwab <[EMAIL PROTECTED]> 2/28/2005 4:57:31 PM >>>
"Stan Guillory" <[EMAIL PROTECTED]> writes:
> That is the mkdir command
I have just upgraded to Autoconf 2.59, Automake 1.95, and Libtool
1.5.14. Now when I build shared libraries,
they don't have the .so extension in thier names. Anybody know why? It
may be a question for the libtool list,
but I thought I try both places.
Stan
>>> Hugh Sasse Staff Elec Eng <[EMAIL
Has anyone had any experience using purify with autoconf based c++
builds. Any caveats? Any tips?
Thanks,
Stanford S. Guillory
Systems Engineer
Southwest Airlines
214-792-6136
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/li
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
Actually, on Solaris at least, LD_LIBRARY_PATH *is* used to find shared libraries to
link against. It's been
something we have particularly had to guard against, since some older versions of
thirdparty libraries we
use have been installed in /usr/lib and it has corrupted our builds. In fact,
LD