public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Santos <daniel.dlds@gmail.com>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Compiling gcc-3.4.6 on sparc Solaris 9
Date: Thu, 14 Jul 2022 19:40:51 +0100	[thread overview]
Message-ID: <00A550FF-E267-496E-B1B0-B2FF9A87589E@gmail.com> (raw)
In-Reply-To: <yddilo02jl5.fsf@CeBiTec.Uni-Bielefeld.DE>

Hello,

As to switching to gcc 4.9, can my currently installed gcc 3.4.6 build it ?
While sticking to the 3.4.6 version, I removed the solaris ld out of the way and am building it with gnu ld.

Right now I have the following error :

rm -f libv3test.a
ar cru libv3test.a testsuite_abi.o testsuite_allocator.o testsuite_hooks.o 
ranlib libv3test.a
touch testsuite_wchar_t
/export/home/dlsa/code/gcc-3.4.6/libstdc++-v3/scripts/create_testsuite_files \
  /export/home/dlsa/code/gcc-3.4.6/libstdc++-v3/testsuite `${PWDCMD-pwd}`
/bin/ksh: /export/home/dlsa/code/gcc-3.4.6/libstdc++-v3/scripts/create_testsuite_files: cannot execute
make[6]: *** [testsuite_files] Error 126
make[6]: Leaving directory `/export/home/dlsa/code/gcc-3.4.6-build/sparc-sun-solaris2.9/sparcv9/libstdc++-v3/testsuite'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/export/home/dlsa/code/gcc-3.4.6-build/sparc-sun-solaris2.9/sparcv9/libstdc++-v3'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/export/home/dlsa/code/gcc-3.4.6-build/sparc-sun-solaris2.9/sparcv9/libstdc++-v3'
make[3]: *** [multi-do] Error 1
make[3]: Leaving directory `/export/home/dlsa/code/gcc-3.4.6-build/sparc-sun-solaris2.9/libstdc++-v3'
make[2]: *** [all-multi] Error 2
make[2]: Leaving directory `/export/home/dlsa/code/gcc-3.4.6-build/sparc-sun-solaris2.9/libstdc++-v3'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/export/home/dlsa/code/gcc-3.4.6-build/sparc-sun-solaris2.9/libstdc++-v3'
make: *** [all-target-libstdc++-v3] Error 2

Can anyone help me understand what this means ?
Thanks
Regards
Daniel Santos



> On 14 Jul 2022, at 09:18, Rainer Orth <ro@cebitec.uni-bielefeld.de> wrote:
> 
> Jonathan Wakely <jwakely.gcc@gmail.com> writes:
> 
>> On Wed, 13 Jul 2022, 19:55 Daniel Santos via Gcc-help, <gcc-help@gcc.gnu.org>
>> wrote:
>> 
>> Hello community,
>> 
>> I am trying to build gcc on Sparc Solaris 9.
>> So far I am creating a directory sibling to the source distribution directory and
>> running configure from there.
>> One thing I don’t understand is why the base configure script does not descend
>> automatically to the gcc subfolder.
>> I have to go in there and run configure again.
>> 
>> Which shell are you using?
>> 
>> See https://gcc.gnu.org/install/specific.html#x-x-solaris2 where it says to use ksh.
>> 
>> While running configure with the command line : ../../gcc-3.4.6/gcc/configure
>> —with-gnu-as —with-gnu-ld
>> and then make : it builds the files and when it gets to running ld I get the error :
>> 
>> /usr/local/sparc-sun-solaris2.9/bin/ld: target elf64-sparc not found
>> 
>> I am building this gcc with the same version installed via sunfkeeware
>> packages.
>> 
>> The reason for building it is that I need objective-c support and the package
>> does not have it.
>> 
>> This ld error indicates that the ld executable being run is from solaris, and not
>> the gnu one I have in /usr/local/bin/ld
>> 
>> Can anyone shed some light on this ?
>> 
>> The installation instructions do say to use the native linker, not the GNU binutils
>> one.
>> Again, see https://gcc.gnu.org/install/specific.html#x-x-solaris2
>> 
>> Passing --with-gnu-ld is wrong if it's finding and using the Solaris linker. Either
>> adjust your PATH so the GNU one is found first, or stop telling GCC it's GNU ld when
>> it isn't.
> 
> Besides, because GCC on Solaris supports two incompatible versions of ld
> (Solaris ld and GNU ld), it is crucial to specify the path to the linker
> you want to configure with with --with-ld=<path to ld> (both for
> /usr/ccs/bin/ld and some version of GNU ld).  Otherwise, PATH changes
> would randomly break the resulting gcc.
> 
> If you really want to use GNU ld (I don't know why you would, though),
> please build and use a recent one: at least what's recommended in
> install.texi.  You'd probably be able to use GNU ld from current
> binutils 2.38, too.
> 
> On top of that, I wouldn't bother with GCC 3.4 at all.  Instead, please
> use the latest release still supporting Solaris 9, GCC 4.9.4 It's way
> better tested and supported than the ancient GCC 3.4.  Please consult
> the Solaris sections of the bundled install docs in
> gcc/doc/install.texi.  It contains many hints and caveats to consider
> when building GCC.  The online version on gcc.gnu.org is for GCC trunk
> only: everything pertaining to Solaris versions no longer supported
> (i.e. before Solaris 11.3) has been removed.
> 
> 	Rainer
> 
> -- 
> -----------------------------------------------------------------------------
> Rainer Orth, Center for Biotechnology, Bielefeld University


  reply	other threads:[~2022-07-14 18:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 18:54 Daniel Santos
2022-07-13 19:47 ` Jonathan Wakely
2022-07-14  8:18   ` Rainer Orth
2022-07-14 18:40     ` Daniel Santos [this message]
2022-07-14 18:50       ` Jonathan Wakely
2022-07-14 18:50       ` Rainer Orth
2022-07-15 18:10         ` Daniel Santos
2022-07-15 19:08           ` Jonathan Wakely
2022-07-16 18:54             ` Daniel Santos
2022-07-17 19:40             ` Daniel Santos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=00A550FF-E267-496E-B1B0-B2FF9A87589E@gmail.com \
    --to=daniel.dlds@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=ro@cebitec.uni-bielefeld.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).