From: Tim Prince <tprince@computer.org>
To: IVAN ANGELOV <ivangotoy@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: C++ compiler cannot create executables
Date: Fri, 14 Sep 2007 15:20:00 -0000 [thread overview]
Message-ID: <46EA8E25.9090508@computer.org> (raw)
In-Reply-To: <c51c48d0709140015y44ded78ds7461f2ff72beaf6f@mail.gmail.com>
IVAN ANGELOV wrote:
> ---------- Forwarded message ----------
> From: IVAN ANGELOV <ivangotoy@gmail.com>
> Date: 14.09.2007 10:11
> Subject: C++ compiler cannot create executables
> To: gcc-help@gcc.gnu.org
>
> Yesterday (13.09.2007) I downloaded the full GCC trunk from svn. It
> was around 300 mb in size. I followed the installation instructions as
> much as I could.
> I made objdir on my desktop and I ran :
> /home/ivan/Desktop/gcc/configure --prefix=/usr/local/gcc/gcc- 4.3.0
> --enable-shared --enable-threads=posix --enable-tls
> --with-gmp=/usr/lib --with-mpfr=/usr/lib
>
> then I ran make bootsrap and went to bed. I didn't have enough
> patience to wait for the tests make -k check process and I commited
> make install :)
> then I symbolically linked gcc , cpp , g++ c++ gccbug gcj gcov
> gfortran from :/usr/local/gcc/gcc-4.3.0/bin to /usr/bin
> then I simply tried to ./configure a piece of code and the shell said:
>
> checking for C++ compiler default output file name... configure:
> error: C++ compiler cannot create executables
> See `config.log' for more details.
>
> The config.log points out:
>
> configure:2113: g++ conftest.cc >&5
> /usr/bin/ld: crtbegin.o: No such file: No such file or directory
The part about symlink surely wasn't in the installation instructions.
You don't want to set up a build in such a way that your original gcc
can be trashed. Test your new compiler in a separate installation from
the original, or before installing. Then, if you want to replace the
compiler in /usr/bin, reconfigure with -prefix=usr and install.
next prev parent reply other threads:[~2007-09-14 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c51c48d0709140011t7806975er6d07c148481ae822@mail.gmail.com>
2007-09-14 8:54 ` IVAN ANGELOV
2007-09-14 15:20 ` Tim Prince [this message]
2001-03-19 9:50 lbergman
2001-03-19 21:16 ` Alexandre Oliva
2001-03-20 7:31 ` lbergman
2001-03-20 10:20 ` Alexandre Oliva
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=46EA8E25.9090508@computer.org \
--to=tprince@computer.org \
--cc=gcc-help@gcc.gnu.org \
--cc=ivangotoy@gmail.com \
/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).