public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmokrejs at ribosome dot natur dot cuni dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/34523] New: configure does not recognize --with-cpu=arm926ejs but --with-cpu=arm926ej-s
Date: Tue, 18 Dec 2007 17:57:00 -0000 [thread overview]
Message-ID: <bug-34523-215@http.gcc.gnu.org/bugzilla/> (raw)
checking whether sigaltstack is declared... yes
checking for struct tms... yes
checking for clock_t... yes
checking for .preinit_array/.init_array/.fini_array support... no
checking if mkdir takes one argument... no
Unknown CPU used in --with-cpu=arm926ejs
make[2]: *** [configure-stage1-gcc] Error 1
make[2]: Leaving directory `/scratch/gcc-4.2.2/objdir'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/scratch/gcc-4.2.2/objdir'
make: *** [bootstrap] Error 2
Configure seems to mis-require a dash in the cpu. Please note the valid cpu
allowed by the compiler is 'arm926ejs' while not 'arm926ej-s'. So, either
configure is happy and the subsequent build process fails after stage1 is
finished or vice versa. It seems it was possible to use --with-cpu=arm926ejs
with 3.4.5 (bug #26378) so I believe this is a regression.
--
Summary: configure does not recognize --with-cpu=arm926ejs but --
with-cpu=arm926ej-s
Product: gcc
Version: 4.2.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: mmokrejs at ribosome dot natur dot cuni dot cz
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34523
next reply other threads:[~2007-12-18 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 17:57 mmokrejs at ribosome dot natur dot cuni dot cz [this message]
2010-04-05 13:55 ` [Bug target/34523] " rearnsha 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-34523-215@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).