From: Michael2.Roth@RSD.rohde-schwarz.com
To: crossgcc@sourceware.cygnus.com
Subject: cross-gcc problem when building libraries for pc-linux
Date: Fri, 15 Dec 2000 08:40:00 -0000 [thread overview]
Message-ID: <C12569B6.005B941E.00@mail.rohde-schwarz.com> (raw)
Hi all,
perhaps someone can comment on my problem building a cross-GCC:
I'm trying to make a cygwin hosted GCC generating pc-linux target code (I used
--target=i686-pc-linux-gnu). Building the binutils works fine, the gcc-core
also. Trying the full gcc package results in the following error message
/usr/local/src/gcc-2.95.2/libiberty/strerror.c:461: conflicting types for
`sys_errlist'
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/../../../../i686-pc-linux-gnu/include/stdio.h:557:
previous declaration of `sys_errlist'
make[1]: *** [strerror.o] Error 1
make: *** [all-target-libiberty] Error 2
Well, if I ignore these (or similar) messages, install the compiler and then
take the libraries from the target system for linking, everything is working.
However, I would like to know why I cannot build these libraries locally.
Obviously, I took the wrong header files from the target system - but which ones
are correct? The target Linux runs egcs-2.91.66, and I simply took the header
files from /usr/include - perhaps I was wrong?
Thanks a lot,
Michael
------
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:[~2000-12-15 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 8:40 Michael2.Roth [this message]
2000-12-18 10:33 ` Kai Ruottu
2000-12-26 22:58 ` gcc link to library built with Sun-CC Bin Zhou
2000-12-15 8:52 cross-gcc problem when building libraries for pc-linux Nathan Knuth
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=C12569B6.005B941E.00@mail.rohde-schwarz.com \
--to=michael2.roth@rsd.rohde-schwarz.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).