From: Frank Meurer <frank@mats.gmd.STOP-UCE.de>
To: help-gcc@gnu.org
Subject: Re: crosscompile for i386-elf on openbsd 2.6
Date: Mon, 03 Jan 2000 20:50:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.05.10001040539280.2268-100000@mats> (raw)
In-Reply-To: <slrn86vqo1.cn8.dbt@pianosa.catch22.org>
On 2 Jan 2000, dbt wrote:
> I'd like to build a crosscompiler for i386-elf on an OpenBSD system.
> binutils has no problem with a target of i386-elf (it expands it to
> i386-pc-elf), but gcc's configure fails with:
> Configuration i386-pc-elf not supported
> i386-elf is listed as supported in the crosscompile faq at
> http://www.objsw.com/CrossGCC/ , any suggestions?
Er... did you try "./configure --target=i386-unknown-elf ..." ?
Or "i386-unknown-netbsd"?
Or "i386-unknown-linux"?
-------------------------------------------------------------------------
We have joy, we have fun, we have Linux on our SUN.
Sending unsolicited commercial email to this address may be a violation
of the Washington State Consumer Protection Act, chapter 19.86 RCW.
Das Verschicken unverlangter kommerzieller email an diese Adresse ist
verboten (LG Traunstein, 2 HK O 3755/97 vom 14.10.1997, CR 1998, 171f).
WARNING: multiple messages have this Message-ID
From: Frank Meurer <frank@mats.gmd.STOP-UCE.de>
To: help-gcc@gnu.org
Subject: Re: crosscompile for i386-elf on openbsd 2.6
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.05.10001040539280.2268-100000@mats> (raw)
Message-ID: <20000401000000.k78mPDulRBh9bHeCNmzBSQ-Woii6Oc6YTInSjLjZRNA@z> (raw)
In-Reply-To: <slrn86vqo1.cn8.dbt@pianosa.catch22.org>
On 2 Jan 2000, dbt wrote:
> I'd like to build a crosscompiler for i386-elf on an OpenBSD system.
> binutils has no problem with a target of i386-elf (it expands it to
> i386-pc-elf), but gcc's configure fails with:
> Configuration i386-pc-elf not supported
> i386-elf is listed as supported in the crosscompile faq at
> http://www.objsw.com/CrossGCC/ , any suggestions?
Er... did you try "./configure --target=i386-unknown-elf ..." ?
Or "i386-unknown-netbsd"?
Or "i386-unknown-linux"?
-------------------------------------------------------------------------
We have joy, we have fun, we have Linux on our SUN.
Sending unsolicited commercial email to this address may be a violation
of the Washington State Consumer Protection Act, chapter 19.86 RCW.
Das Verschicken unverlangter kommerzieller email an diese Adresse ist
verboten (LG Traunstein, 2 HK O 3755/97 vom 14.10.1997, CR 1998, 171f).
next prev parent reply other threads:[~2000-01-03 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-02 16:27 dbt
2000-01-03 20:50 ` Frank Meurer [this message]
2000-01-04 18:48 ` dbt
2000-04-01 0:00 ` dbt
2000-04-01 0:00 ` Frank Meurer
2000-01-07 7:28 ` Kai Ruottu
2000-04-01 0:00 ` Kai Ruottu
2000-04-01 0:00 ` dbt
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=Pine.GSO.4.05.10001040539280.2268-100000@mats \
--to=frank@mats.gmd.stop-uce.de \
--cc=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).