public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.com>
To: Iain Buclaw <ibuclaw@gdcproject.org>,
	       Richard Biener <richard.guenther@gmail.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
	       gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Add target-zlib to top-level configure, use zlib from libphobos
Date: Sat, 16 Feb 2019 12:44:00 -0000	[thread overview]
Message-ID: <aa873c40-6590-45a2-c6db-89fe968fcd8b@ubuntu.com> (raw)
In-Reply-To: <CABOHX+c2VyGsrkUVAkr_XjG-0K6toG7TXa40_k-G8GZQvv2OTw@mail.gmail.com>

On 12.02.19 21:54, Iain Buclaw wrote:
> On Tue, 12 Feb 2019 at 10:40, Richard Biener <richard.guenther@gmail.com> wrote:
>>
>> On Sat, Feb 9, 2019 at 10:37 AM Iain Buclaw <ibuclaw@gdcproject.org> wrote:
>>>
>>> On Mon, 28 Jan 2019 at 13:10, Richard Biener <richard.guenther@gmail.com> wrote:
>>>>
>>>> On Mon, Jan 21, 2019 at 7:35 PM Iain Buclaw <ibuclaw@gdcproject.org> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Following on from the last, this adds target-zlib to target_libraries
>>>>> and updates libphobos build scripts to link to libz_convenience.a.
>>>>> The D front-end already has target-zlib in d/config-lang.in.
>>>>>
>>>>> Is the top-level part OK?  I considered disabling target-zlib if
>>>>> libphobos is not being built, but decided against unless it's
>>>>> requested.
>>>>
>>>> Hmm, you overload --with-system-zlib to apply to both host and target
>>>> (I guess it already applied to build), not sure if that's really desired?
>>>> I suppose libphobos is the first target library linking against zlib?
>>>>
>>>
>>> Originally, libgcj linked to zlib.
>>>
>>>> You are also falling back to in-tree zlib if --with-system-zlib was
>>>> specified but no zlib was found - I guess for cross builds that
>>>> will easily get not noticed...  The toplevel --with-system-zlib makes
>>>> it much harder and simply fails.
>>>>
>>>
>>> OK, so keep --with-target-system-zlib to distinguish between the two?
>>
>> Yes, and fail if specificed but not found.
>>
> 
> Updated patch.  Checked that it correctly fails when
> --with-target-system-zlib and zlib missing.

For the GC enabled libobjc I added an --enable-objc-gc=auto to fall-back to the
in-tree library when no system library is found. Could you do the same for zlib?
There might be some multilib variants missing in distros.

Matthias

  reply	other threads:[~2019-02-16 12:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 18:35 Iain Buclaw
2019-01-28 12:18 ` Richard Biener
2019-01-28 23:27   ` Joseph Myers
2019-02-09  9:37   ` Iain Buclaw
2019-02-12  9:40     ` Richard Biener
2019-02-12 20:55       ` Iain Buclaw
2019-02-16 12:44         ` Matthias Klose [this message]
2019-02-17 16:07           ` Iain Buclaw
2019-02-18 13:26             ` Matthias Klose
2019-03-29 23:32               ` Iain Buclaw
2019-04-06 15:27                 ` Matthias Klose
2019-04-06 17:06                   ` Iain Buclaw
2019-04-11 16:00                     ` Iain Buclaw
2019-04-12 16:25                       ` Jeff Law

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=aa873c40-6590-45a2-c6db-89fe968fcd8b@ubuntu.com \
    --to=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ibuclaw@gdcproject.org \
    --cc=joseph@codesourcery.com \
    --cc=richard.guenther@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).