From: Richard Biener <richard.guenther@gmail.com>
To: "James K. Lowden" <jklowden@schemamania.org>
Cc: gcc@gcc.gnu.org
Subject: Re: How do I create a GCC source code tarball?
Date: Mon, 10 Oct 2022 08:36:55 +0200 [thread overview]
Message-ID: <CAFiYyc1S_=W1tr42BkZ8Z--Sus_2xzhjc=SHFeh9w02j+mQ_eQ@mail.gmail.com> (raw)
In-Reply-To: <20221007185329.70731d284d959b229a908d09@schemamania.org>
On Sat, Oct 8, 2022 at 12:54 AM James K. Lowden
<jklowden@schemamania.org> wrote:
>
> On Tue, 4 Oct 2022 12:03:12 -0700
> Andrew Pinski via Gcc <gcc@gcc.gnu.org> wrote:
>
> > > Building a full distribution of this tree isn't done
> > > via 'make dist'. Check out the etc/ subdirectory
> ...
> > You just tar up the source.
> > You could use maintainer-scripts/gcc_release to make a snapshot but in
> > the end it just does `tar xcfj file.tar.bz2 gcc` .
>
> If I may, the error message would be improved by making it shorter:
>
> > Building a full distribution of this tree isn't done
> > via 'make dist'.
>
> since that at least would be accurate! But why not just make it work
> again? Change the dist target in Makefile.in:
Note that etc/ is present in the src tree (from binutils/gdb), the complication
here is that the toplevel Makefile is shared between gcc and binutils/gdb
so we can't simply invoke something from maintainer-scripts which isn't
present on the binutils/gdb side ...
> dist:
> tar xcfj file.tar.bz2 gcc
> or
> dist:
> $(srcdir)/maintainer-scripts/gcc_release $(RELEASE_OPTS)
>
> where RELEASE_OPTS has some simple default. The user wishing to know
> more can inspect the script to determine what options to use.
>
> I spent several hours looking for information on how to do this. I
> wasn't counting on a decade of misdirection. It's not mentioned
> anywhere that I could find in the source tree or the wiki. I missed
> maintainer-scripts among the 75 files because it wasn't in upper case,
> where I expect to find developer information. If the process of
> generating nightly tarballs is documented, I missed that, too.
There is https://gcc.gnu.org/releasing.html and assorted pages where
such stuff is documented. There's probably something similar on
the binutils/gdb side.
I guess the best thing we can do is improve the wording of the
'make dist' diagnostic plus eventually have parts of it documented
in sourcebuild.texi
Richard.
> I'm happy to open a PR or submit a patch.
>
> --jkl
>
prev parent reply other threads:[~2022-10-10 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 23:31 Robert Dubner
2022-10-04 19:03 ` Andrew Pinski
2022-10-04 20:44 ` Robert Dubner
2022-10-07 22:53 ` James K. Lowden
2022-10-10 6:36 ` Richard Biener [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='CAFiYyc1S_=W1tr42BkZ8Z--Sus_2xzhjc=SHFeh9w02j+mQ_eQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jklowden@schemamania.org \
/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).