public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	Christoph Hellwig <hch@infradead.org>,
	Karel Zak <kzak@redhat.com>,
	List util-linux-ng <util-linux-ng@vger.kernel.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux-ng 2.13-rc1
Date: Fri, 6 Jul 2007 12:35:14 -0700	[thread overview]
Message-ID: <20070706193514.GO17650@tasint.org> (raw)
In-Reply-To: <468E04D3.6080002@redhat.com>

On Fri, Jul 06, 2007 at 11:01:07AM +0200, Gerd Hoffmann wrote:
> And the 10% where it doesn't work it is a real pain to figure what goes
> wrong due to the completely unreadable Makefiles generated by autotools.
>  After all they are not Makefiles, they are shellscripts embedded into
> Makefiles.

	Do not mistake the use of autoconf with automake.  automake
generates the unreadable Makefiles.  You can quite easily create a
useful Makefile yourself and use autoconf to select installation
locations, detect features of older/newer libcs, etc.  See
http://oss.oracle.com/projects/makebo/ for an example of a build system
that doesn't use automake, but allows for autoconf to do build-time
configuration (an example user of makebo is ocfs2-tools, see
 http://oss.oracle.com/projects/ocfs2-tools/src/trunk/).
	And if you think that all packages should Just Work on all
Linuxen, with out any build-time detection, try determining the
differing udev layouts of FC6, FC7, Debian, Ubuntu, SuSE9, SuSE10, etc.
Or where manpages go.  The %configure of RPM specfiles and the
dh_installman of debian packages handle this for you...often because
they can use expected behavior of your build system.  What about
futexes?  Older systems don't have them.  Gotta detect that.

Joel

-- 

"I'm drifting and drifting
 Just like a ship out on the sea.
 Cause I ain't got nobody, baby,
 In this world to care for me."

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

  parent reply	other threads:[~2007-07-06 19:35 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 22:11 [ANNOUNCE] util-linux-ng 2.13-rc1 Karel Zak
2007-07-04  8:42 ` Christoph Hellwig
2007-07-04 10:34   ` David Miller
2007-07-05 16:41   ` Mike Frysinger
2007-07-05 18:04     ` Andreas Dilger
2007-07-05 21:30     ` Karel Zak
2007-07-06  0:38       ` Matthew Wilcox
2007-07-05 23:03   ` Jeff Garzik
2007-07-06  9:01     ` Gerd Hoffmann
2007-07-06  9:16       ` Jeff Garzik
2007-07-06 19:35       ` Joel Becker [this message]
2007-07-09  7:20         ` Gerd Hoffmann
2007-07-09 20:18           ` Mike Frysinger
2007-07-04 11:11 ` Jan Engelhardt
2007-07-05 17:22   ` H. Peter Anvin
2007-07-04 17:47 ` DervishD
2007-07-05  7:01   ` Nix
     [not found] <8CYT9-4Ou-23@gated-at.bofh.it>
     [not found] ` <8Dh9k-8lT-3@gated-at.bofh.it>
     [not found]   ` <8DtDz-3xC-15@gated-at.bofh.it>
2007-07-05 14:50     ` Bodo Eggert
2007-07-05 19:20       ` DervishD
2007-07-05 20:42         ` Nix
2007-07-05 20:55           ` Bernhard Walle
2007-07-06  6:42             ` Nix
2007-07-06  7:19               ` Mike Frysinger
2007-07-06 22:43                 ` Nix
2007-07-06  6:41           ` DervishD
2007-07-06  7:17             ` Mike Frysinger
2007-07-06 10:43               ` DervishD
2007-07-06 12:17         ` Bodo Eggert
2007-07-06 12:51           ` DervishD
2007-07-05 20:36       ` Nix
2007-07-05 21:30       ` Mike Frysinger
2007-07-05 21:34         ` Nix
2007-07-05 21:47           ` Mike Frysinger
2007-07-06  0:30         ` Bryan Henderson
2007-07-06  1:16           ` Mike Frysinger
2007-07-06 16:50             ` Bryan Henderson

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=20070706193514.GO17650@tasint.org \
    --to=joel.becker@oracle.com \
    --cc=hch@infradead.org \
    --cc=jeff@garzik.org \
    --cc=kraxel@redhat.com \
    --cc=kzak@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=util-linux-ng@vger.kernel.org \
    /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