linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Clark Williams <clark.williams@gmail.com>
Cc: Robert Schwebel <r.schwebel@pengutronix.de>,
	Michael Olbrich <m.olbrich@pengutronix.de>,
	linux-rt-users@vger.kernel.org, John Kacur <jkacur@gmail.com>
Subject: Re: [PATCH] all programs that are linked with -lrttest must depend on librttest.a
Date: Mon, 23 Feb 2015 17:02:53 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.10.1502231702140.7063@riemann> (raw)
In-Reply-To: <20150219164400.67d39390@sluggy>



On Thu, 19 Feb 2015, Clark Williams wrote:

> On Thu, 19 Feb 2015 20:59:09 +0100
> Robert Schwebel <r.schwebel@pengutronix.de> wrote:
> 
> > From: Michael Olbrich <m.olbrich@pengutronix.de>
> > 
> > Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> > ---
> >  Makefile | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/Makefile b/Makefile
> > index 9e479d3c0dca..4ee553849cce 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -73,14 +73,14 @@ cyclictest: cyclictest.o librttest.a
> >  signaltest: signaltest.o librttest.a
> >  	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
> > 
> > -pi_stress: pi_stress.o
> > +pi_stress: pi_stress.o librttest.a
> >  	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
> > 
> >  hwlatdetect:  src/hwlatdetect/hwlatdetect.py
> >  	chmod +x src/hwlatdetect/hwlatdetect.py
> >  	ln -s src/hwlatdetect/hwlatdetect.py hwlatdetect
> > 
> > -rt-migrate-test: rt-migrate-test.o
> > +rt-migrate-test: rt-migrate-test.o librttest.a
> >  	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
> > 
> >  ptsematest: ptsematest.o librttest.a
> > @@ -101,7 +101,7 @@ sendme: sendme.o librttest.a
> >  pip_stress: pip_stress.o librttest.a
> >  	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
> > 
> > -hackbench: hackbench.o
> > +hackbench: hackbench.o librttest.a
> >  	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
> > 
> >  librttest.a: rt-utils.o error.o rt-get_cpu.o rt-sched.o
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> Makes sense to me. John is working on the next spin of rt-tests so I
> CC'd him to pull in this change.
> 
> Clark
> 

(resend with a sane emailer)
I think we have to NAK this one.
I saw this problem too, if you try to do an individual build, hackbench 
and rt-migrate fail unless the lib rttest has already been built.
The thing is, neither hackbench nor rt-migrate use any of the functions in 
that lib rttest, so I'd rather not put a false dependency on the lib where 
it isn't needed.

If you'd like to come up with a patch that separates it out of the default 
libs to solve the problem, I'd accept that.

Thanks!

      reply	other threads:[~2015-02-23 16:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 19:59 [PATCH] all programs that are linked with -lrttest must depend on librttest.a Robert Schwebel
2015-02-19 22:44 ` Clark Williams
2015-02-23 16:02   ` John Kacur [this message]

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=alpine.LFD.2.10.1502231702140.7063@riemann \
    --to=jkacur@redhat.com \
    --cc=clark.williams@gmail.com \
    --cc=jkacur@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=m.olbrich@pengutronix.de \
    --cc=r.schwebel@pengutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).