From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 110888 invoked by alias); 3 Jan 2019 17:44:01 -0000 Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org Received: (qmail 110869 invoked by uid 89); 3 Jan 2019 17:44:00 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=UD:io, H*f:sk:2a4a462, H*i:sk:2a4a462, dear X-HELO: sonic303-24.consmr.mail.ne1.yahoo.com Received: from sonic303-24.consmr.mail.ne1.yahoo.com (HELO sonic303-24.consmr.mail.ne1.yahoo.com) (66.163.188.150) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 03 Jan 2019 17:43:58 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1546537436; bh=8rY4BJQ8Suua+FIL2GiXSjCJXuQh8FP8vMvMz16itws=; h=Subject:To:References:From:Date:In-Reply-To:From:Subject; b=1EjIHyulgRsFPcpa8+oZsiNjwYs40zm/v8JuKfXFb0MwdpQ2eDb+nc2sMkkTc5hhhXBUUZbjoOXl0Zd+PRh/k4pZ68eIz4E7AyHsjmRTmRcaEJHe0D6wRkd0Xg/c9I9rp3Ra5TyAB418z0r5lYVfy4+Nrbhlk3DrCW1fzY6Sws8= Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.ne1.yahoo.com with HTTP; Thu, 3 Jan 2019 17:43:56 +0000 Received: from 216.100.252.242 (EHLO [172.17.3.32]) ([216.100.252.242]) by smtp414.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 86b52947e4b5c166b91443f09b1a9d96 for ; Thu, 03 Jan 2019 17:43:51 +0000 (UTC) Subject: Re: addToolVersion.sh To: crossgcc@sourceware.org References: <2a4a4629-64ec-c855-522c-8c8f5fdc0ab9@fransdb.nl> From: Alexey Neyman Message-ID: Date: Thu, 03 Jan 2019 17:44:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <2a4a4629-64ec-c855-522c-8c8f5fdc0ab9@fransdb.nl> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-01/txt/msg00008.txt.bz2 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. >