From: Ian Zhang <hhzhang@yahoo.com>
To: crossgcc@sourceware.cygnus.com
Subject: Need help to install a cross compiler for powerpc
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <20010118011401.62340.qmail@web10003.mail.yahoo.com> (raw)
Message-ID: <20010401000000.zJ_WHsIwrC8KnMMDvG0tIGuKiKFAAxr0yldydJFH_88@z> (raw)
Hi,
I am trying to build a cross compiler for powerpc on
Redhat 6.1. I tried to follow the FAQ and did
something like this:
1. download
binutils-2.9.1.tar.gz gcc-core-2.95.2.tar.gz
gcc-g++-2.95.2.tar.gz gdb-4.17.tar.gz
newlib-1.8.2.tar.gz
2.
My current directory is: /dn/cross/
cd /dn/cross
mkdir build-binutils build-gcc build-gdb build-newlib
mkdir install
tar xzvf binutils-2.9.1.tar.gz
tar xzvf gcc-core-2.95.2.tar.gz
tar gcc-g++-2.95.2.tar.gz
3. I try to build a cross-compiler for powerpc.
Following FAQ:
target=powerpc-eabi
prefix=/dn/cross/install
cd build-binutils
../binutils-2.9.1/configure --target=$target
--prefix=$prefix -v
make all install
cd ../build-gcc
../gcc-2.95.2/configure --target=$target
--prefix=$prefix
make all
I got the following error
stdlib.h No such file or directory.
unistd.h No such file or directory.
4. After I read the mailing list.
I copied /usr/include to $prefix/$target/sub-include
I have one question:
Is /usr/include the right source for those header
file?
5. After I rerun the configure and make all, I got the
following error:
checking whether the C compiler
(/dn/cross/build-gcc/gcc/xgcc -B/dn/cross/build-
gcc/gcc/ -B/dn/cross/install/powerpc-eabi/bin/ -g -O2
) works... no
configure: error: installation or configuration
problem: C compiler cannot creat
e executables.
make[1]: Entering directory
`/dn/cross/build-gcc/powerpc-eabi/libio'
test x"no" != xyes ||\
/dn/cross/build-gcc/gcc/xgcc
-B/dn/cross/build-gcc/gcc/ -B/dn/cross/install/po
werpc-eabi/bin/ -c -g -O2 -I.
-I../../../gcc-2.95.2/libio ../../../gcc-2.95.2/
libio/filedoalloc.c -o pic/filedoalloc.o
/dn/cross/build-gcc/gcc/xgcc
-B/dn/cross/build-gcc/gcc/ -B/dn/cross/install/powe
rpc-eabi/bin/ -c -g -O2 -I.
-I../../../gcc-2.95.2/libio ../../../gcc-2.95.2/lib
io/filedoalloc.c
In file included from
../../../gcc-2.95.2/libio/libio.h:30,
from
../../../gcc-2.95.2/libio/iolibio.h:1,
from
../../../gcc-2.95.2/libio/libioP.h:47,
from
../../../gcc-2.95.2/libio/filedoalloc.c:45:
_G_config.h:43: parse error before `_G_sigset_t'
_G_config.h:43: warning: data definition has no type
or storage class
make[1]: *** [filedoalloc.o] Error 1
make[1]: Leaving directory
`/dn/cross/build-gcc/powerpc-eabi/libio'
make: *** [all-target-libio] Error 2
[builder@prtpd320 build-gcc]
Can anyone help me with those?
Thanks,
Ian Zhang
=====
Ian Zhang
hhzhang@yahoo.com
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2001-04-01 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 17:14 Ian Zhang [this message]
2001-04-01 0:00 ` Ian Zhang
2001-01-17 18:46 Ian Zhang
2001-04-01 0:00 ` Ian Zhang
2001-01-17 23:13 Hua Ji
2001-04-01 0:00 ` Hua Ji
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=20010118011401.62340.qmail@web10003.mail.yahoo.com \
--to=hhzhang@yahoo.com \
--cc=crossgcc@sourceware.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).