From: Abdul Wahid Memon <engrwahidmemon@gmail.com>
To: gcc-help@gcc.gnu.org
Cc: gideon425.gb5@mailnull.com
Subject: Re: Problem building gcc
Date: Mon, 19 Dec 2011 18:45:00 -0000 [thread overview]
Message-ID: <CAM8ts8d5Er5GgndH_qxfL1oVUdRD0sU0VTkoz6YqQ9yBP-vfjQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1111300052430.2529@laptop-mg.saclay.inria.fr>
Hello everyone
I also got the same error and according to your solution I set
LIBRARY_PATH=/usr/lib/x86_64-linux-gnu but then the compilation
process complains that
checking LIBRARY_PATH variable... contains current directory
configure: error:
*** LIBRARY_PATH shouldn't contain the current directory when
*** building gcc. Please change the environment variable
*** and run configure again.
make[2]: *** [configure-stage2-gcc] Error 1
make[2]: Leaving directory `/home/abdul/cc02/gcc-4.6.2/src-infra/obj-gcc'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory `/home/abdul/cc02/gcc-4.6.2/src-infra/obj-gcc'
make: *** [all] Error 2
Regards
Abdul
On Wed, Nov 30, 2011 at 12:56 AM, Marc Glisse <marc.glisse@inria.fr> wrote:
> On Tue, 29 Nov 2011, gideon425.gb5@mailnull.com wrote:
>
>> I am having problems building gcc 4.6.2
>>
>> I am using Ubuntu 11.10
>>
>> Here is the error
>>
>> /usr/bin/ld: cannot find crti.o: No such file or directory
>
>
> Here is the solution:
> export LIBRARY_PATH=/usr/lib/x86_64-linux-gnu
>
>
>> What additional information can I supply to help understand this problem?
>
>
> Problem understood, gcc doesn't currently support debian and the derivative
> distributions like ubuntu.
>
> --
> Marc Glisse
next prev parent reply other threads:[~2011-12-19 18:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 8:35 gideon425.gb5
2011-11-30 8:58 ` Marc Glisse
2011-12-19 18:45 ` Abdul Wahid Memon [this message]
2011-12-19 21:21 ` Ian Lance Taylor
2011-12-20 2:25 ` Abdul Wahid Memon
2011-12-20 5:07 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2010-05-06 5:40 Pavel Pavlov
2010-05-06 6:02 ` Pavel Pavlov
2010-05-06 6:16 ` Ian Lance Taylor
2010-05-06 6:40 ` Pavel Pavlov
2010-05-07 19:03 ` Ralf Wildenhues
2010-05-07 23:04 ` Pavel Pavlov
2008-08-28 13:28 problem " collinr
2008-08-28 13:42 ` Brian Dessent
2000-11-02 10:59 Problem building GCC Andrew Dumaresq
2000-11-03 18:51 ` 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=CAM8ts8d5Er5GgndH_qxfL1oVUdRD0sU0VTkoz6YqQ9yBP-vfjQ@mail.gmail.com \
--to=engrwahidmemon@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gideon425.gb5@mailnull.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).