public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: dbt@meat.net (dbt)
To: help-gcc@gnu.org
Subject: crosscompile for i386-elf on openbsd 2.6
Date: Sun, 02 Jan 2000 16:27:00 -0000	[thread overview]
Message-ID: <slrn86vqo1.cn8.dbt@pianosa.catch22.org> (raw)

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?

-- 
David Terrell                             | dbt@meat.net
Prime Minister, Nebcorp Inc               | http://wwn.nebcorp.com/

WARNING: multiple messages have this Message-ID
From: dbt@meat.net (dbt)
To: help-gcc@gnu.org
Subject: crosscompile for i386-elf on openbsd 2.6
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <slrn86vqo1.cn8.dbt@pianosa.catch22.org> (raw)
Message-ID: <20000401000000.wJWOfh_oB6WEJcxrqEpd7wBdIm2AFZm-M2nm6jt8fZw@z> (raw)

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?

-- 
David Terrell                             | dbt@meat.net
Prime Minister, Nebcorp Inc               | http://wwn.nebcorp.com/

             reply	other threads:[~2000-01-02 16:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-02 16:27 dbt [this message]
2000-01-03 20:50 ` Frank Meurer
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=slrn86vqo1.cn8.dbt@pianosa.catch22.org \
    --to=dbt@meat.net \
    --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).