From: Joel Brobecker <brobecker@adacore.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
simark@simark.ca, gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: [RFA/gdb-9-branch] Abort configure immediately if building GDB in tree
Date: Sat, 01 Feb 2020 10:26:00 -0000 [thread overview]
Message-ID: <20200201102647.GC19442@adacore.com> (raw)
In-Reply-To: <20200201101940.GB19442@adacore.com>
> > >>> I'm wondering what to do here. I think I found a hacky and ugly
> > >>> solution here, but I'm trying to see if there's a better approach.
> > >>
> > >> A special command-line switch to 'configure', to be used by
> > >> src-release.sh?
> > >
> > > A quick attempt here didn't really work. The script is able to finish
> > > the build and create a tarball, but for some reason the gdb directory is
> > > not configured/built.
> >
> > OK, I think I have something that works. When 'configure' is invoked
> > with '--enable-src-release-build', a tarball is generated and, as far as
> > I have checked, contains the correct snapshot.
> >
> > WDYT?
>
> Thanks! I didn't realize that this would impact source packaging
> like that.
>
> Let's go with your patch. I'm about to start working on the release,
> so I'll apply it for you.
Or not. Jonah just reported another blocking issue :-(, so I won't
be creating this release this weekend.
So the "good" news is that you can push the patch yourself!
--
Joel
next prev parent reply other threads:[~2020-02-01 10:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 7:30 Joel Brobecker
2020-01-06 3:06 ` Simon Marchi
2020-01-17 18:24 ` Joel Brobecker
2020-01-17 18:24 ` Simon Marchi
2020-01-17 18:43 ` Joel Brobecker
2020-01-30 22:56 ` Sergio Durigan Junior
2020-01-31 8:55 ` Eli Zaretskii
2020-01-31 21:02 ` Sergio Durigan Junior
2020-01-31 22:52 ` Sergio Durigan Junior
2020-02-01 7:24 ` Eli Zaretskii
2020-02-01 10:19 ` Joel Brobecker
2020-02-01 10:26 ` Joel Brobecker [this message]
2020-02-01 20:38 ` Sergio Durigan Junior
2020-01-17 18:26 ` Tom Tromey
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=20200201102647.GC19442@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=simark@simark.ca \
--cc=tom@tromey.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