public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "abiggadike at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/16371] [3.4/3.5 Regression] Fails to build the target libstdc++-v3 library on a cross to any linux Date: Tue, 24 Aug 2004 19:09:00 -0000 [thread overview] Message-ID: <20040824190912.17122.qmail@sourceware.org> (raw) In-Reply-To: <20040705162800.16371.lv@gentoo.org> ------- Additional Comments From abiggadike at yahoo dot com 2004-08-24 19:09 ------- Trying to build a cross compiler for Solaris 9 x86 and I'm seeing the same problem when building binutils (which contains libiberty). Configure: ../binutils-2.15/configure --host=i686-pc-linux-gnu --target i386-pc-solaris2.9 \ --with-headers=/path/to/headers --with-libs=/path/to/libs \ --prefix=/path/to/prefix -v --disable-nls Error occurs during 'make': Configuring in libiberty /solaris-9/build-binutils/libiberty configure: loading cache ./config.cache checking whether to enable maintainer-specific portions of Makefiles... no checking for makeinfo... makeinfo checking for perl... perl checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for i686-pc-linux-gnu-ar... ar checking for i686-pc-linux-gnu-ranlib... ranlib checking for i686-pc-linux-gnu-gcc... gcc checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking how to run the C preprocessor... gcc -E checking whether gcc and cc understand -c and -o together... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking whether byte ordering is bigendian... no checking for a BSD-compatible install... /usr/bin/install -c xhost-mkfrag is unchanged checking for sys/file.h... yes checking for sys/param.h... yes checking for limits.h... yes checking for stdlib.h... yes checking for malloc.h... yes checking for string.h... yes checking for unistd.h... yes checking for strings.h... yes checking for sys/time.h... yes checking for time.h... yes checking for sys/resource.h... yes checking for sys/stat.h... yes checking for sys/mman.h... yes checking for fcntl.h... yes checking for alloca.h... yes checking for sys/pstat.h... no checking for sys/sysmp.h... no checking for sys/sysinfo.h... yes checking for machine/hal_sysinfo.h... no checking for sys/table.h... no checking for sys/sysctl.h... yes checking for sys/systemcfg.h... no checking for sys/wait.h that is POSIX.1 compatible... yes checking whether time.h and sys/time.h may both be included... yes checking whether errno must be declared... no checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... (cached) yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for memory.h... yes checking for strings.h... (cached) yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... (cached) yes checking for uintptr_t... yes checking for pid_t... yes checking for library containing strerror... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES. make: *** [configure-libiberty] Error 1 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16371
next prev parent reply other threads:[~2004-08-24 19:09 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-05 16:28 [Bug libstdc++/16371] New: gcc 3.4.1 fails to configure on amd64 with multilib enabled lv at gentoo dot org 2004-07-05 16:31 ` [Bug libstdc++/16371] " pinskia at gcc dot gnu dot org 2004-07-05 16:52 ` lv at gentoo dot org 2004-07-05 16:59 ` lv at gentoo dot org 2004-07-05 17:02 ` pcarlini at suse dot de 2004-07-05 17:27 ` lv at gentoo dot org 2004-07-05 19:01 ` lv at gentoo dot org 2004-07-23 3:29 ` mg_gentoo at yahoo dot com 2004-07-23 8:58 ` mg_gentoo at yahoo dot com 2004-07-23 9:18 ` lv at gentoo dot org 2004-07-23 9:38 ` [Bug libstdc++/16371] gcc 3.4.1 - GLIBCXX_CHECK_COMPLEX_MATH_SUPPORT does not respect GCC_NO_EXECUTABLES lv at gentoo dot org 2004-07-23 11:07 ` mg_gentoo at yahoo dot com 2004-07-26 14:16 ` [Bug libstdc++/16371] [3.4/3.5 Regression] Fails to build the target libstdc++-v3 library on a cross to any linux pinskia at gcc dot gnu dot org 2004-07-26 14:17 ` pinskia at gcc dot gnu dot org 2004-07-26 14:19 ` pinskia at gcc dot gnu dot org 2004-07-26 23:06 ` mg_gentoo at yahoo dot com 2004-07-26 23:16 ` lars dot sonchocky-helldorf at hamburg dot de 2004-07-27 7:23 ` remedy at programmit dot co dot uk 2004-07-29 16:39 ` mg_gentoo at yahoo dot com 2004-08-24 19:09 ` abiggadike at yahoo dot com [this message] 2004-08-25 4:16 ` [Bug libstdc++/16371] [3.4/3.5 Regression] libstdc++ fails for crosses pinskia at gcc dot gnu dot org 2004-08-25 4:16 ` pinskia at gcc dot gnu dot org 2004-08-29 18:55 ` mmitchel at gcc dot gnu dot org 2004-09-15 2:42 ` [Bug libstdc++/16371] [3.4/4.0 " nospam-bugzilla at uun dot org 2004-09-28 13:49 ` jtison at ntplx dot net 2004-11-01 0:46 ` mmitchel at gcc dot gnu dot org 2004-11-10 21:12 ` mg_gentoo at yahoo dot com 2004-11-11 0:40 ` wilson at specifixinc dot com 2004-11-11 3:45 ` mg_gentoo at yahoo dot com 2004-12-05 3:14 ` [Bug libstdc++/16371] " pinskia at gcc dot gnu dot org 2005-03-06 15:40 ` pinskia at gcc dot gnu dot org
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=20040824190912.17122.qmail@sourceware.org \ --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).