Fwd: [protobuf] Re: Issue with protobuf-2.3.0: Problem running 'configure' on Solaris 10
-- Forwarded message -- From: Steven Ong stevenong2...@gmail.com Date: Sat, Mar 20, 2010 at 9:32 PM Subject: Re: [protobuf] Re: Issue with protobuf-2.3.0: Problem running 'configure' on Solaris 10 To: Kenton Varda ken...@google.com Hi all, After taking the second look of the 'config.log', I found that I missed this line: ld: fatal: file values-Xa.o: open failed: No such file or directory ...And after googling, I found that I need to install the sun package: SUNWarc ** Sorry, I felt really stupid at this point ** ... Now, I am running into a new error: GNU C (GCC) version 4.3.3 (i386-pc-solaris2.8) compiled by GNU C version 4.3.3, GMP version 4.2.2, MPFR version 2.3.1. GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 Compiler executable checksum: d69afb5aa27ddb6cc8ec83352dafa664 COLLECT_GCC_OPTIONS='-o' 'conftest' '-v' '-mtune=i386' /opt/csw/bin/gas -v --traditional-format -V -Qy -s -o /var/tmp//ccSaYWux.o /var/tmp//ccGvFHch.s GNU assembler version 2.19 (i386-pc-solaris2.8) using BFD version (GNU Binutils) 2.19 COMPILER_PATH=/opt/csw/gcc4/libexec/gcc/i386-pc-solaris2.8/4.3.3/:/opt/csw/gcc4/libexec/gcc/i386-pc-solaris2.8/4.3.3/:/opt/csw/gcc4/libexec/gcc/i386-pc-solaris2.8/:/opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/:/opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/:/usr/ccs/bin/ LIBRARY_PATH=/opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/:/usr/ccs/lib/:/opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/../../../:/lib/:/usr/lib/ COLLECT_GCC_OPTIONS='-o' 'conftest' '-v' '-mtune=i386' /usr/ccs/bin/ld -V -Y P,/usr/ccs/lib:/usr/lib -Qy -o conftest /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/crt1.o /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/crti.o /usr/ccs/lib/values-Xa.o /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/crtbegin.o -L/opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3 -L/usr/ccs/lib -L/opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/../../.. /var/tmp//ccSaYWux.o -lgcc -lgcc_eh -lc -lgcc -lgcc_eh /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/crtend.o /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/crtn.o ld: Software Generation Utilities - Solaris Link Editors: 5.11-1.1652 configure:3104: $? = 0 configure:3128: result: configure:3134: checking for suffix of object files configure:3160: gcc -c -v conftest.c 5 Using built-in specs. Target: i386-pc-solaris2.8 Configured with: ../gcc-4.3.3/configure --prefix=/opt/csw/gcc4 --exec-prefix=/opt/csw/gcc4 --with-gnu-as --with-as=/opt/csw/bin/gas --without-gnu-ld --with-ld=/usr/ccs/bin/ld --enable-nls --with-included-gettext --with-libiconv-prefix=/opt/csw --with-x --with-mpfr=/opt/csw --with-gmp=/opt/csw --enable-java-awt=xlib --enable-libada --enable-libssp --enable-objc-gc --enable-threads=posix --enable-stage1-languages=c --enable-languages=ada,c,c++,fortran,java,objc Thread model: posix gcc version 4.3.3 (GCC) COLLECT_GCC_OPTIONS='-c' '-v' '-mtune=i386' /opt/csw/gcc4/libexec/gcc/i386-pc-solaris2.8/4.3.3/cc1 -quiet -v conftest.c -quiet -dumpbase conftest.c -mtune=i386 -auxbase conftest -version -o /var/tmp//ccABOt9D.s ignoring nonexistent directory /usr/local/include ignoring nonexistent directory /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/../../../../i386-pc-solaris2.8/include #include ... search starts here: #include ... search starts here: /opt/csw/gcc4/include /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/include /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/include-fixed /usr/include End of search list. GNU C (GCC) version 4.3.3 (i386-pc-solaris2.8) compiled by GNU C version 4.3.3, GMP version 4.2.2, MPFR version 2.3.1. GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 Compiler executable checksum: d69afb5aa27ddb6cc8ec83352dafa664 COLLECT_GCC_OPTIONS='-c' '-v' '-mtune=i386' /opt/csw/bin/gas -v --traditional-format -V -Qy -s -o conftest.o /var/tmp//ccABOt9D.s GNU assembler version 2.19 (i386-pc-solaris2.8) using BFD version (GNU Binutils) 2.19 COMPILER_PATH=/opt/csw/gcc4/libexec/gcc/i386-pc-solaris2.8/4.3.3/:/opt/csw/gcc4/libexec/gcc/i386-pc-solaris2.8/4.3.3/:/opt/csw/gcc4/libexec/gcc/i386-pc-solaris2.8/:/opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/:/opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/:/usr/ccs/bin/ LIBRARY_PATH=/opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/:/usr/ccs/lib/:/opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.3.3/../../../:/lib/:/usr/lib/ COLLECT_GCC_OPTIONS='-c' '-v' '-mtune=i386' configure:3163: $? = 0 configure:3186: result: o configure:3190: checking whether we are using the GNU C compiler configure:3219: gcc -c -v conftest.c 5 Using built-in specs. Target: i386-pc-solaris2.8 Configured with: ../gcc-4.3.3/configure --prefix=/opt/csw/gcc4 --exec-prefix=/opt/csw/gcc4 --with-gnu-as --with-as=/opt/csw/bin/gas --without-gnu-ld --with-ld=/usr/ccs/bin/ld --enable-nls --with-included-gettext --with-libiconv-prefix=/opt/csw --with-x --with-mpfr=/opt/csw --with-gmp=/opt/csw --enable-java-awt=xlib --enable-libada --enable-libssp --enable-objc-gc
Re: [protobuf] Re: Issue with protobuf-2.3.0: Problem running 'configure' on Solaris 10
You might be able to solve this by setting LD=gcc, like:
./configure LD=gcc
On Sun, Mar 14, 2010 at 4:00 PM, Steven Ong stevenong2...@gmail.com wrote:
One more thing...
I discovered that the whole root cause is as the following:
Although the code was compiled by CSW gcc4, Sun's linker (from /usr/bin/ld)
was invoked to link the compiled code. Apparently, there are incompatibility
between the code compiled by gcc and the one that Sun's ld can take, hence,
it unable to link...
Hi Maciej,
Have you ever run into this issue with CSW? How did you resolve it?
Thanks all,
Steven
On Sun, Mar 14, 2010 at 4:09 PM, Steven Ong stevenong2...@gmail.comwrote:
Hi all,
I just installed a new box with openSolaris (0906). This time I also in
stalled gcc version 4.3.4. When I run configure it's failed, and here is the
excerpt from config.log:
Target: i386-pc-solaris2.10
Configured with: /export/medusa/dclarke/build/GCC/gcc-4.3.4/configure
--build=i386-pc-solaris2.10 --with-gnu-as --with-as=/opt/csw/bin/gas
--without-gnu-ld --with-ld=/usr/ccs/bin/ld --with-cpu-32=i386
--with-cpu-64=opteron --with-arch-32=i386 --with-arch-64=opteron
--enable-stage1-languages=c --enable-nls --with-libiconv-prefix=/opt/csw
--enable-threads=posix --prefix=/opt/csw/gcc4 --with-local-prefix=/opt/csw
--enable-shared --enable-multilib --with-included-gettext --with-system-zlib
--with-gmp=/opt/csw --with-mpfr=/opt/csw
--enable-languages=c,c++,objc,fortran --enable-bootstrap
Thread model: posix
gcc version 4.3.4 (GCC)
configure:2934: $? = 0
configure:2941: gcc -V 5
gcc: '-V' option must have argument
configure:2944: $? = 1
configure:2967: checking for C compiler default output file name
configure:2994: gccconftest.c 5
ld: fatal: file crt1.o: open failed: No such file or directory
collect2: ld returned 1 exit status
configure:2997: $? = 1
configure:3035: result:
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME Protocol Buffers
| #define PACKAGE_TARNAME protobuf
| #define PACKAGE_VERSION 2.3.0
| #define PACKAGE_STRING Protocol Buffers 2.3.0
| #define PACKAGE_BUGREPORT protobuf@googlegroups.com
| #define PACKAGE protobuf
| #define VERSION 2.3.0
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:3041: error: C compiler cannot create executables
See `config.log' for more details.
Thanks in advance for your help
Steven
On Fri, Mar 12, 2010 at 8:25 AM, stevenong2007
stevenong2...@gmail.comwrote:
Hi,
Actually I am trying this on 2 different boxes: (1) Solaris 10 and (2)
Nexenta.
On (1) the gcc version was (gcc (GCC) 3.4.6)
On (2) the gcc version was (gcc version 4.2.3 (Ubuntu
4.2.3-2nexenta7) )
... And neither has worked.
I am really sorry for the confusion. Here is the excerpt from gtest/
config.log which I captured from (2) (The Nexenta box):
***
gcc version 4.2.3 (Ubuntu 4.2.3-2nexenta7)
configure:2769: $? = 0
configure:2776: gcc -V 5
gcc: '-V' option must have argument
configure:2779: $? = 1
configure:2802: checking for C compiler default output file name
configure:2829: gcc -m64 conftest.c 5
configure:2832: $? = 0
configure:2870: result: a.out
configure:2887: checking whether the C compiler works
configure:2897: ./a.out
./configure: line 2898: ./a.out: cannot execute binary file
configure:2900: $? = 126
configure:2909: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
***
... Kenton int the previous reply pointed it out that the '-m64' flag
might be the one causing problem. I'm going to try it out tonight when
I get home.
Also, thanks Maciej for you info in the previous reply about the newer
version of gcc. I will give it a try a let you know.
Again, sorry for all the confusion and thanks for all the respond.
Regards,
Steven
On Mar 12, 6:11 am, Maciej Bliziński blizin...@google.com wrote:
On Mar 11, 3:44 am, stevenong2007 stevenong2...@gmail.com wrote:
I am running Nexenta (Debian on top of Solaris 11)
Allright, that changes a lot of things. I was assuming you were
running Solaris 10 or OpenSolaris. There's something I don't
understand here though -- if you're using nexenta, why is your gcc so
old?
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to
protobuf+unsubscr...@googlegroups.comprotobuf%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/protobuf?hl=en.
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to
Re: [protobuf] Re: Issue with protobuf-2.3.0: Problem running 'configure' on Solaris 10
Hi all,
I just installed a new box with openSolaris (0906). This time I also in
stalled gcc version 4.3.4. When I run configure it's failed, and here is the
excerpt from config.log:
Target: i386-pc-solaris2.10
Configured with: /export/medusa/dclarke/build/GCC/gcc-4.3.4/configure
--build=i386-pc-solaris2.10 --with-gnu-as --with-as=/opt/csw/bin/gas
--without-gnu-ld --with-ld=/usr/ccs/bin/ld --with-cpu-32=i386
--with-cpu-64=opteron --with-arch-32=i386 --with-arch-64=opteron
--enable-stage1-languages=c --enable-nls --with-libiconv-prefix=/opt/csw
--enable-threads=posix --prefix=/opt/csw/gcc4 --with-local-prefix=/opt/csw
--enable-shared --enable-multilib --with-included-gettext --with-system-zlib
--with-gmp=/opt/csw --with-mpfr=/opt/csw
--enable-languages=c,c++,objc,fortran --enable-bootstrap
Thread model: posix
gcc version 4.3.4 (GCC)
configure:2934: $? = 0
configure:2941: gcc -V 5
gcc: '-V' option must have argument
configure:2944: $? = 1
configure:2967: checking for C compiler default output file name
configure:2994: gccconftest.c 5
ld: fatal: file crt1.o: open failed: No such file or directory
collect2: ld returned 1 exit status
configure:2997: $? = 1
configure:3035: result:
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME Protocol Buffers
| #define PACKAGE_TARNAME protobuf
| #define PACKAGE_VERSION 2.3.0
| #define PACKAGE_STRING Protocol Buffers 2.3.0
| #define PACKAGE_BUGREPORT protobuf@googlegroups.com
| #define PACKAGE protobuf
| #define VERSION 2.3.0
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:3041: error: C compiler cannot create executables
See `config.log' for more details.
Thanks in advance for your help
Steven
On Fri, Mar 12, 2010 at 8:25 AM, stevenong2007 stevenong2...@gmail.comwrote:
Hi,
Actually I am trying this on 2 different boxes: (1) Solaris 10 and (2)
Nexenta.
On (1) the gcc version was (gcc (GCC) 3.4.6)
On (2) the gcc version was (gcc version 4.2.3 (Ubuntu
4.2.3-2nexenta7) )
... And neither has worked.
I am really sorry for the confusion. Here is the excerpt from gtest/
config.log which I captured from (2) (The Nexenta box):
***
gcc version 4.2.3 (Ubuntu 4.2.3-2nexenta7)
configure:2769: $? = 0
configure:2776: gcc -V 5
gcc: '-V' option must have argument
configure:2779: $? = 1
configure:2802: checking for C compiler default output file name
configure:2829: gcc -m64 conftest.c 5
configure:2832: $? = 0
configure:2870: result: a.out
configure:2887: checking whether the C compiler works
configure:2897: ./a.out
./configure: line 2898: ./a.out: cannot execute binary file
configure:2900: $? = 126
configure:2909: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
***
... Kenton int the previous reply pointed it out that the '-m64' flag
might be the one causing problem. I'm going to try it out tonight when
I get home.
Also, thanks Maciej for you info in the previous reply about the newer
version of gcc. I will give it a try a let you know.
Again, sorry for all the confusion and thanks for all the respond.
Regards,
Steven
On Mar 12, 6:11 am, Maciej Bliziński blizin...@google.com wrote:
On Mar 11, 3:44 am, stevenong2007 stevenong2...@gmail.com wrote:
I am running Nexenta (Debian on top of Solaris 11)
Allright, that changes a lot of things. I was assuming you were
running Solaris 10 or OpenSolaris. There's something I don't
understand here though -- if you're using nexenta, why is your gcc so
old?
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to
protobuf+unsubscr...@googlegroups.comprotobuf%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/protobuf?hl=en.
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to
protobuf+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] Re: Issue with protobuf-2.3.0: Problem running 'configure' on Solaris 10
One more thing...
I discovered that the whole root cause is as the following:
Although the code was compiled by CSW gcc4, Sun's linker (from /usr/bin/ld)
was invoked to link the compiled code. Apparently, there are incompatibility
between the code compiled by gcc and the one that Sun's ld can take, hence,
it unable to link...
Hi Maciej,
Have you ever run into this issue with CSW? How did you resolve it?
Thanks all,
Steven
On Sun, Mar 14, 2010 at 4:09 PM, Steven Ong stevenong2...@gmail.com wrote:
Hi all,
I just installed a new box with openSolaris (0906). This time I also in
stalled gcc version 4.3.4. When I run configure it's failed, and here is the
excerpt from config.log:
Target: i386-pc-solaris2.10
Configured with: /export/medusa/dclarke/build/GCC/gcc-4.3.4/configure
--build=i386-pc-solaris2.10 --with-gnu-as --with-as=/opt/csw/bin/gas
--without-gnu-ld --with-ld=/usr/ccs/bin/ld --with-cpu-32=i386
--with-cpu-64=opteron --with-arch-32=i386 --with-arch-64=opteron
--enable-stage1-languages=c --enable-nls --with-libiconv-prefix=/opt/csw
--enable-threads=posix --prefix=/opt/csw/gcc4 --with-local-prefix=/opt/csw
--enable-shared --enable-multilib --with-included-gettext --with-system-zlib
--with-gmp=/opt/csw --with-mpfr=/opt/csw
--enable-languages=c,c++,objc,fortran --enable-bootstrap
Thread model: posix
gcc version 4.3.4 (GCC)
configure:2934: $? = 0
configure:2941: gcc -V 5
gcc: '-V' option must have argument
configure:2944: $? = 1
configure:2967: checking for C compiler default output file name
configure:2994: gccconftest.c 5
ld: fatal: file crt1.o: open failed: No such file or directory
collect2: ld returned 1 exit status
configure:2997: $? = 1
configure:3035: result:
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME Protocol Buffers
| #define PACKAGE_TARNAME protobuf
| #define PACKAGE_VERSION 2.3.0
| #define PACKAGE_STRING Protocol Buffers 2.3.0
| #define PACKAGE_BUGREPORT protobuf@googlegroups.com
| #define PACKAGE protobuf
| #define VERSION 2.3.0
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:3041: error: C compiler cannot create executables
See `config.log' for more details.
Thanks in advance for your help
Steven
On Fri, Mar 12, 2010 at 8:25 AM, stevenong2007 stevenong2...@gmail.comwrote:
Hi,
Actually I am trying this on 2 different boxes: (1) Solaris 10 and (2)
Nexenta.
On (1) the gcc version was (gcc (GCC) 3.4.6)
On (2) the gcc version was (gcc version 4.2.3 (Ubuntu
4.2.3-2nexenta7) )
... And neither has worked.
I am really sorry for the confusion. Here is the excerpt from gtest/
config.log which I captured from (2) (The Nexenta box):
***
gcc version 4.2.3 (Ubuntu 4.2.3-2nexenta7)
configure:2769: $? = 0
configure:2776: gcc -V 5
gcc: '-V' option must have argument
configure:2779: $? = 1
configure:2802: checking for C compiler default output file name
configure:2829: gcc -m64 conftest.c 5
configure:2832: $? = 0
configure:2870: result: a.out
configure:2887: checking whether the C compiler works
configure:2897: ./a.out
./configure: line 2898: ./a.out: cannot execute binary file
configure:2900: $? = 126
configure:2909: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
***
... Kenton int the previous reply pointed it out that the '-m64' flag
might be the one causing problem. I'm going to try it out tonight when
I get home.
Also, thanks Maciej for you info in the previous reply about the newer
version of gcc. I will give it a try a let you know.
Again, sorry for all the confusion and thanks for all the respond.
Regards,
Steven
On Mar 12, 6:11 am, Maciej Bliziński blizin...@google.com wrote:
On Mar 11, 3:44 am, stevenong2007 stevenong2...@gmail.com wrote:
I am running Nexenta (Debian on top of Solaris 11)
Allright, that changes a lot of things. I was assuming you were
running Solaris 10 or OpenSolaris. There's something I don't
understand here though -- if you're using nexenta, why is your gcc so
old?
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to
protobuf+unsubscr...@googlegroups.comprotobuf%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/protobuf?hl=en.
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to
protobuf+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue with protobuf-2.3.0: Problem running 'configure' on Solaris 10
Hi, Actually I am trying this on 2 different boxes: (1) Solaris 10 and (2) Nexenta. On (1) the gcc version was (gcc (GCC) 3.4.6) On (2) the gcc version was (gcc version 4.2.3 (Ubuntu 4.2.3-2nexenta7) ) ... And neither has worked. I am really sorry for the confusion. Here is the excerpt from gtest/ config.log which I captured from (2) (The Nexenta box): *** gcc version 4.2.3 (Ubuntu 4.2.3-2nexenta7) configure:2769: $? = 0 configure:2776: gcc -V 5 gcc: '-V' option must have argument configure:2779: $? = 1 configure:2802: checking for C compiler default output file name configure:2829: gcc -m64 conftest.c 5 configure:2832: $? = 0 configure:2870: result: a.out configure:2887: checking whether the C compiler works configure:2897: ./a.out ./configure: line 2898: ./a.out: cannot execute binary file configure:2900: $? = 126 configure:2909: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details. *** ... Kenton int the previous reply pointed it out that the '-m64' flag might be the one causing problem. I'm going to try it out tonight when I get home. Also, thanks Maciej for you info in the previous reply about the newer version of gcc. I will give it a try a let you know. Again, sorry for all the confusion and thanks for all the respond. Regards, Steven On Mar 12, 6:11 am, Maciej Bliziński blizin...@google.com wrote: On Mar 11, 3:44 am, stevenong2007 stevenong2...@gmail.com wrote: I am running Nexenta (Debian on top of Solaris 11) Allright, that changes a lot of things. I was assuming you were running Solaris 10 or OpenSolaris. There's something I don't understand here though -- if you're using nexenta, why is your gcc so old? -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] Re: Issue with protobuf-2.3.0: Problem running 'configure' on Solaris 10
No, you can't skip configuring the gtest directory.
But why does your gcc produce executables that can't be executed? Is it the
-m64 flag that breaks them?
On Thu, Mar 11, 2010 at 6:19 PM, stevenong2007 stevenong2...@gmail.comwrote:
Hi,
Thanks for your respond. Here is the excerpt from gtest/config.log
that I think relevant to this issue...
***
gcc version 4.2.3 (Ubuntu 4.2.3-2nexenta7)
configure:2769: $? = 0
configure:2776: gcc -V 5
gcc: '-V' option must have argument
configure:2779: $? = 1
configure:2802: checking for C compiler default output file name
configure:2829: gcc -m64 conftest.c 5
configure:2832: $? = 0
configure:2870: result: a.out
configure:2887: checking whether the C compiler works
configure:2897: ./a.out
./configure: line 2898: ./a.out: cannot execute binary file
configure:2900: $? = 126
configure:2909: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
***
...One more question: Is it possible to tell 'configure' to skip the
'gtest' directory? (I've tried '--without-gtest' and --'without-system-
gtest' - neither work)
Thanks in advance for your help.
Steven
On Mar 10, 11:18 pm, Kenton Varda ken...@google.com wrote:
Oops, it looks like it's actually gtest/config.log that you need to look
at,
since the failure happened when configuring the gtest sub-package.
On Wed, Mar 10, 2010 at 7:44 PM, stevenong2007 stevenong2...@gmail.com
wrote:
I am running Nexenta (Debian on top of Solaris 11), and the gcc
version is:
gcc (GCC) 4.2.3 (Ubuntu 4.2.3-2nexenta7)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There
is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
Also, here is the excerpt from config.log...
configure:16902: checking whether to check for GCC pthread/shared
inconsistencies
configure:16925: /usr/bin/gcc-4.2 -o conftest -shared -fPIC -Wl,-
z,defs -m64 -D_REENTRANT -pthreads conftest.c 5
configure:16931: $? = 0
configure:16952: result: yes
configure:16958: checking whether -pthread is sufficient with -shared
configure:16983: /usr/bin/gcc-4.2 -o conftest -shared -fPIC -Wl,-
z,defs -m64 -D_REENTRANT -pthreads conftest.c 5
/var/tmp//cc9WaO7o.o: In function `main':
conftest.c:(.text+0x11): undefined reference to `pthread_join'
conftest.c:(.text+0x1b): undefined reference to `pthread_attr_init'
conftest.c:(.text+0x20): undefined reference to `_getfp'
conftest.c:(.text+0x36): undefined reference to
`__pthread_cleanup_push'
conftest.c:(.text+0x4f): undefined reference to `pthread_create'
conftest.c:(.text+0x5d): undefined reference to
`__pthread_cleanup_pop'
collect2: ld returned 1 exit status
configure:16989: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME Protocol Buffers
| #define PACKAGE_TARNAME protobuf
| #define PACKAGE_VERSION 2.3.0
| #define PACKAGE_STRING Protocol Buffers 2.3.0
| #define PACKAGE_BUGREPORT protobuf@googlegroups.com
| #define PACKAGE protobuf
| #define VERSION 2.3.0
| #define _GNU_SOURCE 1
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define __EXTENSIONS__ 1
| #define _POSIX_PTHREAD_SEMANTICS 1
| #define _TANDEM_SOURCE 1
| #define HAVE_DLFCN_H 1
| #define LT_OBJDIR .libs/
| #define STDC_HEADERS 1
| #define HAVE_FCNTL_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_LIMITS_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_FTRUNCATE 1
| #define HAVE_MEMSET 1
| #define HAVE_MKDIR 1
| #define HAVE_STRCHR 1
| #define HAVE_STRERROR 1
| #define HAVE_STRTOL 1
| /* end confdefs.h. */
| #include pthread.h
| int
| main ()
| {
| pthread_t th; pthread_join(th, 0);
| pthread_attr_init(0); pthread_cleanup_push(0, 0);
| pthread_create(0,0,0,0); pthread_cleanup_pop(0);
| ;
| return 0;
| }
configure:17010: result: no
configure:17020: checking whether -lpthread fixes that
configure:17046: /usr/bin/gcc-4.2 -o conftest -shared -fPIC -Wl,-
z,defs -m64 -D_REENTRANT -pthreads conftest.c -lpthread 5
configure:17052: $? = 0
configure:17070: result: yes
configure:17179: checking the location of hash_map
configure:17223: g++ -c -g -DNDEBUG -m64 conftest.cpp 5
configure:17229: $? = 0
configure:17287: result: tr1/unordered_map
configure:17456: creating ./config.status
## -- ##
## Running config.status. ##
## -- ##
[protobuf] Re: Issue with protobuf-2.3.0: Problem running 'configure' on Solaris 10
I am running Nexenta (Debian on top of Solaris 11), and the gcc
version is:
gcc (GCC) 4.2.3 (Ubuntu 4.2.3-2nexenta7)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There
is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
Also, here is the excerpt from config.log...
configure:16902: checking whether to check for GCC pthread/shared
inconsistencies
configure:16925: /usr/bin/gcc-4.2 -o conftest -shared -fPIC -Wl,-
z,defs -m64 -D_REENTRANT -pthreads conftest.c 5
configure:16931: $? = 0
configure:16952: result: yes
configure:16958: checking whether -pthread is sufficient with -shared
configure:16983: /usr/bin/gcc-4.2 -o conftest -shared -fPIC -Wl,-
z,defs -m64 -D_REENTRANT -pthreads conftest.c 5
/var/tmp//cc9WaO7o.o: In function `main':
conftest.c:(.text+0x11): undefined reference to `pthread_join'
conftest.c:(.text+0x1b): undefined reference to `pthread_attr_init'
conftest.c:(.text+0x20): undefined reference to `_getfp'
conftest.c:(.text+0x36): undefined reference to
`__pthread_cleanup_push'
conftest.c:(.text+0x4f): undefined reference to `pthread_create'
conftest.c:(.text+0x5d): undefined reference to
`__pthread_cleanup_pop'
collect2: ld returned 1 exit status
configure:16989: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME Protocol Buffers
| #define PACKAGE_TARNAME protobuf
| #define PACKAGE_VERSION 2.3.0
| #define PACKAGE_STRING Protocol Buffers 2.3.0
| #define PACKAGE_BUGREPORT protobuf@googlegroups.com
| #define PACKAGE protobuf
| #define VERSION 2.3.0
| #define _GNU_SOURCE 1
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define __EXTENSIONS__ 1
| #define _POSIX_PTHREAD_SEMANTICS 1
| #define _TANDEM_SOURCE 1
| #define HAVE_DLFCN_H 1
| #define LT_OBJDIR .libs/
| #define STDC_HEADERS 1
| #define HAVE_FCNTL_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_LIMITS_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_FTRUNCATE 1
| #define HAVE_MEMSET 1
| #define HAVE_MKDIR 1
| #define HAVE_STRCHR 1
| #define HAVE_STRERROR 1
| #define HAVE_STRTOL 1
| /* end confdefs.h. */
| #include pthread.h
| int
| main ()
| {
| pthread_t th; pthread_join(th, 0);
| pthread_attr_init(0); pthread_cleanup_push(0, 0);
| pthread_create(0,0,0,0); pthread_cleanup_pop(0);
| ;
| return 0;
| }
configure:17010: result: no
configure:17020: checking whether -lpthread fixes that
configure:17046: /usr/bin/gcc-4.2 -o conftest -shared -fPIC -Wl,-
z,defs -m64 -D_REENTRANT -pthreads conftest.c -lpthread 5
configure:17052: $? = 0
configure:17070: result: yes
configure:17179: checking the location of hash_map
configure:17223: g++ -c -g -DNDEBUG -m64 conftest.cpp 5
configure:17229: $? = 0
configure:17287: result: tr1/unordered_map
configure:17456: creating ./config.status
## -- ##
## Running config.status. ##
## -- ##
This file was extended by Protocol Buffers config.status 2.3.0, which
was
generated by GNU Autoconf 2.61. Invocation command line was
CONFIG_FILES=
CONFIG_HEADERS =
CONFIG_LINKS=
CONFIG_COMMANDS =
$ ./config.status
on ongs-11
config.status:926: creating Makefile
config.status:926: creating src/Makefile
config.status:926: creating protobuf.pc
config.status:926: creating protobuf-lite.pc
config.status:926: creating config.h
config.status:1178: config.h is unchanged
config.status:1225: executing depfiles commands
config.status:1225: executing libtool commands
configure:19970: === configuring in gtest (/projects/
protoc-2.3.0SrcBuildArchive/protobuf-2.3.0/gtest)
configure:20073: running /bin/sh ./configure '--prefix=/usr/local'
'CC=/usr/bin/gcc-4.2' --cache-file=/dev/null --srcdir=.
configure:20078: error: ./configure failed for gtest
Thanks in advance for your help.
Steven
On Mar 3, 1:57 pm, Monty Taylor mord...@inaugust.com wrote:
Hi Steven!
If you're running Solaris 10, I HIGHLY recommend the use of Sun Studio
instead of GCC. GCC shipped with Solaris is ludicrously old and has issues.
If you cannot, for some reason, use Sun Studio instead, I highly
recommend installing a recent gcc (4.2 or later) I believe there is one
in blastwave.
We (the Drizzle project have had nothing but nightmares with gcc on
solaris and C++ - and we even worked for Sun until just recently)
However - config.log is going to be the place to look if you do want to
try to ferret out this problem. I wouldn't hold my breath though.
Monty
On 03/03/2010 11:03 AM, Kenton Varda wrote:
Please check config.log for a more detailed error message.
On Wed, Mar 3, 2010 at 7:43 AM, Steven Ong stevenong2...@gmail.com
mailto:stevenong2...@gmail.com wrote:
Hi
Re: [protobuf] Re: Issue with protobuf-2.3.0: Problem running 'configure' on Solaris 10
Oops, it looks like it's actually gtest/config.log that you need to look at,
since the failure happened when configuring the gtest sub-package.
On Wed, Mar 10, 2010 at 7:44 PM, stevenong2007 stevenong2...@gmail.comwrote:
I am running Nexenta (Debian on top of Solaris 11), and the gcc
version is:
gcc (GCC) 4.2.3 (Ubuntu 4.2.3-2nexenta7)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There
is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
Also, here is the excerpt from config.log...
configure:16902: checking whether to check for GCC pthread/shared
inconsistencies
configure:16925: /usr/bin/gcc-4.2 -o conftest -shared -fPIC -Wl,-
z,defs -m64 -D_REENTRANT -pthreads conftest.c 5
configure:16931: $? = 0
configure:16952: result: yes
configure:16958: checking whether -pthread is sufficient with -shared
configure:16983: /usr/bin/gcc-4.2 -o conftest -shared -fPIC -Wl,-
z,defs -m64 -D_REENTRANT -pthreads conftest.c 5
/var/tmp//cc9WaO7o.o: In function `main':
conftest.c:(.text+0x11): undefined reference to `pthread_join'
conftest.c:(.text+0x1b): undefined reference to `pthread_attr_init'
conftest.c:(.text+0x20): undefined reference to `_getfp'
conftest.c:(.text+0x36): undefined reference to
`__pthread_cleanup_push'
conftest.c:(.text+0x4f): undefined reference to `pthread_create'
conftest.c:(.text+0x5d): undefined reference to
`__pthread_cleanup_pop'
collect2: ld returned 1 exit status
configure:16989: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME Protocol Buffers
| #define PACKAGE_TARNAME protobuf
| #define PACKAGE_VERSION 2.3.0
| #define PACKAGE_STRING Protocol Buffers 2.3.0
| #define PACKAGE_BUGREPORT protobuf@googlegroups.com
| #define PACKAGE protobuf
| #define VERSION 2.3.0
| #define _GNU_SOURCE 1
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define __EXTENSIONS__ 1
| #define _POSIX_PTHREAD_SEMANTICS 1
| #define _TANDEM_SOURCE 1
| #define HAVE_DLFCN_H 1
| #define LT_OBJDIR .libs/
| #define STDC_HEADERS 1
| #define HAVE_FCNTL_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_LIMITS_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_FTRUNCATE 1
| #define HAVE_MEMSET 1
| #define HAVE_MKDIR 1
| #define HAVE_STRCHR 1
| #define HAVE_STRERROR 1
| #define HAVE_STRTOL 1
| /* end confdefs.h. */
| #include pthread.h
| int
| main ()
| {
| pthread_t th; pthread_join(th, 0);
| pthread_attr_init(0); pthread_cleanup_push(0, 0);
| pthread_create(0,0,0,0); pthread_cleanup_pop(0);
| ;
| return 0;
| }
configure:17010: result: no
configure:17020: checking whether -lpthread fixes that
configure:17046: /usr/bin/gcc-4.2 -o conftest -shared -fPIC -Wl,-
z,defs -m64 -D_REENTRANT -pthreads conftest.c -lpthread 5
configure:17052: $? = 0
configure:17070: result: yes
configure:17179: checking the location of hash_map
configure:17223: g++ -c -g -DNDEBUG -m64 conftest.cpp 5
configure:17229: $? = 0
configure:17287: result: tr1/unordered_map
configure:17456: creating ./config.status
## -- ##
## Running config.status. ##
## -- ##
This file was extended by Protocol Buffers config.status 2.3.0, which
was
generated by GNU Autoconf 2.61. Invocation command line was
CONFIG_FILES=
CONFIG_HEADERS =
CONFIG_LINKS=
CONFIG_COMMANDS =
$ ./config.status
on ongs-11
config.status:926: creating Makefile
config.status:926: creating src/Makefile
config.status:926: creating protobuf.pc
config.status:926: creating protobuf-lite.pc
config.status:926: creating config.h
config.status:1178: config.h is unchanged
config.status:1225: executing depfiles commands
config.status:1225: executing libtool commands
configure:19970: === configuring in gtest (/projects/
protoc-2.3.0SrcBuildArchive/protobuf-2.3.0/gtest)
configure:20073: running /bin/sh ./configure '--prefix=/usr/local'
'CC=/usr/bin/gcc-4.2' --cache-file=/dev/null --srcdir=.
configure:20078: error: ./configure failed for gtest
Thanks in advance for your help.
Steven
On Mar 3, 1:57 pm, Monty Taylor mord...@inaugust.com wrote:
Hi Steven!
If you're running Solaris 10, I HIGHLY recommend the use of Sun Studio
instead of GCC. GCC shipped with Solaris is ludicrously old and has
issues.
If you cannot, for some reason, use Sun Studio instead, I highly
recommend installing a recent gcc (4.2 or later) I believe there is one
in blastwave.
We (the Drizzle project have had nothing but nightmares with gcc on
solaris and C++ - and we even worked for Sun until just recently)
However - config.log is going
