public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "James K. Lowden" <jklowden@schemamania.org>
To: gcc@gcc.gnu.org
Cc: Andrew Pinski <pinskia@gmail.com>
Subject: Re: How do I create a GCC source code tarball?
Date: Fri, 7 Oct 2022 18:53:29 -0400	[thread overview]
Message-ID: <20221007185329.70731d284d959b229a908d09@schemamania.org> (raw)
In-Reply-To: <CA+=Sn1ndLDUW1bquv6KC=zNgjsyD4ZjfLDExNbm55J-s9yjnQQ@mail.gmail.com>

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: 

	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. 

I'm happy to open a PR or submit a patch.

--jkl


  parent reply	other threads:[~2022-10-07 22:53 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 [this message]
2022-10-10  6:36     ` Richard Biener

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=20221007185329.70731d284d959b229a908d09@schemamania.org \
    --to=jklowden@schemamania.org \
    --cc=gcc@gcc.gnu.org \
    --cc=pinskia@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).