public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47107] ix86-netware is recognized by config.guess, but has no valid basic_machine set
Date: Fri, 21 Sep 2012 16:35:00 -0000	[thread overview]
Message-ID: <bug-47107-4-pz4H1mCjeK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47107-4@http.gcc.gnu.org/bugzilla/>


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

Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2012-09-17

--- Comment #2 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> 2012-09-21 16:34:59 UTC ---
What I am seeing now is that the configure command succeeds, and make all-gcc
builds a bunch of libraries, and then it fails with:

checking for stddef.h... yes
ranlib libcpp.a
checking for string.h... (cached) yes
make[1]: Leaving directory `/home/amylaar/fsf/tst-ix86-netware/libcpp'
checking for strings.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for time.h... yes
checking for iconv.h... yes
checking for fcntl.h... yes

...

checking whether putchar_unlocked is declared... yes
checking whether putc_unlocked is declared... yes
checking whether getrlimit is declared... yes
checking whether setrlimit is declared... yes
checking whether getrusage is declared... yes
checking whether ldgetname is declared... no
checking whether times is declared... yes
checking whether sigaltstack is declared... yes
checking whether madvise is declared... yes
checking for struct tms... yes
checking for clock_t... yes
checking for F_SETLKW... yes
checking if mkdir takes one argument... no
*** Configuration ix86-pc-netware not supported
make: *** [configure-gcc] Error 1

Is that the expected behaviour, or is config.sub culpable in allowing
ix86-netware?


  parent reply	other threads:[~2012-09-21 16:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-29 12:04 [Bug target/47107] New: " amylaar at gcc dot gnu.org
2010-12-29 14:08 ` [Bug target/47107] " joseph at codesourcery dot com
2012-09-21 16:35 ` amylaar at gcc dot gnu.org [this message]
2012-09-21 16:45 ` joseph at codesourcery dot com
2013-02-26 11:18 ` amylaar at gcc dot gnu.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-47107-4-pz4H1mCjeK@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).