linux-kernel - Re: PATCH [0/3]: Simplify the kernel build by removing perl.

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:  <yw1x3ag2t2gd.fsf@thrashbarg.mansr.com>
Date:	Fri, 02 Jan 2009 10:41:22 +0000
From:	Måns Rullgård <mans@...sr.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-embedded@...r.kernel.org
Subject:  Re: PATCH [0/3]: Simplify the kernel build by removing perl.

Alejandro Mery <amery@...nsde.org> writes:

> Christoph Hellwig escribió:
>> On Fri, Jan 02, 2009 at 10:26:37AM +0100, Arkadiusz Miskiewicz wrote:
>>   
>>> On Friday 02 of January 2009, Rob Landley wrote:
>>>     
>>>> Before 2.6.25 (specifically git bdc807871d58285737d50dc6163d0feb72cb0dc2 )
>>>> building a Linux kernel never required perl to be installed on the build
>>>> system.  (Various development and debugging scripts were written in perl
>>>> and python and such, but they weren't involved in actually building a
>>>> kernel.) Building a kernel before 2.6.25 could be done with a minimal
>>>> system built from gcc, binutils, bash, make, busybox, uClibc, and the Linux
>>>> kernel, and nothing else.
>>>>       
>>> And now bash is going to be required... while some distros don't need/have 
>>> bash. /bin/sh should be enough.
>>>     
>>
>> *nod*  bash is in many ways a worse requirement than perl.  strict posix
>> /bin/sh + awk + sed would be nicest, but if that's too much work perl
>> seems reasonable.
> well, bash is not worse as bash is trivial to cross-compile to run on a
> constrained sandbox and perl is a nightmare, but I agree bash should be
> avoided too.
>
> I think the $(( ... )) bash-ism can be replaced with a simple .c helper toy.

The $(( ... )) construct is standard POSIX shell syntax, see
http://www.opengroup.org/onlinepubs/000095399/utilities/xcu_chap02.html#tag_02_06_04

Bash supports $[ ... ] as an alternate syntax for the same thing.
Perhaps you were thinking of that.

-- 
Måns Rullgård
mans@...sr.com

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/