public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bart dot vanassche at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/23656] New: Cross-compilation with newlib fails in libiberty Date: Wed, 31 Aug 2005 15:36:00 -0000 [thread overview] Message-ID: <20050831153403.23656.bart.vanassche@gmail.com> (raw) While attempting to generate a cross-compiler, I got a build error in libiberty/strsignal.c, because newlib has a strsignal() definition but libiberty does not test for the strsignal() declaration in the newlib headers. ####################################### $PREFIX kernel=... (2.4.31 Linux kernel sources) combined=... (tree with gcc-3.4.4 and newlib-1.13.0 sources combined) export PREFIX=/home/bart/cross export KERNELARCH=m68k export TARGET=m68k-amiga-linux export HOST=i686-pc-linux-gnu mkdir -p $PREFIX/$TARGET/include cd $PREFIX/$TARGET/include || exit $? ln -s $kernel/include/linux . ln -s $kernel/include/asm-generic . ln -s $kernel/include/asm-$KERNELARCH asm $combined/configure \ --disable-checking \ --disable-mudflap \ --disable-nls \ --disable-shared \ --enable-__cxa_atexit \ --enable-languages=c,c++ \ --enable-threads=single \ --prefix=$PREFIX \ --target=$TARGET \ --with-local-prefix=$PREFIX \ --with-newlib \ --with-sysroot=$PREFIX/$TARGET \ -- Summary: Cross-compilation with newlib fails in libiberty Product: gcc Version: 3.4.4 Status: UNCONFIRMED Severity: normal Priority: P2 Component: other AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: bart dot vanassche at gmail dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: m68k-amiga-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23656
next reply other threads:[~2005-08-31 15:34 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-31 15:36 bart dot vanassche at gmail dot com [this message] 2005-08-31 15:38 ` [Bug other/23656] " bart dot vanassche at gmail dot com
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=20050831153403.23656.bart.vanassche@gmail.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).