public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/51093] GCC 4.4.3 build fails with 'OPTION_ISA_AES' as undefined
Date: Sat, 12 Nov 2011 13:39:00 -0000 [thread overview]
Message-ID: <bug-51093-4-Kqb9F54SSK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51093-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51093
--- Comment #4 from Mikael Pettersson <mikpe at it dot uu.se> 2011-11-12 13:12:05 UTC ---
(In reply to comment #0)
> I've downloaded gcc 4.4.3 tar-ball package.
> Configured and build as follows for host-x86_64-unknown-linux-gnu:
> <./configure --prefix=$HOME/install/dir/ --enable-languages=c++>
> <make bootstrap>
I just successfully bootstrapped gcc-4.4.3 on x86_64 (Fedora 13) configured
exactly as indicated above, except I also passed in --with-gmp= and
--with-mpfr= to pick up my locally built gmp/mpfr libraries, and I built in a
separate object directory.
Are you sure you didn't supply any other options to configure?
Ditto for 'make bootstrap'?
Are you sure there were no errors from configure?
Where there any warnings or errors from 'make bootstrap' before the one you
showed here?
What's the host environment (Linux distro, host gcc version, binutils version,
glibc version, how much memory, how much swap)?
> gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes
> -Wmissing-prototypes -Wcast-qual -fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE
> -I. -Ibuild -I../.././gcc -I../.././gcc/build -I../.././gcc/../include
> -I../.././gcc/../libcpp/include -I/usr/intel/pkgs/libgmp/4.3.0/include
> -I/usr/intel/pkgs/libgmp/4.3.0/include -I/usr/intel/pkgs/libmpfr/2.4.1/include
These paths to /usr/intel/pkgs/ look non-standard. Where did they come from?
next prev parent reply other threads:[~2011-11-12 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 12:38 [Bug other/51093] New: " omjiomer at gmail dot com
2011-11-11 13:05 ` [Bug other/51093] " mikpe at it dot uu.se
2011-11-11 19:56 ` [Bug target/51093] " pinskia at gcc dot gnu.org
2011-11-11 20:22 ` omjiomer at gmail dot com
2011-11-12 13:39 ` mikpe at it dot uu.se [this message]
2012-01-06 0:39 ` pinskia 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-51093-4-Kqb9F54SSK@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).