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: gcc    conftest.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.com>wrote:
>
>> 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<protobuf%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.

Reply via email to