From: Mark Wielaard <mjw@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: systemtap@sources.redhat.com, Dave Brolley <brolley@redhat.com>
Subject: Re: /usr/bin/staprun hardcoded in latest git
Date: Mon, 05 Jan 2009 09:59:00 -0000 [thread overview]
Message-ID: <1231149523.3499.8.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <20090104194526.GA496@one.firstfloor.org>
Hi Andi,
On Sun, 2009-01-04 at 20:45 +0100, Andi Kleen wrote:
> On Sun, Jan 04, 2009 at 08:11:07PM +0100, Mark Wielaard wrote:
> > hmmm. Even even with --prefix=/usr/local I am unable to replicate :{
> > Could you rm stapio-mainloop.o && make stapio-mainloop.o ?
> > With --prefix=/usr/local it should give:
> > gcc -DHAVE_CONFIG_H -I. -DBINDIR='"/usr/local/bin"'
> > -DPKGDATADIR='"/usr/local/share/systemtap"'
> > -DPKGLIBDIR='"/usr/local/libexec/systemtap"' [...]
>
> Ah indeed that fixes it. So it looks like just the dependencies
> are broken?
Glad to have your issue worked out. And yes, if you reconfigure in an
build dir then currently you will have to do a make clean first. We
could instead of passing BINDIR and friends through AM_CPPFLAGS in
Makefile.am, add them to config.h and include that in the relevant .c
files. Then a reconfigure should trigger a rebuild of the .o files. Does
that make sense to others? Or is that too tricky for the runtime .c
files?
Cheers,
Mark
next prev parent reply other threads:[~2009-01-05 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 14:15 Andi Kleen
2009-01-04 18:30 ` Mark Wielaard
2009-01-04 18:42 ` Andi Kleen
2009-01-04 19:11 ` Mark Wielaard
2009-01-04 19:31 ` Andi Kleen
2009-01-05 9:59 ` Mark Wielaard [this message]
2009-01-05 12:42 ` Andi Kleen
2009-01-11 13:47 ` Mark Wielaard
2009-01-05 16:09 ` Dave Brolley
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=1231149523.3499.8.camel@dijkstra.wildebeest.org \
--to=mjw@redhat.com \
--cc=andi@firstfloor.org \
--cc=brolley@redhat.com \
--cc=systemtap@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).