lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAJTyqKNsh1UgpuZYoqR6BshxaEEh55WMs=S87U=jYbhQfzvF3g@mail.gmail.com>
Date:   Thu, 29 Apr 2021 05:20:45 +0000
From:   Mariusz Ceier <mceier+kernel@...il.com>
To:     David Laight <David.Laight@...lab.com>
Cc:     "ojeda@...nel.org" <ojeda@...nel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "rust-for-linux@...r.kernel.org" <rust-for-linux@...r.kernel.org>,
        "linux-kbuild@...r.kernel.org" <linux-kbuild@...r.kernel.org>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/13] [RFC] Rust support

On 28/04/2021, David Laight <David.Laight@...lab.com> wrote:
> From: Mariusz Ceier
>> Sent: 28 April 2021 19:34
> ....
>>
>> I suggest to wait until featureful GPL implementation of rust language
>> is made (assuming GNU Rust is on the way) before merging any rust code
>> in the kernel and when that implementation is done make a requirement
>> that all rust code must be buildable by at least GPL implementation.
>>
>> Maybe it would also be worthwhile to make the requirement that the
>> kernel must be buildable with free software (not just open source
>> software) explicit ?
>
> Or put the version of the compiler that works in the source tree
> with the kernel and then build it as part of the full build.
>
That is an overkill :)
Even hosting a copy of all required tools at kernel.org might be an
overkill (but who knows);
I think having links at
https://www.kernel.org/doc/html/latest/process/changes.html#getting-updated-software
is enough.

> It is enough of a PITA having to find libelf-devel in order to
> build objtool, never mind having to find the correct version
> of something else.
>
> gcc tends to be available and the version doesn't matter too much.
> But ever that gives problems.
>
>       David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1
> 1PT, UK
> Registration No: 1397386 (Wales)
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ