[Bug c++/36248] New: configure: error: cannot compute suffix of object files: cannot compil

2008-05-16 Thread info at yourkit dot com
Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: info at yourkit dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36248

[Bug middle-end/36248] configure: error: cannot compute suffix of object files: cannot compil

2008-05-16 Thread info at yourkit dot com
--- Comment #2 from info at yourkit dot com 2008-05-16 17:20 --- Created an attachment (id=15646) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15646action=view) config.log with error I've attached config.log. It contains a message that libmpfr.so cannot be loaded, but --with-mpfr

[Bug middle-end/36248] configure: error: cannot compute suffix of object files: cannot compil

2008-05-16 Thread info at yourkit dot com
--- Comment #3 from info at yourkit dot com 2008-05-16 19:00 --- Actually it's a dumb shit that make doesn't modify LD_LIBRARY_PATH. It will be so naturally... For what purpose do we specify --with-mpfr-lib specified? *** This bug has been marked as a duplicate of 35577

[Bug bootstrap/35577] configure: error: cannot compute suffix of object files

2008-05-16 Thread info at yourkit dot com
--- Comment #7 from info at yourkit dot com 2008-05-16 19:00 --- *** Bug 36248 has been marked as a duplicate of this bug. *** -- info at yourkit dot com changed: What|Removed |Added

[Bug libstdc++/28125] Cannot build cross compiler for Solaris: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES

2006-06-23 Thread info at yourkit dot com
--- Comment #2 from info at yourkit dot com 2006-06-23 10:31 --- I've charged target from i386-pc-solaris2.10 to i386-pc-solaris2.9 and successfully built cross-compiler, but the resulting compiler cannot produce 64bit binaries (as expected, because Solaris9 on Intel is a 32bit). I

[Bug other/25035] [4.1/4.2 regression] libssp causes a failure with cross compilers

2006-06-23 Thread info at yourkit dot com
--- Comment #9 from info at yourkit dot com 2006-06-23 12:09 --- I can confirm this bug. target=i386-pc-solaris2.10; host=i386-pc-linux-gnu; GCC 4.1.1; BinUtils 2.16.1 Checking multilib configuration... /bin/sh /home/anton/tmp/gcc/gcc-4.1.1/mkinstalldirs i386-pc-solaris2.10/libssp

[Bug libstdc++/28125] Cannot build cross compiler for Solaris: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES

2006-06-23 Thread info at yourkit dot com
--- Comment #3 from info at yourkit dot com 2006-06-23 12:28 --- I've discovered that if only C language is specified and --disable-libssp is added (to work around bug #25035) then cross complier can be successfully built. So the problem somewehere in C++ part. -- http

[Bug bootstrap/28101] Cannot build cross compiler for Solaris: values-Xa.o: No such file: No such file or directory

2006-06-21 Thread info at yourkit dot com
--- Comment #1 from info at yourkit dot com 2006-06-21 08:10 --- All librarues from /usr/lib (from target Solaris machine) should be copied to $PREFIX/sysroot/usr/lib -- info at yourkit dot com changed: What|Removed |Added

[Bug libstdc++/28125] New: Cannot build cross compiler for Solaris: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES

2006-06-21 Thread info at yourkit dot com
Severity: critical Priority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: info at yourkit dot com GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: i386-pc-solaris2.10 http://gcc.gnu.org/bugzilla/show_bug.cgi?id

[Bug libstdc++/28125] Cannot build cross compiler for Solaris: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES

2006-06-21 Thread info at yourkit dot com
--- Comment #1 from info at yourkit dot com 2006-06-21 16:03 --- Created an attachment (id=11721) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11721action=view) config.log I have attached config.log file from directory /home/anton/tmp/gcc/objdir/i386-pc-solaris2.10/libstdc++v3

[Bug libstdc++/26810] error when building cross-compiler

2006-06-21 Thread info at yourkit dot com
--- Comment #2 from info at yourkit dot com 2006-06-21 16:07 --- I'm experienced with the similar bug #28125. Please help, I'm ready to provide any additinal information. -- info at yourkit dot com changed: What|Removed |Added

[Bug c++/28097] New: error: �PATH_MAX� undeclared (first use in this function) when building cross compiler

2006-06-20 Thread info at yourkit dot com
ReportedBy: info at yourkit dot com GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: sparc-sun-solaris2.9 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28097

[Bug c++/28098] New: error: �PATH_MAX� undeclared (first use in this function) when building cross compiler

2006-06-20 Thread info at yourkit dot com
ReportedBy: info at yourkit dot com GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: sparc-sun-solaris2.9 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28098

[Bug bootstrap/28101] New: Cannot build cross compiler for Solaris: values-Xa.o: No such file: No such file or directory

2006-06-20 Thread info at yourkit dot com
: gcc Version: 4.1.1 Status: UNCONFIRMED Severity: critical Priority: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: info at yourkit dot com GCC host triplet: x86_64-unknown-linux-gnu GCC target

[Bug target/28097] error: �PATH_MAX� undeclared (first use in this function) when building cross compiler

2006-06-20 Thread info at yourkit dot com
--- Comment #2 from info at yourkit dot com 2006-06-20 16:38 --- Actually the problem was solved (in our case) by copying header files from Solaris machine to $PREFIX/sysroot/usr/include dictory and additing --with-sysroot=$PREFIX/sysroot to configuration options. Binutils also need

[Bug target/21277] Runtime error with C++ shared library and --disable-shared

2005-05-02 Thread info at yourkit dot com
--- Additional Comments From info at yourkit dot com 2005-05-02 06:59 --- First of all, thank you all for the suggestions. libstdc++'s configure contains the docs for --with-pic: I'm sorry, I'm not a gcc configuration guru :), and all that I was doing was building gcc via its

[Bug target/21277] Runtime error with C++ shared library and --disable-shared

2005-05-02 Thread info at yourkit dot com
--- Additional Comments From info at yourkit dot com 2005-05-02 07:19 --- I'd be happy to try if you'd tell me where to switch this option g++ -m64 -fPIC q.cpp -shared -mimpure-text -o libq.so It doesn't help -- the same problem -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id

[Bug target/21277] Runtime error with C++ shared library and --disable-shared

2005-05-02 Thread info at yourkit dot com
--- Additional Comments From info at yourkit dot com 2005-05-02 07:23 --- Eric, maybe you can tell me more how/where to apply this --with-pic option? I was googling myself, but found nothing about this option. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21277

[Bug target/21277] Runtime error with C++ shared library and --disable-shared

2005-05-02 Thread info at yourkit dot com
--- Additional Comments From info at yourkit dot com 2005-05-02 07:33 --- readelf -r libq.so | grep R_SPARC_WDISP30gives the following: a73c 004f0007 R_SPARC_WDISP30 abort + 0 a764 004f0007 R_SPARC_WDISP30 abort + 0

[Bug target/21277] Runtime error with C++ shared library and --disable-shared

2005-05-02 Thread info at yourkit dot com
--- Additional Comments From info at yourkit dot com 2005-05-02 08:15 --- OK, the fundamental problem is that you're trying to build shared libraries with a compiler configured with --disable-shared. That's not really intended (and might cause problems for exception propagation in C

[Bug target/21277] Runtime error with C++ shared library and --disable-shared

2005-05-02 Thread info at yourkit dot com
--- Additional Comments From info at yourkit dot com 2005-05-02 09:25 --- 5 MB uncompressed for 32-bit, 6 MB uncompressed for 64-bit! Of course it's not a show stopper, but given 2-3M total packed size of the distribution, we'd prefer not to double it. Furthermore, the approach always

[Bug target/21277] Runtime error with C++ shared library and --disable-shared

2005-05-02 Thread info at yourkit dot com
--- Additional Comments From info at yourkit dot com 2005-05-02 09:46 --- Adding --with-pic to the command line of gcc's configure helped. Thanks a lot, Eric! -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21277

[Bug target/21277] Runtime error with C++ shared library and --disable-shared

2005-05-02 Thread info at yourkit dot com
--- Additional Comments From info at yourkit dot com 2005-05-02 11:10 --- Thanks a lot, Eric! Andrew deserves them too. No doubt :) I'm sorry. And, again, not using a shared libgcc on Solaris means that exceptions cannot be propagated across shared libraries; that's why g

[Bug c++/21277] New: gcc 4.0 fails to statically link on Solaris SPARC 64 bit

2005-04-29 Thread info at yourkit dot com
Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: info at yourkit dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21277

[Bug c++/21277] gcc 4.0 fails to statically link on Solaris SPARC 64 bit

2005-04-29 Thread info at yourkit dot com
--- Additional Comments From info at yourkit dot com 2005-04-29 07:38 --- Forgot to say: binutils 2.15 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21277

[Bug c++/21277] gcc 4.0 fails to statically link on Solaris SPARC 64 bit

2005-04-29 Thread info at yourkit dot com
--- Additional Comments From info at yourkit dot com 2005-04-29 08:27 --- So you are not building with --with-pic? I'm sorry, where and when should I specify this option? gcc's configure --help does not return this flag among possible options. -- What|Removed

[Bug c++/21277] gcc 4.0 fails to statically link on Solaris SPARC 64 bit

2005-04-29 Thread info at yourkit dot com
--- Additional Comments From info at yourkit dot com 2005-04-29 15:25 --- I have re-installed the recommended at http://gcc.gnu.org/install/specific.html binutils (branch binutils-2_15-branch from CVS) AND even re-compiled gcc after that. It doesn't help - the problem remains