public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Nasser M. Abbasi" <nma@12000.org>
To: gcc-help@gcc.gnu.org
Subject: failed building gcc 4.6 from sources on linux mint 2.6.35-28-generic, when doing Fortran build
Date: Sun, 27 Mar 2011 12:13:00 -0000	[thread overview]
Message-ID: <4D8EF93B.10307@12000.org> (raw)

I am not sure if I should report this as a bug, or not. Thought
first to ask here.

I am trying to build gcc 4.6 which I downloaded today. I followed
all instructions, did the following:

1. build/install  m4-latest
2. build/install  gmp-5.0.01
3. build/install  mpfr-3.0.0
4. build/install  mpc-0.9
5. and now for gcc 4.6:

./configure
make  

This after about 2 hrs compiling, I get this error:

c-4.6.0/host-i686-pc-linux-gnu/gcc/xgcc -B/media/sf_nabbasi/data/Fortran_related/gcc_4_6/gcc-4.6.0/host-i686-pc-linux-gnu/gcc/ -B/usr/local/i686-pc-linux-gnu/bin/ -B/usr/local/i686-pc-linux-gnu/lib/ -isystem /usr/local/i686-pc-linux-gnu/include -isystem /usr/local/i686-pc-linux-gnu/sys-include
checking for suffix of object files... configure: error: in `/media/sf_nabbasi/data/Fortran_related/gcc_4_6/gcc-4.6.0/i686-pc-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[2]: *** [configure-stage1-target-libgcc] Error 1
make[2]: Leaving directory `/media/sf_nabbasi/data/Fortran_related/gcc_4_6/gcc-4.6.0'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/media/sf_nabbasi/data/Fortran_related/gcc_4_6/gcc-4.6.0'
make: *** [all] Error 2

-----------------------------------

my current gcc is

  gcc -v
Using built-in specs.
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.4.4-14ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.4 --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu
Thread model: posix
gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)

--------------------------------

I put the config.log file in this directory is someone wants to look at it

http://12000.org/tmp/march_27_2011/

ps. not sure if this is important or not, I am running linux on a VM machine. Installed
Linux mint on it.

thank you,
--Nasser

             reply	other threads:[~2011-03-27  8:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-27 12:13 Nasser M. Abbasi [this message]
2011-03-27 12:29 ` Marc Glisse
2011-03-27 19:58   ` Nasser M. Abbasi
2011-03-27 20:18     ` Jonathan Wakely
2011-03-28  1:06       ` Nasser M. Abbasi
2011-03-28  7:53         ` Jonathan Wakely

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=4D8EF93B.10307@12000.org \
    --to=nma@12000.org \
    --cc=gcc-help@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).