linux-kernel - Re: Moving include/asm-*

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: <20080522.104356.76251548.davem@davemloft.net>
Date:	Thu, 22 May 2008 10:43:56 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	schwab@...e.de
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Moving include/asm-*

From: Andreas Schwab <schwab@...e.de>
Date: Thu, 22 May 2008 18:32:29 +0200

> David Miller <davem@...emloft.net> writes:
> 
> > That doesn't make it any more intuitive.
> 
> Flexibility comes with some cost.

GLIBC is overly flexible, to the point of being painful.

It is designed in such a way that you cannot even do a fully parallel
build.  It can only parallelize in one directory at a time.

It stats files like crazy, in every subdirectory it visits, in order
to implement this prioritization scheme.

It is the most inefficient build system that I am aware of for such an
important code base.
--
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/