Hi Art,
> I tried the '--without-gnu-ld --with-ld=/usr/ccs/bin/ld' configure options
> and my build failed again as my GNU 'ld' binary was again being found. So
strange: I'd have expected for gcc to honor a full path in --with-ld
(and --with-ls for that matter). But then I never tried this befor
> Hi Art,
Hello.
>> Could be, see above. Apart from that, I wonder why you insist on using
>> GNU ld on Solaris. install.texi strongly suggests to use the Solaris
>> linker instead, and I stand by that advise.
>
>> A couple of comments on those configure options: avoid everything not
>> strictl
Hi Art,
>> Could be, see above. Apart from that, I wonder why you insist on using
>> GNU ld on Solaris. install.texi strongly suggests to use the Solaris
>> linker instead, and I stand by that advise.
>
>> A couple of comments on those configure options: avoid everything not
>> strictly necessar
> Hi Art,
Hi. Thanks for helping me try to fix the build problem I'm seeing.
{ ... snip ... }
> Could be, see above. Apart from that, I wonder why you insist on using
> GNU ld on Solaris. install.texi strongly suggests to use the Solaris
> linker instead, and I stand by that advise.
> A couple
Hi Art,
> I've had no luck building GCC on a Sparc-based Solaris machine here
> since early March - right around the time some LTO related patches
> landed. I've started trying again and the build fails when linking
> libgcc_so at the end of stage1. Here's the end of the build log:
>
> { ... snip
Hi.
I've had no luck building GCC on a Sparc-based Solaris machine here
since early March - right around the time some LTO related patches
landed. I've started trying again and the build fails when linking
libgcc_so at the end of stage1. Here's the end of the build log:
{ ... snip ... }
/bin/bas
