From: dbt@meat.net (dbt)
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: <slrn875bt7.3cn.dbt@pianosa.catch22.org> (raw)
Message-ID: <20000401000000.vjy_7avr4ZniyYjTTSZKLk2de1vhGov8wHOXrR4iv4Q@z> (raw)
In-Reply-To: <Pine.GSO.4.05.10001040539280.2268-100000@mats>
Frank Meurer <frank@mats.gmd.STOP-UCE.de> says:
>
>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 ..." ?
configure fails with "Configuration i386-unkown-elf not supported"
>Or "i386-unknown-netbsd"?
/scratch/cross/build/gcc/xgcc -B/scratch/cross/build/gcc/ -B/usr/local/i386-unkown-netbsd/bin/ -I/usr/local/i386-unkown-netbsd/include -DCROSS_COMPILE -DIN_GCC -g -O2 -I./include -I. -I../../src/gcc -I../../src/gcc/config -I../../src/gcc/../include -aux-info SYSCALLS.c.X -S -o tmp-SYSCALLS.s SYSCALLS.c
In file included from SYSCALLS.c:86:
include/stddef.h:28: machine/ansi.h: No such file or directory
*** Error code 1
Stop in /scratch/cross/build/gcc.
*** Error code 1
>Or "i386-unknown-linux"?
libio compile fails.
I'm going to try the netbsd build with gmake instead of bsd make and
see if that makes a difference, though it shouldn't....
--
David Terrell | dbt@meat.net
Prime Minister, Nebcorp Inc | http://wwn.nebcorp.com/
next prev parent reply other threads:[~2000-04-01 0:00 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
2000-01-04 18:48 ` dbt [this message]
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=slrn875bt7.3cn.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).