From: Hauke Mehrtens <hauke@hauke-m.de>
To: Shetu Ayalew <shetu@mellanox.com>, backports@vger.kernel.org
Subject: Re: generate backport error
Date: Thu, 11 Jun 2020 16:30:01 +0200 [thread overview]
Message-ID: <fa307949-4370-dc19-2136-116d9806fdbf@hauke-m.de> (raw)
In-Reply-To: <ea4eaf08-d135-69c0-0fa1-f8ad4499edd1@mellanox.com>
[-- Attachment #1.1: Type: text/plain, Size: 2838 bytes --]
On 6/8/20 10:15 AM, Shetu Ayalew wrote:
> On 6/7/2020 5:46 PM, Hauke Mehrtens wrote:
>> On 6/1/20 11:19 AM, Shetu Ayalew wrote:
>>> Hi,
>>>
>>> I'm trying to run the the gentree.py.
>>> I use coccinelle 1.0.7 and the following tree -
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
>>>
>>> with few different tags the last one was v5.7-rc3-1 (for backports
>>> tree) and v5.7-rc3 (for the Linux tree).
>>>
>>> and I get error:
>>>
>>> Traceback (most recent call last):
>>> File "./gentree.py", line 1107, in <module>
>>> ret = _main()
>>> File "./gentree.py", line 724, in _main
>>> logwrite=logwrite)
>>> File "./gentree.py", line 914, in process
>>> kver = gen_version.kernelversion(bpid.project_dir)
>>> File
>>> "/.autodirect/swgwork/shetu/upstream/backports/lib/bpversion.py",
>>> line 40, in kernelversion
>>> _check(process)
>>> File
>>> "/.autodirect/swgwork/shetu/upstream/backports/lib/bpversion.py",
>>> line 11, in _check
>>> raise ExecutionError(process.returncode)
>>> lib.bpversion.ExecutionError
>>>
>>>
>>> To my understanding the source of the above error is the fail of the run
>>> of the following command that the script executes:
>>>
>>> "make --no-print-directory -C /swgwork/shetu/upstream/backport_vr
>>> kernelversion"
>>>
>>> The error I get is "you shouldn't run make in the backports tree, but
>>> only in the generated output ...".
>>>
>>> But the directory backport_vr is not under the backports tree. Moreover
>>> I tried running make kernelversion
>>>
>>> from backport_vr and I got the same error message. Do you familiar with
>>> this probelm, any idea how to solve it ?
>>>
>>>
>>> Thanks,
>>>
>>> Shetu.
>> Hi Shetu,
>>
>> The script tries to get the kernel version of the kernel you want to
>> create a backports release for and this somehow fails.
>>
>> Could you please run this manually like I did here:
>>
>> $ make --no-print-directory -C ~/linux/linux-next kernelversion
>> 5.7.0-rc3
>> $ echo $?
>> 0
>>
>> Please keep the mailing list in CC.
>>
>> Hauke
>>
> Hi,
>
> I did and got the same output as you. But it seems like the script is
> not using the source tree path as in you asked me to do, rather it uses
> the output tree (after backport) path.
> Looking into the Makefile is looks like the it checks if file named
> local-symbols exits (which not) and thus fails.
>
> Thanks
>
> Shetu.
>
How do you call the ./gentree.py script like this?
./gentree.py ~/linux/linux-next-clean/
/home/hauke/backports/backports-5.7-rc3-test1
If you just need the wifi drivers form a recent kernel you can also
download a pregenerted tar here:
https://backports.wiki.kernel.org/index.php/Releases
Hauke
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-06-11 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 9:19 generate backport error Shetu Ayalew
2020-06-07 14:46 ` Hauke Mehrtens
2020-06-08 8:15 ` Shetu Ayalew
2020-06-11 14:30 ` Hauke Mehrtens [this message]
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=fa307949-4370-dc19-2136-116d9806fdbf@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.org \
--cc=shetu@mellanox.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).