> It would be good if we could see a copy of config.log. Install.log is over 25K lines, too large for posting. See it here: http://www.physics.rutgers.edu/~rvaughn/install.log
-Richard Following is On Feb 16, 1:29 am, David Kirkby <[email protected]> wrote: > On 15 February 2010 18:51, William Stein <[email protected]> wrote: > > > > > On Mon, Feb 15, 2010 at 10:19 AM, [email protected] <[email protected]> > > wrote: > >> I am running 64-bit Scientific Linux 4.8. > >> I downloaded/un-tar'd sage-4.2.1.tar, > >> cd'd to sage-4.2.1 and ran 'make'. > > >> Relevant output appended. > > >> -Richard Vaughn > > >> ================================================================ > > >> checking whether we are using the GNU C++ compiler... yes > >> checking whether g++ accepts -g... yes > >> checking C++ compiler g++ -O2 -m64 -march=nocona -mtune=nocona... no, > >> std iostream > >> checking C++ compiler g++ -g -O2... no, std iostream > >> configure: error: C++ compiler not available, see config.log for > >> details > > > The above error suggests to me that you need to install a C++ compiler? > > Do you have gcc and g++ installed? If so, what versions? > > > -- William > > It would be good if we could see a copy of config.log. From later > posts, it would appear this case is not unique on Suse. In which case, > if I could see config.log, it may be possible to check for this > problem earlier in the 'prereq' script. That would allow us to detect > the issue earlier. -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
