From: Ian Lance Taylor <iant@google.com>
To: Steffen Dettmer <steffen.dettmer@googlemail.com>
Cc: binutils@sourceware.org
Subject: Re: binutils prerequisites (recent zlib version - what else?)
Date: Tue, 26 Apr 2011 16:27:00 -0000 [thread overview]
Message-ID: <mcr39l5m118.fsf@google.com> (raw)
In-Reply-To: <BANLkTimD7ftqv6+=Ho_Mr4uyrcUufCQQBA@mail.gmail.com> (Steffen Dettmer's message of "Tue, 26 Apr 2011 16:52:31 +0200")
Steffen Dettmer <steffen.dettmer@googlemail.com> writes:
> So for now the additional configure option `--with-zlib=no'
> should avoid (or workaround?) my issue.
By the way, this can also be written as --without-zlib.
> I assume that when zlib is installed, then at least some "recent"
> version must be installed, because there is no
> `--with-zlib=internal' or alike, is this correct?
Yes.
> I noticed that gcc has an option `--with-system-zlib', so in
> total I would need --with-system-zlib=no, but if I understand
> correctly this is not supported by binutil/bfd.
> Did I understand correctly?
Unrecognized --with options are ignored. The difference in the options
is because for gcc, zlib is not optional when building libjava. For the
binutils zlib is always optional.
Ian
next prev parent reply other threads:[~2011-04-26 16:27 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 [this message]
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
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=mcr39l5m118.fsf@google.com \
--to=iant@google.com \
--cc=binutils@sourceware.org \
--cc=steffen.dettmer@googlemail.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).