From: Uri Moszkowicz <uri@4refs.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Trouble building AR
Date: Wed, 19 Jun 2013 22:04:00 -0000 [thread overview]
Message-ID: <CAMJd5ASmSWq6tgHWJoO2NDF-mx0=3kF7ySMN4zfcXiQ54aaFLQ@mail.gmail.com> (raw)
In-Reply-To: <CAKOQZ8xQ_VuQonBLqLqm4QVg9eO9CpZjqG-a5BrMpgVc=QOmQA@mail.gmail.com>
Log uploaded here:
http://www.4refs.com/gcc.log
It seems to be looking in the right places just not for the right
file. It looks for "real-ld", "collect-ld", and "ld-new" but not "ld".
On Wed, Jun 19, 2013 at 4:38 PM, Ian Lance Taylor <iant@google.com> wrote:
> On Wed, Jun 19, 2013 at 2:20 PM, Uri Moszkowicz <uri@4refs.com> wrote:
>> No luck - same error :( I see the following list in config.log:
>>
>> /tools/gcc-4.7.2/lib/gcc/x86_64-unknown-linux-gnu/4.7.2/../../../../x86_64-unknown-linux-gnu/bin/ld:
>> cannot find -lpwl
>> collect2: error: ld returned 1 exit status
>
> Errors in config.log are normal.
>
>> Is that of interest? Maybe I should just try a different GCC /
>> binutils combination. Any other suggestions to help figure out what's
>> wrong?
>
> You said the program is failing when you try to use it. Try running
> gcc -o foo foo.c -Wl,-debug
> That should show all the places where the collect2 program is looking
> for ld. Then we need to find out why it is not looking in the right
> place.
>
> Ian
next prev parent reply other threads:[~2013-06-19 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 20:08 Uri Moszkowicz
2013-06-18 23:16 ` Ian Lance Taylor
2013-06-19 19:10 ` Uri Moszkowicz
2013-06-19 19:25 ` Ian Lance Taylor
2013-06-19 21:21 ` Uri Moszkowicz
2013-06-19 21:38 ` Ian Lance Taylor
2013-06-19 22:04 ` Uri Moszkowicz [this message]
2013-06-19 23:06 ` Ian Lance Taylor
2013-06-21 19:19 ` Uri Moszkowicz
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='CAMJd5ASmSWq6tgHWJoO2NDF-mx0=3kF7ySMN4zfcXiQ54aaFLQ@mail.gmail.com' \
--to=uri@4refs.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).