public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dschlic1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/45174] Make fails in zlib
Date: Sun, 08 Aug 2010 19:19:00 -0000	[thread overview]
Message-ID: <20100808191917.16125.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45174-19456@http.gcc.gnu.org/bugzilla/>



------- Comment #19 from dschlic1 at gmail dot com  2010-08-08 19:19 -------
Subject: Re:  Make fails in zlib

Hello;
        I am afraid I messed up my system. I was playing around trying to
install the latest versions of binutils and gcc on my linux system
(native, not cross compile), and now I am getting a different error. In
zlib's config.log:

ne=generic --enable-checking=release --build=i486-linux-gnu
--host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) 
configure:3234: $? = 0
configure:3223: gcc  -m64 -V >&5
gcc: '-V' must come at the start of the command line
configure:3234: $? = 1
configure:3223: gcc  -m64 -qversion >&5
gcc: unrecognized option '-qversion'
gcc: no input files
configure:3234: $? = 1
configure:3250: gcc  -m64 -o conftest -g -O2    conftest.c  >&5
Assembler messages:
Fatal error: No compiled in support for x86_64
configure:3253: $? = 1
configure:3441: checking for suffix of object files
configure:3463: gcc  -m64 -c -g -O2  conftest.c >&5
Assembler messages:
Fatal error: No compiled in support for x86_64
configure:3467: $? = 1

It looks like configure is trying to compile sources to 64 bit. I am
running a 32 bit system. Any ideas on how to tell configure to compile
for a 32 bit linux box?

Thank You,
Donald Schlicht


-- 


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


  parent reply	other threads:[~2010-08-08 19:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 22:20 [Bug bootstrap/45174] New: " dschlic1 at gmail dot com
2010-08-03 22:23 ` [Bug bootstrap/45174] " dschlic1 at gmail dot com
2010-08-03 22:25 ` pinskia at gcc dot gnu dot org
2010-08-03 22:28 ` pinskia at gcc dot gnu dot org
2010-08-03 23:00 ` dschlic1 at gmail dot com
2010-08-03 23:14 ` pinskia at gcc dot gnu dot org
2010-08-03 23:22 ` dschlic1 at gmail dot com
2010-08-04  0:42 ` pinskia at gcc dot gnu dot org
2010-08-04  0:43 ` pinskia at gcc dot gnu dot org
2010-08-05  0:27 ` dschlic1 at gmail dot com
2010-08-05 17:01 ` rwild at gcc dot gnu dot org
2010-08-06 14:35 ` dschlic1 at gmail dot com
2010-08-06 17:22 ` rwild at gcc dot gnu dot org
2010-08-07  0:18 ` dschlic1 at gmail dot com
2010-08-07 14:29 ` rwild at gcc dot gnu dot org
2010-08-08 19:19 ` dschlic1 at gmail dot com [this message]
2010-08-08 20:44 ` rwild at gcc dot gnu dot org
2010-08-09  0:42 ` dschlic1 at gmail dot com
2010-09-07 14:49 ` ibolton at gcc dot gnu dot org
2010-09-08 10:06 ` ibolton at gcc dot gnu dot org
2010-09-08 16:27 ` rwild at gcc dot gnu dot org
     [not found] <bug-45174-4@http.gcc.gnu.org/bugzilla/>
2010-10-02 14:52 ` rwild at gcc dot gnu.org
2011-01-18  1:46 ` John.Tytgat at aaug dot net
2011-01-18  6:29 ` John.Tytgat at aaug dot net
2011-01-18  8:30 ` rwild at gcc dot gnu.org
2011-04-12 19:36 ` dschlic1 at gmail dot com

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=20100808191917.16125.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: 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).