On 04/20/2011 03:00 PM, Ray Kolbe wrote: > I am attempting to install autoconf-2.68. I have installed gcc (GCC) 3.4.6 > directly from sunfreeware, so it's located in /usr/local/bin. I would like > to install a later version, but need autoconf to work first. I curently > have autoconf 2.59 installed. > > I am running Solaris on an Ultra-60 with 2 processors and 1GB of memory. > > Thanks for any help you may be able to provide. > > --Ray
Thanks for the report. Most of your failures look like this one for 260. compile.at:144: testing AC_LANG_SOURCE(C++) ... > configure:2007: g++ -o conftest conftest.cpp >&5 > configure:2011: $? = 0 > configure:2018: ./conftest > ld.so.1: conftest: fatal: libstdc++.so.6: open failed: No such file or directory > ./configure: line 2020: 27274 Killed ./conftest$ac_cv_exeext That is, you've got some setup issues where your existing C++ compiler is broken. I don't know if autoconf should be able to handle this gracefully. Generally, g++ is either present and working, or missing and autoconf gets along just fine; you are in the rare condition of g++ present but not working. At any rate, I think this is a bug in your environment and not in your just-built autoconf, so I think you can go ahead and install it without issues. Autoconf itself does not require a working compiler for building or installation; the only use of the compiler is in the testsuite, where autoconf assumes that if a compiler is present it will work (basically, the test is proving whether autoconf can correctly determine details about a working compiler, and you've thrown it a wrench by not having a working compiler). -- Eric Blake ebl...@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
