From: Mike Neuhauser <mike@gams.co.at>
To: egcs@cygnus.com
Subject: --with-headers for cross-compile broken? (egcs-971201)
Date: Tue, 02 Dec 1997 09:56:00 -0000 [thread overview]
Message-ID: <199712021615.RAA11779@scully.gams.co.at> (raw)
I'm trying to build a powerpc-unknown-linux-gnulibc2 targeted cross
compiler on an i686-pc-linux-gnulibc1 host. I've got problems with the
target header files.
I'm using bintuls-2.8.1.0.17 (binutils and egcs are built together)
and egcs-971201 (egcs-971122 shows same behaviour).
The following sets up the build directory and does the build:
mkdir otb
cd otb
ln -s ../egcs-971201/* .
ln -s ../binutils-2.8.1.0.17/{bfd,binutils,gas,gprof,ld,opcodes} .
mkdir build
cd build
../configure --prefix=/usr/local/powerpc-unknown-linux-gnulibc2 \
--target=powerpc-unknown-linux-gnulibc2 \
--with-headers=<dir with headers of gnu-libc2>
make cross
configure copies the headers to
/usr/local/powerpc-unknown-linux-gnulibc2/powerpc-unknown-linux-gnulibc2/sys-include,
but when libgcc2.c is compiled to get _eprintf.o, the header stdio.h is
not found. The header search list for this compile is
include
.
../../gcc
../../gcc/config
/disk/home/mike/SOHO/Src/otb/build/gcc/include
/usr/local/powerpc-unknown-linux-gnulibc2/lib/gcc-lib/powerpc-unknown-linux-gnulibc2/egcs-2.90.18/include
/usr/local/powerpc-unknown-linux-gnulibc2/powerpc-unknown-linux-gnulibc2/include
After I copied the headers manually to
/usr/local/powerpc-unknown-linux-gnulibc2/powerpc-unknown-linux-gnulibc2/include
the cross-compiler was build successfully.
Does anyone know, if this is a bug, or if I have used this feature wrong
(whats the right way to do it)?
Thank you!
next reply other threads:[~1997-12-02 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-02 9:56 Mike Neuhauser [this message]
1997-12-02 11:25 ` Jeffrey A Law
1997-12-03 3:30 ` Mike Neuhauser
1997-12-05 10:44 ` Jeffrey A Law
1998-02-24 19:54 ` Jeffrey A Law
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=199712021615.RAA11779@scully.gams.co.at \
--to=mike@gams.co.at \
--cc=egcs@cygnus.com \
/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).