public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bunk at stusta dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/28949]  New: [4.2 regression] configure-target-libiberty: Link tests are not  allowed after GCC_NO_EXECUTABLES.
Date: Mon, 04 Sep 2006 15:33:00 -0000	[thread overview]
Message-ID: <bug-28949-9876@http.gcc.gnu.org/bugzilla/> (raw)

I did:

../configure --target=arm-linux --prefix=/usr/local/DIR/gcc-arm- svn20060904
--enable-languages=c --with-as=/usr/local/bin/arm-linux-as
--with-ld=/usr/local/bin/arm-linux-ld --without-headers --disable-shared
--disable-multilib --enable-threads=single --disable-nls --disable-libmudflap
--disable-libssp

make


error message:

<--  snip  -->

...
checking for pid_t... no
checking for library containing strerror... configure: error: Link tests are
not
 allowed after GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-libiberty] Error 1
make[1]: Leaving directory `/TMP/svn/gcc/build-arm'
make: *** [all] Error 2

<--  snip  -->

The error is not specific for the arm target, I'm also getting it for several
other targets.


-- 
           Summary: [4.2 regression] configure-target-libiberty: Link tests
                    are not
                    allowed after GCC_NO_EXECUTABLES.
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: bunk at stusta dot de
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: arm-unknown-linux-gnu (and several others)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28949


             reply	other threads:[~2006-09-04 15:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04 15:33 bunk at stusta dot de [this message]
2006-09-04 15:34 ` [Bug bootstrap/28949] " bunk at stusta dot de
2006-09-04 15:34 ` bunk at stusta dot de
2006-09-04 16:21 ` pinskia at gcc dot gnu dot org
2006-09-04 16:27 ` bunk at stusta dot de
2006-09-04 16:46 ` bunk at stusta dot de
2006-09-10 17:01 ` jsm28 at gcc dot gnu dot org
2006-09-10 22:26 ` [Bug bootstrap/28949] " pinskia at gcc dot gnu dot org
2006-09-10 22:42 ` bunk at stusta dot de
2007-05-14 21:37 ` mmitchel at gcc dot gnu dot org
2007-07-17  3:35 ` cnstar9988 at gmail dot com
2007-07-17  3:59 ` 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=bug-28949-9876@http.gcc.gnu.org/bugzilla/ \
    --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: 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).