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 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)
> w
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 tak
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-
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 wrote:
> Hi,
>
> Thanks for your respond. Here is the excerpt from gtest/config.log
> that I
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 wrote:
> I am running Nexenta (Debian on top of Solaris 11), and the gcc
> version is:
>
> gcc (GCC) 4.2.3
