From: Joel Brobecker <brobecker@adacore.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: gcc-patches@gcc.gnu.org, binutils@sourceware.org,
gdb-patches@sourceware.org
Subject: Re: [RFA] Add --with-libz-prefix option in config/zlib.m4
Date: Wed, 07 Jan 2015 17:02:00 -0000 [thread overview]
Message-ID: <20150107170224.GP5445@adacore.com> (raw)
In-Reply-To: <FF7C0642-8F80-4D67-B5E1-92219910FC89@adacore.com>
> > This patch enhances config/zlib.m4 to introduce an extra option
> > --with-libz-prefix which allows us to provide the location of
> > the zlib library we want to use during the build.
>
> I prefer the gcc way to provide external library:
>
> --with-zlib -> system zlib used
> --with-zlib=pathname -> zlib from pathname is used
Unfortunately, we took a different route with GDB (with-...-prefix).
For instance:
--with-libiconv-prefix
--with-liblzma-prefix
--with-libbabeltrace-prefix
We already have a really nice macro that takes care of a lot of
configury for us with respect to lib depenencies, which I see
in gcc's root configure.ac that gmp/mpfr/mpc options is done
via specific code.
What I'm getting at is that, to achieve your prefered option
(which I agree is more elegant), it would take a significant
effort.
--
Joel
next prev parent reply other threads:[~2015-01-07 17:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 14:46 Joel Brobecker
2015-01-07 16:01 ` Tristan Gingold
2015-01-07 17:02 ` Joel Brobecker [this message]
2015-02-19 7:55 ` Thomas Schwinge
2015-02-19 7:58 ` Thomas Schwinge
2015-01-21 7:49 ` ping: " Joel Brobecker
2015-01-21 8:22 ` Tristan Gingold
2015-01-21 8:33 ` Joel Brobecker
2015-02-04 3:57 ` ping^2: " Joel Brobecker
2015-02-18 12:09 ` ping #3: " Joel Brobecker
2015-02-18 12:56 ` H.J. Lu
2015-02-18 16:55 ` Mike Frysinger
2015-02-18 16:58 ` H.J. Lu
2015-02-18 19:44 ` Mike Frysinger
2015-02-18 19:52 ` H.J. Lu
2015-02-18 20:32 ` Mark Wielaard
2015-02-18 20:42 ` Jakub Jelinek
2015-02-18 20:53 ` H.J. Lu
2015-02-18 21:54 ` Mark Wielaard
2015-02-18 22:03 ` H.J. Lu
2015-02-18 22:21 ` Mike Frysinger
2015-02-18 22:24 ` H.J. Lu
2015-02-18 23:10 ` Mike Frysinger
2015-02-19 7:17 ` Mark Wielaard
2015-02-19 13:52 ` H.J. Lu
2015-02-20 8:01 ` Mark Wielaard
2015-02-18 17:00 ` Joel Sherrill
2015-02-19 2:42 ` Joel Brobecker
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=20150107170224.GP5445@adacore.com \
--to=brobecker@adacore.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.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).