Hopefully Mariah has some idea about this. I don't see why that wouldn't compile, except that perhaps it needs a -m64 or something like that.
Bill. 2009/5/31 Jason Moxham <[email protected]>: > > compiling > > int main (void) { return 0; } > > with > gcc crap.cc && ./a.out > is fine > > but > g++ crap.cc && ./a.out > libc.so.1: a.out: > fatal: /usr/local/gcc-4.4.0/x86_64-SunOS-core2/lib/amd64/libstdc++.so.6: > wrong ELF class: ELFCLASS64 > Killed > > which is what configure basically trys to do > > not sure why it doesn't happen when we just have --enable-cxx and no > build=none > > > > > On Sunday 31 May 2009 01:44:57 Bill Hart wrote: >> What does config.log say went wrong? >> >> 2009/5/31 Jason Moxham <[email protected]>: >> > ./configure --enable-cxx --build=none >> > fails on fulvia with >> > >> > checking build system type... none-none-none >> > checking host system type... none-none-none >> > checking for a BSD-compatible >> > install... /home/jasonmoxham/mpir/mpir/trunk/install-sh -c >> > checking whether build environment is sane... yes >> > checking for gawk... no >> > checking for mawk... no >> > checking for nawk... nawk >> > checking whether make sets $(MAKE)... yes >> > checking whether to enable maintainer-specific portions of Makefiles... >> > no checking ABI=long >> > checking compiler gcc -O3 -DNO_ASM... yes >> > checking for gcc... gcc >> > checking for C compiler default output file name... a.out >> > checking whether the C compiler works... yes >> > checking whether we are cross compiling... no >> > checking for suffix of executables... >> > checking for suffix of object files... o >> > checking whether we are using the GNU C compiler... yes >> > checking whether gcc accepts -g... yes >> > checking for gcc option to accept ISO C89... none needed >> > checking for gcc option to accept ISO C99... -std=gnu99 >> > checking for gcc -std=gnu99 option to accept ISO Standard C... >> > (cached) -std=gnu99 >> > checking how to run the C preprocessor... gcc -std=gnu99 -E >> > checking build system compiler gcc -std=gnu99... yes >> > checking for build system preprocessor... gcc -std=gnu99 -E >> > checking for build system executable suffix... >> > checking whether build system compiler is ANSI... yes >> > checking for build system compiler math library... -lm >> > checking for g++... g++ >> > checking whether we are using the GNU C++ compiler... yes >> > checking whether g++ accepts -g... yes >> > checking C++ compiler g++ -DNO_ASM -O3... no, program does not run >> > checking C++ compiler g++ -DNO_ASM -g -O2... no, program does not run >> > configure: error: C++ compiler not available, see config.log for details >> > >> > The options works fine on thier own >> > >> > I've opened a trac ticket for this >> > This fails with the current mpir-1.1.2 as well >> > In case your wondering why you may want build=none , its to get all the >> > asserts for maximum debugging >> > >> > Jason >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. 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/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
