From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Daniel Santos <daniel.dlds@gmail.com>
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 20:50:44 +0200 [thread overview]
Message-ID: <yddfsj3a5q3.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <00A550FF-E267-496E-B1B0-B2FF9A87589E@gmail.com> (Daniel Santos's message of "Thu, 14 Jul 2022 19:40:51 +0100")
Hi Daniel,
> As to switching to gcc 4.9, can my currently installed gcc 3.4.6 build it ?
as documented in install.texi (you absolute need to check it!), GCC 4.9
requires a ISO C++98 compiler, so GC 3.4.6 should be good. If all else
fails, you need to take some intermediate step (like GCC 4.7 which only
needed an ISO C89 compiler).
> While sticking to the 3.4.6 version, I removed the solaris ld out of the
Don't mess around with the installed /usr/ccs/bin/ld. Just pass
--with-ld=<your desired ld> (and --with-gnu-ld or --without-gnu-ld as
needed.
> way and am building it with gnu ld.
Again: why are you so adamant on using GNU ld here? Solaris ld works
way better.
> 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
That script hardcodes /bin/sh which on Solaris 9 probably isn't able to
execute that script. The invocation should be prefixed with $(SHELL)
(initialized from $CONFIG_SHELL) instead.
I'm pretty certain issues like this have been resolved for GCC 4.9/4.8,
so you'd better not bother with GCC 3.4 anymore.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2022-07-14 18:50 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
2022-07-14 18:50 ` Jonathan Wakely
2022-07-14 18:50 ` Rainer Orth [this message]
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=yddfsj3a5q3.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=daniel.dlds@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/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).