Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Binutils <binutils@sourceware.org>,
	GDB <gdb-patches@sourceware.org>
Subject: Re: ping #3: [RFA] Add --with-libz-prefix option in config/zlib.m4
Date: Thu, 19 Feb 2015 02:42:00 -0000	[thread overview]
Message-ID: <20150219024204.GE23529@adacore.com> (raw)
In-Reply-To: <CAMe9rOp9YQrhwwrmqRa+a-04BNvd+p9_MVgxkiVhgt+6TkDb7g@mail.gmail.com>

> Why do you want to turn off zlib? On Linux/x86,  zlib is required
> for assembler.  At least, you should issue an error when --without-libz
> is used in binutils for Linux/x86 target.

I am trying to do the exact opposite, which is to provide an option
to compile WITH zlib, but using an install at a non-standard location.

> I guess someone has asked it before.  Why can't zlib be made the
> same as
> 
>   --with-mpc=PATH         specify prefix directory for installed MPC package.
>                           Equivalent to --with-mpc-include=PATH/include plus
>                           --with-mpc-lib=PATH/lib
>   --with-mpc-include=PATH specify directory for installed MPC include files
>   --with-mpc-lib=PATH     specify directory for the installed MPC library
> 
> It is more flexible than your patch.  If you have some existing packages
> which use your scheme, you can translate the configure command line
> options to this one.

This is fustrating. I already answered that question.

-- 
Joel


      parent reply	other threads:[~2015-02-19  2:42 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
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 [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=20150219024204.GE23529@adacore.com \
    --to=brobecker@adacore.com \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.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