From: Kai Ruottu <kai.ruottu@wippies.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Cc: gcc_mailinglist@abwesend.de
Subject: Re: Aw: Re: compile gcc 4.7.2 Ubuntu 12.04 fails with GCC_NO_EXECUTABLES
Date: Thu, 07 Mar 2013 21:12:00 -0000 [thread overview]
Message-ID: <513902D3.8040509@wippies.com> (raw)
In-Reply-To: <5138FED7.3050105@wippies.com>
7.3.2013 22:55, Kai Ruottu kirjoitti:
> 7.3.2013 22:19, gcc_mailinglist@abwesend.de kirjoitti:
>> /usr/bin/ld: cannot find crt1.o: No such file or directory
>> /usr/bin/ld: cannot find crti.o: No such file or directory
>
> The previous seems to be the problem... Basically the Ubuntu's custom
> ld should know where these startups are, in '/usr/lib/x86_64-linux-gnu'
> I think. Please check where they really are in your system...
>
> If the command 'ld -verbose' (used with '| less') doesn't show the
> places
> where they are in the 'SEARCH_DIR' or something in the output
> beginning, then
> something is broken :-(
>
> Searching with Google for "building GCC for Ubuntu" may tell what are the
> problems and workarounds, Ubuntu isn't a "standard" Linux but somehow
> "custom".
>
OK, in :
http://solarianprogrammer.com/2012/04/13/building-gcc-4-7-on-ubuntu-12-04/
there were instructions to set in environment (in your case) :
export LD_LIBRARY_PATH=/opt/gcc_4_7_2/lib:$LD_LIBRARY_PATH
export LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/
export C_INCLUDE_PATH=/usr/include/x86_64-linux-gnu
export CPLUS_INCLUDE_PATH=/usr/include/x86_64-linux-gnu
before 'configure' and 'make' and make a symlink :
sudo ln -s /usr/lib/x86_64-linux-gnu /usr/lib64
before 'make install'
next prev parent reply other threads:[~2013-03-07 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 19:40 Daniel Albers
2013-03-07 20:13 ` Kai Ruottu
2013-03-07 20:23 ` Jonathan Wakely
[not found] ` <trinity-11eb852c-f6de-44f2-afeb-9c410c8d709f-1362687570409@3capp-gmx-bs09>
[not found] ` <5138FED7.3050105@wippies.com>
2013-03-07 21:12 ` Kai Ruottu [this message]
2013-03-07 22:12 ` Aw: Re: " gcc_mailinglist
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=513902D3.8040509@wippies.com \
--to=kai.ruottu@wippies.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc_mailinglist@abwesend.de \
/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).