public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: kerolasa@gmail.com
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: v2.22 wish list
Date: Wed, 11 Apr 2012 13:42:23 +0200	[thread overview]
Message-ID: <20120411114223.GU19784@x2.net.home> (raw)
In-Reply-To: <CAG27Bk0ZtUj0-7Jr4VKaQ++YzKzeqhVQsOQzYwkBPGWV1pan-A@mail.gmail.com>

On Thu, Mar 01, 2012 at 10:51:05PM +0100, Sami Kerola wrote:
> CC: mail list.
> On Thu, Mar 1, 2012 at 22:47, Sami Kerola <kerolasa@iki.fi> wrote:
> > On Wed, Feb 29, 2012 at 16:44, Karel Zak <kzak@redhat.com> wrote:
> >> This is my v2.22 wish list. The list contains large/invasive tasks only.
> >> Comments, volunteers, .... ? ;-)
> > [snip]
> >>  * non-recursive build-system (now many files from lib/ are compileted
> >>   more than once), see:
> >>   http://thread.gmane.org/gmane.linux.utilities.util-linux-ng/3297
> >
> > I gave a try to non-recursive build, and getting it to work took a bit

 In your implementation you're successfully resolved the problem with
 lib/*.c, but it's not non-recursive build.

 The non-recursive build means that there is only one Makefile.am, so
 make(1) is able to optimize compilation and SMP machines. See the old
 discussion with Flameeyel for more details.

 Your attempt could be a first step to make the build system more
 effective and maintainable. The second step (real non-recursive
 build) is more invasive.

 Notes:

  - we have SUID_{LDFLAGS,CFLAGS} so it would be better to have
    separate libcommon.la for suid utils

  - please define on $top_builddir based $($ul_libcommon_la) rather than use
    everywhere ../lib/libcommon.la

> > work meaning changes here and there. I think the preview version below
> > does what was asked, but in all honesty it is not ready be merged. The
> > change needs to be split to reasonable chunks (now single big commit).

 Yes :-)

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2012-04-11 11:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 15:44 v2.22 wish list Karel Zak
2012-02-29 16:02 ` Keshav P R
2012-02-29 16:25   ` Karel Zak
     [not found] ` <CAG27Bk1kMB9Mw46T3Lb0DBttqDOrHU0JBTkSERd7rfL8ikvH8A@mail.gmail.com>
2012-03-01 21:51   ` Sami Kerola
2012-04-11 11:42     ` Karel Zak [this message]
2012-03-02 15:10 ` Karel Zak
2012-03-03 14:45 ` Petr Uzel
2012-03-12 17:50 ` Mike Frysinger

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=20120411114223.GU19784@x2.net.home \
    --to=kzak@redhat.com \
    --cc=kerolasa@gmail.com \
    --cc=util-linux@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