* addToolVersion.sh
@ 2019-01-02 12:00 Frans de Boer
2019-01-02 16:03 ` addToolVersion.sh Josh Branning
2019-01-03 3:11 ` addToolVersion.sh Alexey Neyman
0 siblings, 2 replies; 6+ messages in thread
From: Frans de Boer @ 2019-01-02 12:00 UTC (permalink / raw)
To: crossgcc
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: addToolVersion.sh
2019-01-02 12:00 addToolVersion.sh Frans de Boer
@ 2019-01-02 16:03 ` Josh Branning
2019-01-02 17:11 ` addToolVersion.sh Frans de Boer
2019-01-03 3:11 ` addToolVersion.sh Alexey Neyman
1 sibling, 1 reply; 6+ messages in thread
From: Josh Branning @ 2019-01-02 16:03 UTC (permalink / raw)
To: crossgcc
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: addToolVersion.sh
2019-01-02 16:03 ` addToolVersion.sh Josh Branning
@ 2019-01-02 17:11 ` Frans de Boer
0 siblings, 0 replies; 6+ messages in thread
From: Frans de Boer @ 2019-01-02 17:11 UTC (permalink / raw)
To: crossgcc
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: addToolVersion.sh
2019-01-02 12:00 addToolVersion.sh Frans de Boer
2019-01-02 16:03 ` addToolVersion.sh Josh Branning
@ 2019-01-03 3:11 ` Alexey Neyman
2019-01-03 9:04 ` addToolVersion.sh Frans de Boer
1 sibling, 1 reply; 6+ messages in thread
From: Alexey Neyman @ 2019-01-03 3:11 UTC (permalink / raw)
To: crossgcc
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.
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: addToolVersion.sh
2019-01-03 3:11 ` addToolVersion.sh Alexey Neyman
@ 2019-01-03 9:04 ` Frans de Boer
2019-01-03 17:44 ` addToolVersion.sh Alexey Neyman
0 siblings, 1 reply; 6+ messages in thread
From: Frans de Boer @ 2019-01-03 9:04 UTC (permalink / raw)
To: crossgcc
On 03-01-19 04:11, Alexey Neyman wrote:
> 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.
>>
>>
Hi Alexey,
The gen-versions.sh was introduced by yourself. I saw a posting of
2017-7-13 from your hand ;)
As for the outdated version of the documentation, it is the version
published on the web site and addresses 1.23 also.
And the procedure for updating/adding new versions is clear. Did figure
out step 1 already, but did not realize that manage-packages.sh was the
tool to use to update the xxxx.in file. I only browse through it,
probably because I had the former tool on my mind.
Anyhow, I will verify your pointer later on.
Question: it seems that crosstool-NG has evolved well beyond the early
2017 release. Don't you think it is time to release an updated version?
Also, it seems that you prefer git pull requests for updated/new pieces,
this applies to the documentation too?
--- Frans.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: addToolVersion.sh
2019-01-03 9:04 ` addToolVersion.sh Frans de Boer
@ 2019-01-03 17:44 ` Alexey Neyman
0 siblings, 0 replies; 6+ messages in thread
From: Alexey Neyman @ 2019-01-03 17:44 UTC (permalink / raw)
To: crossgcc
On 1/3/19 1:04 AM, Frans de Boer wrote:
> On 03-01-19 04:11, Alexey Neyman wrote:
>> 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.
>>>
>>>
> Hi Alexey,
>
> The gen-versions.sh was introduced by yourself. I saw a posting of
> 2017-7-13 from your hand ;)
Yes, this was temporarily a separate script that was later merged into
`bootstrap`. My point is, no documentation should be referring to that
script.
>
> As for the outdated version of the documentation, it is the version
> published on the web site and addresses 1.23 also.
I know, which is why I asked you to log this as an issue :P
>
> And the procedure for updating/adding new versions is clear. Did
> figure out step 1 already, but did not realize that manage-packages.sh
> was the tool to use to update the xxxx.in file. I only browse through
> it, probably because I had the former tool on my mind.
>
> Anyhow, I will verify your pointer later on.
>
> Question: it seems that crosstool-NG has evolved well beyond the early
> 2017 release. Don't you think it is time to release an updated version?
Yes, I planned to do that by the end of the year but my laptop broke. I
marked the remaining issues that I want to get resolved before the
release - once they're done, I'll tag an RC, run a full build-all on
supported Linux distributions and - assuming no regressions - tag a release.
> Also, it seems that you prefer git pull requests for updated/new
> pieces, this applies to the documentation too?
Yes, please, using the crosstool-ng/crosstool-ng.github.io repository.
Regards,
Alexey.
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-01-03 17:44 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 ` addToolVersion.sh Alexey Neyman
2019-01-03 9:04 ` addToolVersion.sh Frans de Boer
2019-01-03 17:44 ` addToolVersion.sh Alexey Neyman
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).