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 <[email protected]>wrote: > 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 <[email protected]> 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 <[email protected] > >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 "[email protected]" > > > | #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 <[email protected]> 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 < > [email protected] > > > > > <mailto:[email protected]>> wrote: > > > > > > > Hi all, > > > > > > > I tried to run 'configure' for the 'protobuf-2.3.0' on an > Intelx86 > > > > > and Solaris 10 machine. It's failed and I saw the following > error > > > > > message: > > > > > > > .... > > > > > config.status: creating protobuf-lite.pc > > > > > config.status: creating config.h > > > > > config.status: executing depfiles commands > > > > > config.status: executing libtool commands > > > > > === configuring in gtest > > > > > > (/home/song/MyProjects/googleProtocolBuffers/protobuf-2.3.0/gtest) > > > > > configure: running /bin/bash ./configure > > > > > '--prefix=/home/song/MyProjects/LibDist/protobuf-2.3.0' > > > > > --cache-file=/dev/null --srcdir=. > > > > > checking for a BSD-compatible install... build-aux/install-sh > -c > > > > > checking whether build environment is sane... yes > > > > > checking for a thread-safe mkdir -p... build-aux/install-sh -c > -d > > > > > checking for gawk... no > > > > > checking for mawk... no > > > > > checking for nawk... nawk > > > > > checking whether make sets $(MAKE)... yes > > > > > checking for gcc... gcc > > > > > *checking for C compiler default output file name... > > > > > configure: error: C compiler cannot create executables* > > > > > See `config.log' for more details. > > > > > configure: error: *./configure failed for gtest* > > > > > > > ...Here are the info on the GNU tools: > > > > > > > $ gcc --version > > > > > gcc (GCC) 3.4.6 > > > > > Copyright (C) 2006 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. > > > > > > > $ make --version > > > > > GNU Make 3.80 > > > > > Copyright (C) 2002 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. > > > > > > > $ ./configure --version > > > > > Protocol Buffers configure 2.3.0 > > > > > generated by GNU Autoconf 2.61 > > > > > > > Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, > 2001, > > > > > 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc. > > > > > This configure script is free software; the Free Software > > > Foundation > > > > > gives unlimited permission to copy, distribute and modify it. > > > > > > > Any help would be greatly appreciated. > > > > > > > Best regards, > > > > > Steven > > > > > > > -- > > > > > You received this message because you are subscribed to the > Google > > > > > Groups "Protocol Buffers" group. > > > > > To post to this group, send email to [email protected] > > > > > <mailto:[email protected]>. > > > > > To unsubscribe from this group, send email to > > > > > > > > > > [email protected]<protobuf%[email protected]> > <protobuf%[email protected] om> > > > > > > > > > > <mailto:protobuf%[email protected]<protobuf%[email protected]> > <protobuf%252bunsubscr...@go oglegroups.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 [email protected]. > > > > > To unsubscribe from this group, send email to > > > > > [email protected]<protobuf%[email protected]> > <protobuf%[email protected] om> > > > . > > > > > 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 [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<protobuf%[email protected]> > <protobuf%[email protected] om> > > > . > > > 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 [email protected]. > To unsubscribe from this group, send email to > [email protected]<protobuf%[email protected]> > . > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
