linux-ext4 - Re: [PATCH] configure.in: add --disable-libuuid option (Was: libuuid (Re: blkid: util-linux-ng vs. e2fsprogs))

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: <20090702142515.GA29429@mit.edu>
Date:	Thu, 2 Jul 2009 10:25:15 -0400
From:	Theodore Tso <tytso@....edu>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Mike Frysinger <vapier@...too.org>,
	Scott James Remnant <scott@...ntu.com>,
	Karel Zak <kzak@...hat.com>,
	Andrey Borzenkov <arvidjaar@...l.ru>,
	util-linux-ng@...r.kernel.org, linux-ext4@...r.kernel.org
Subject: Re: [PATCH] configure.in: add --disable-libuuid option (Was:
	libuuid (Re: blkid: util-linux-ng vs. e2fsprogs))

On Thu, Jul 02, 2009 at 02:49:24PM +0200, Kay Sievers wrote:
> > Kay's rules look like they should be fairly straightforward to drop into
> > e2fsprogs.  personally i'd use:
> > E = @:
> > when V=1, but this is probably just splitting hairs
> 
> Ah nice, looks good to me, if that works.

Take a look at what I've checked into e2fsprogs' maint branch; it was
largely based on what you suggested.

If someone can point me at an autoconf test that determines whether or
not we're using gmake, I could even set up something which sucks in a
Makefile fragment that enhances what we can do for developers who are
using GNU make.  (i.e., if you're using GNU make, "make V=1" will
DTRT, but if you're using a Solaris or BSD make, you'll have to settle
for "configure --enable-verbose-makecmds")

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html