From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: Re: addToolVersion.sh
Date: Thu, 03 Jan 2019 03:11:00 -0000 [thread overview]
Message-ID: <ab78447e-56dc-5b53-f187-c607e52017fb@att.net> (raw)
In-Reply-To: <f9f5e942-b223-fd80-96db-1503f700014c@fransdb.nl>
That section in the docs (which mentions addToolVersion.sh) is outdated
and needs to be updated. Please file an issue; my laptop broke so I am
without a machine where I can do ct-ng development at this time.
I am not sure where you found a reference to gen-version.sh; I couldn't
find any in current crosstool-NG, nor in its docs.
The current procedure to add a new version of a component is to:
1. Copy/create a directory for a new version under packages/PACKAGE-NAME/
2. Verify the package signature, update the checksums for all downloads,
check if the patches apply (and if necessary, update the patches). All
that is done by running maintainer/manage-packages.sh script; run it
without arguments to get some help.
Regards,
Alexey.
On 1/2/19 4:00 AM, Frans de Boer wrote:
> Dear Reader,
>
> I am using the git version of crosstool-NG and want to add a new
> kernel. However, the above mentioned tool as well as the potential
> replacement gen-versions.sh are nowhere to be found.
>
> I can add things manually in linux.in and in the new chksum file, but
> that seems a bit awkward knowing that there have been (a) tool(s) for
> this purpose.
>
> Suggestion?
>
> Regards, Frans.
>
>
next prev parent reply other threads:[~2019-01-03 3:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 12:00 addToolVersion.sh Frans de Boer
2019-01-02 16:03 ` addToolVersion.sh Josh Branning
2019-01-02 17:11 ` addToolVersion.sh Frans de Boer
2019-01-03 3:11 ` Alexey Neyman [this message]
2019-01-03 9:04 ` addToolVersion.sh Frans de Boer
2019-01-03 17:44 ` addToolVersion.sh Alexey Neyman
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=ab78447e-56dc-5b53-f187-c607e52017fb@att.net \
--to=stilor@att.net \
--cc=crossgcc@sourceware.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).