From: Steffen Dettmer <steffen.dettmer@googlemail.com>
To: binutils@sourceware.org
Subject: Re: binutils prerequisites (recent zlib version - what else?)
Date: Tue, 26 Apr 2011 18:39:00 -0000 [thread overview]
Message-ID: <BANLkTimipvrmJdTKKfwhezTf1979Y4Sbpg@mail.gmail.com> (raw)
In-Reply-To: <mcry62wq3jh.fsf@coign.corp.google.com>
On Tue, Apr 26, 2011 at 8:18 PM, Ian Lance Taylor <iant@google.com> wrote:
> kevin diggs <diggskevin38@gmail.com> writes:
>
>> On Tue, Apr 26, 2011 at 11:26 AM, Ian Lance Taylor <iant@google.com> wrote:
>>>
>>> Unrecognized --with options are ignored. The difference in the
>>>
>>> Ian
>>>
>> Why? Wouldn't it be better to tell the poor, confused user that they
>> are configuring up the wrong tree?
Here I think the binutils/bfd/configure should check for ../../zlib,
which will be there in "gcc combined build", and use it, shouldn't it?
but of course then zlib needs to be built first etc.
maybe configure --help should have some support for AC_CONFIG_SUBDIRS?
However, in this case it would still be missleading, because
binutils have --with-zlib (but no support for --with-system-zlib),
gcc has only (?) --with-system-zlib, so it seems to be let's say "incompatible"
a bit.
Steffen
next prev parent reply other threads:[~2011-04-26 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 12:44 Steffen Dettmer
2011-04-26 14:52 ` Steffen Dettmer
2011-04-26 16:27 ` Ian Lance Taylor
2011-04-26 16:34 ` Steffen Dettmer
2011-04-26 17:04 ` H.J. Lu
2011-04-26 18:34 ` Steffen Dettmer
2011-04-26 18:05 ` kevin diggs
2011-04-26 18:11 ` kevin diggs
2011-04-26 18:21 ` Ian Lance Taylor
2011-04-26 18:19 ` Ian Lance Taylor
2011-04-26 18:39 ` Steffen Dettmer [this message]
2011-04-26 18:44 ` Steffen Dettmer
2011-04-27 6:08 ` Ralf Wildenhues
2011-08-04 22:08 ` [PATCH] Correct zlib checks [Was: binutils prerequisites (recent zlib version - what else?)] Maciej W. Rozycki
2011-08-05 7:52 ` Paolo Bonzini
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=BANLkTimipvrmJdTKKfwhezTf1979Y4Sbpg@mail.gmail.com \
--to=steffen.dettmer@googlemail.com \
--cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).