From: Nick Clifton <nickc@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, Matthias Klose <doko@ubuntu.com>
Cc: Jeff Law <law@redhat.com>,
gdb-patches@sourceware.org,
binutils <binutils@sourceware.org>
Subject: Re: [patch] update zlib to the 1.2.10 release.
Date: Mon, 23 Jan 2017 16:01:00 -0000 [thread overview]
Message-ID: <43e32524-d616-7957-e279-c4bd51a95ba0@redhat.com> (raw)
In-Reply-To: <20170123040915.knf76kwgwxji2ng4@adacore.com>
Hi Joel,
> Can you tell us what these changes are? Currently nightly source
> packaging is broken while configuring zlib.
> ./config.status: line 1191: ./../../config-ml.in: No such file or directory
> Makefile:10001: recipe for target 'configure-zlib' failed
I have checked in a patch to restore the old behaviour to zlib's Makefile
and allow building with srcdir == builddir. At least for now. If we do
decide to ban this behaviour then this patch can be reverted, or a top level
check and warning added.
Cheers
Nick
zlib/ChangeLog.bin-gdb
2017-01-23 Nick Clifton <nickc@redhat.com>
* configure.ac: Restore old behaviour of only enabling multilibs
when a target subdirectory is defined. This allows building with
srcdir == builddir.
* configure: Regenerate.
prev parent reply other threads:[~2017-01-23 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 14:45 Matthias Klose
2017-01-12 21:17 ` Jeff Law
2017-01-12 21:27 ` Matthias Klose
2017-01-12 21:38 ` Jeff Law
2017-01-12 21:39 ` Jeff Law
2017-01-13 12:14 ` Matthias Klose
2017-01-22 18:01 ` Matthias Klose
2017-01-22 18:12 ` NightStrike
2017-01-22 18:42 ` Matthias Klose
2017-01-23 22:57 ` Iain Buclaw
2017-01-23 4:09 ` Joel Brobecker
2017-01-23 9:10 ` Matthias Klose
2017-01-23 16:01 ` Nick Clifton [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=43e32524-d616-7957-e279-c4bd51a95ba0@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=doko@ubuntu.com \
--cc=gdb-patches@sourceware.org \
--cc=law@redhat.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).