public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Frans de Boer <frans@fransdb.nl>
To: crossgcc@sourceware.org
Subject: Re: addToolVersion.sh
Date: Wed, 02 Jan 2019 17:11:00 -0000	[thread overview]
Message-ID: <b018b898-a0fa-849c-3ddc-9f12bc440037@fransdb.nl> (raw)
In-Reply-To: <7c40d7ef-8484-c736-b70a-349c8dd94083@gmail.com>

On 02-01-19 17:03, Josh Branning wrote:
> On 02/01/19 12:00, 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.
>>
>
> Hi there, this is probably not the best way, but is how I did so for 
> the linux-libre kernel;
>
> https://git.parabola.nu/abslibre.git/tree/pcr/crosstool-ng/ctng-libre.patch 
>
>
> Josh

Well, if you have not yet compiled the software, then you only need to 
add a directory with a chsum file for the wanted kernel software. Not 
sure if this approach for linux-libre-* works too.
But having compiled the software and you want to patch (update) only, 
you also have to add some lines to the linux.in file. The structure is 
also given within the linux.in file.

So, it is fairly easy to make a script file for that. Making a script 
for all others pieces of software might become a bigger hurdle to take, 
but still doable.

Maybe I use/adapt the tool from the 1.23 release. Still wondering why it 
was not (anymore) included in the git (master) repository.

-- Frans.

  reply	other threads:[~2019-01-02 17: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   ` Frans de Boer [this message]
2019-01-03  3:11 ` addToolVersion.sh Alexey Neyman
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=b018b898-a0fa-849c-3ddc-9f12bc440037@fransdb.nl \
    --to=frans@fransdb.nl \
    --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).