public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Santos <daniel.dlds@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Compiling gcc-3.4.6 on sparc Solaris 9
Date: Wed, 13 Jul 2022 19:54:29 +0100	[thread overview]
Message-ID: <6A2F680E-2A62-46AA-8320-B799E1B49357@gmail.com> (raw)

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.

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 ?

Thanks
Regards
Daniel Santos

Daniel Santos




             reply	other threads:[~2022-07-13 18:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 18:54 Daniel Santos [this message]
2022-07-13 19:47 ` Jonathan Wakely
2022-07-14  8:18   ` Rainer Orth
2022-07-14 18:40     ` Daniel Santos
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=6A2F680E-2A62-46AA-8320-B799E1B49357@gmail.com \
    --to=daniel.dlds@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /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).