public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robert Dubner <rdubner@symas.com>
To: "Andrew Pinski" <pinskia@gmail.com>
Cc: <gcc@gcc.gnu.org>
Subject: RE: How do I create a GCC source code tarball?
Date: Tue, 4 Oct 2022 15:44:39 -0500 (CDT)	[thread overview]
Message-ID: <04e901d8d832$1f738b20$5e5aa160$@symas.com> (raw)
In-Reply-To: <CA+=Sn1ndLDUW1bquv6KC=zNgjsyD4ZjfLDExNbm55J-s9yjnQQ@mail.gmail.com>

I had a feeling that's what the answer was going to be, but, well, I figured 
it couldn't hurt to ask.

Especially because I hadn't before noticed the maintainer-scripts 
subdirectory.  That alone made asking worth it.

Thank you very much,

Bob Dubner

-----Original Message-----
From: Andrew Pinski <pinskia@gmail.com>
Sent: Tuesday, October 4, 2022 15:03
To: Robert Dubner <rdubner@symas.com>
Cc: gcc@gcc.gnu.org
Subject: Re: How do I create a GCC source code tarball?

On Mon, Oct 3, 2022 at 4:32 PM Robert Dubner <rdubner@symas.com> wrote:
>
> I have modified the source code of GCC, and I need a tarball for that
> modified source.
>
> My code is based on the trunk branch of the repository at
> git://gcc.gnu.org/git/gcc.git
>
> I attempted to execute "make dist", and have encountered the response
>
>       Building a full distribution of this tree isn't done
>       via 'make dist'.  Check out the etc/ subdirectory
>
> I have been unable to locate a subdirectory name "etc/".
>
> With that as background, my question is:
>
> How do I create a source code tarball for GCC?

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` .

Thanks,
Andrew

>
> Thanks very much for any help.
>
>

  reply	other threads:[~2022-10-04 20:44 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 [this message]
2022-10-07 22:53   ` James K. Lowden
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='04e901d8d832$1f738b20$5e5aa160$@symas.com' \
    --to=rdubner@symas.com \
    --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).