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

On Thu, 14 Jul 2022 at 19:40, Daniel Santos <daniel.dlds@gmail.com> wrote:
>
> Hello,
>
> As to switching to gcc 4.9, can my currently installed gcc 3.4.6 build it ?

Yes.

> 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

It's telling you it can't execute the script.

Is that file executable? It should be.

  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 [this message]
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=CAH6eHdQVwc5HEoCJCoe9bEOp1+5DGpwUPK3q+dRz6hOYsnTucw@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=daniel.dlds@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --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).