public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Mike Frysinger <vapier@gentoo.org>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] remove linux_syscall_numbers.h from tree
Date: Tue, 23 Apr 2013 20:08:43 +0200	[thread overview]
Message-ID: <20130423180843.GA330@rei.Home> (raw)
In-Reply-To: <201304231342.02090.vapier@gentoo.org>

Hi!
> > > is keeping it in the tree a big deal ?  i think it's pretty common for
> > > people to go into specific subdirs and run `make` and today, our
> > > subdirs don't declare a dependency on this file so it'll get
> > > automatically regenerated (nor do i think they should even bother).
> > 
> > You need to regenerate the file after each change to the *.in files,
> > and that means that people will forget from time to time.
> 
> so people aren't testing their commits ;)

Well, I do not like to increase number of things to check for a commit.
Fixing the testcases is complicated enough...

> > It would be better to add another rule to testcases.mk similiar to the
> > one for LIBLTP.
> 
> those rules only generate libltp.a if the file doesn't already exist.  so 
> tweaking that would be like the status quo, but worse in that `git pull` is 
> now guaranteed to not update the file :).

Hmm, I would expect that the library will be rebuild after some of it's
sources has changed. And we aren't doing that, I would call such
behavior a bug.

But thinking of consequencies, changing it carelessly would most likely
break parallel make.

> i don't want to add things like `make -C testcases/kernel/include/` as then 
> you'll have multiple subdirs processing the same thing.  maybe if we had a .mk 
> file in testcases/kernel/include/ that testcases.mk could include, and if the 
> top level testcases/kernel/ make sure we process that first before any subdirs.

I see.

Or we get this behavior if we set a flag in toplevel Makefile and the
header would be regenerated (in the leaf Makefile) only if the toplevel
flag is not set. And we could do the same for the library as well.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2013-04-23 18:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 13:53 [LTP] [PATCH] remove linux_syscall_numbers.h from tree Jan Stancek
2013-04-23 14:08 ` chrubis
2013-04-23 16:11 ` Mike Frysinger
2013-04-23 16:46   ` chrubis
     [not found]     ` <201304231342.02090.vapier@gentoo.org>
2013-04-23 18:08       ` chrubis [this message]
2013-04-25 14:34       ` chrubis
     [not found]         ` <201304251532.46436.vapier@gentoo.org>
2013-04-27  6:29           ` 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=20130423180843.GA330@rei.Home \
    --to=chrubis@suse.cz \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vapier@gentoo.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