From: "Tomasz Kłoczko" <kloczek@rudy.mif.pg.gda.pl>
To: ultralinux@vger.kernel.org
Subject: Re: egcs 1.1.1 and ultrasparc .. possible ?
Date: Tue, 08 Dec 1998 08:07:03 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-91313362000041@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-91308610811901@msgid-missing>
On Mon, 7 Dec 1998, David S. Miller wrote:
> Date: Mon, 7 Dec 1998 18:23:15 +0100 (EET)
> From: =?ISO-8859-2?Q?Tomasz_K³oczko?= <kloczek@rudy.mif.pg.gda.pl>
>
> I try use egcs on ultra. After building binutils 2.9.1.0.17 and
> egcs 1.1.1 with using UP 1.1 gcc/binutils I try rebuild binutils
> ones more and this fails. What is wrong in above procedure ? What I
> need (patches ?) for making this ? If anyone know please .. :)
>
> You need to build these things in "sparc32 mode". ie. run:
>
> sparc32 bash
>
> Then the configure scripts of those packages will configure and build
> properly.
Works :)
Thanks.
Dave .. is this possible to build egcs for crosscompile sparc64 binaries ?
If yes .. simple how to do this ? How to prepare binutils and egcs ?
kloczek
PS. If any one want .. ready to use rpm with binutils 2.9.1.0.17 is
avalaible on ftp://cenzor.zie.pg.gda.pl/pub/PLD-stable/sparc/.
--
-----------------------------------------------------------
*Ludzie nie maj± problemów, tylko sobie sami je stwarzaj±*
-----------------------------------------------------------
Tomasz K³oczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gda.pl*
next prev parent reply other threads:[~1998-12-08 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-07 17:23 egcs 1.1.1 and ultrasparc .. possible ? Tomasz Kłoczko
1998-12-08 5:01 ` David S. Miller
1998-12-08 8:07 ` Tomasz Kłoczko [this message]
1998-12-08 8:09 ` David S. Miller
1998-12-08 8:17 ` Tomasz Kłoczko
1998-12-08 8:25 ` David S. Miller
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=marc-linux-ultrasparc-91313362000041@msgid-missing \
--to=kloczek@rudy.mif.pg.gda.pl \
--cc=ultralinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.