From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: update zlib handling
Date: Thu, 02 Apr 2015 10:34:00 -0000 [thread overview]
Message-ID: <551D1B2A.5020707@foss.arm.com> (raw)
In-Reply-To: <20150402053537.GB9832@vapier>
On 02/04/15 06:35, Mike Frysinger wrote:
> On 01 Apr 2015 15:01, Richard Earnshaw wrote:
>> On 01/04/15 06:08, Mike Frysinger wrote:
>>> With zlib being mandatory, and the updated m4 configs, we need to regen
>>> and use the new settings w/bfd to avoid linkage errors.
>>>
>>> Committed.
>>
>> This seems to cause:
>>
>> make[3]: *** No rule to make target `-L../zlib', needed by `run'. Stop.
>> make[3]: Leaving directory `/work/rearnsha/scratch/gnu/gcc/trunk/sim/arm'
>> make[2]: *** [all] Error 1
>>
>>
>> The problem seems to be that ZLIB is used in BFD_LIB, which is used in
>> LIBDEPS which is a dependency for "run".
>
> i think H.J.Lu checked in a patch to fix this
> -mike
>
Yep, seems to be working now.
R.
prev parent reply other threads:[~2015-04-02 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 5:08 Mike Frysinger
2015-04-01 14:01 ` Richard Earnshaw
2015-04-01 17:16 ` Mike Frysinger
2015-04-02 5:35 ` Mike Frysinger
2015-04-02 10:34 ` Richard Earnshaw [this message]
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=551D1B2A.5020707@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=gdb-patches@sourceware.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