From: jimmy.durand.wesolowski@gmail.com (Jimmy Durand)
Subject: [lttng-dev] [LTTNG][LTTng-ust] "Out of system" building patches.
Date: Sat, 24 Aug 2013 21:42:15 +0200 [thread overview]
Message-ID: <CAMaFG-2cJ+uGdwC5hHMBHUs+HBciaPXtYQ6YAkwan5bL9O=9Og@mail.gmail.com> (raw)
In-Reply-To: <20130824175909.GA12409@Krystal>
2013/8/24 Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
> * Jimmy Durand (jimmy.durand.wesolowski at gmail.com) wrote:
> > 2013/8/22 Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
> >
> > > * Jimmy Durand Wesolowski (jimmy.durand.wesolowski at gmail.com) wrote:
> > > > Hi,
> > > >
> > > >
> > > > Here are some patches to allow installing LTTng-ust out of the system
> > > > directories, ie building with "./configure --prefix", without having
> to
> > > set
> > > > C/CPP/LDFLAGS at both the configure and the make building steps.
> > >
> > > Usually, setting CPPFLAGS/CFLAGS/LDFLAGS at configure time is enough,
> > > e.g.:
> > >
> > > LDFLAGS=/usr/local/lib ./configure
> > >
> > > What feature is this patchset adding that is not covered by the usual
> > > approach ? Or what is it fixing ?
> > >
> > Actually, this is enough for a regular system build, but if you wish to
> > build
> > it in another directory with --prefix=<PATH>, which is the case for
> cross-
> > compiling, this not enough.
>
> It might be a failure of my imagination but.. why is
> CPPFLAGS/CFLAGS/LDFLAGS not enough to get UST to fetch the dependencies
> it needs (e.g. userspace RCU) when they have been installed in
> non-standard paths (because e.g. userspace RCU has been configured with
> a --prefix path for sake of cross-compiling).
>
When building the doc/examples source directories, it seems that the
Makefiles are
not using the compiler and the flags set during the './configure' stage.
Can you give a more detailed use-case that CPPFLAGS/CFLAGS/LDFLAGS fail
> to cover ?
>
Yes, I will send it a complete use case Monday morning (UTC+1).
Thanks,
Thank you for the support,
--
Jimmy Durand Wesolowski
Linux System Engineer & amateur photographer
OpenWide
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20130824/c1b66eac/attachment.html>
next parent reply other threads:[~2013-08-24 19:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1377160051-12449-1-git-send-email-jimmy.durand.wesolowski@gmail.com>
[not found] ` <20130822125523.GB26852@Krystal>
[not found] ` <CAMaFG-3HCsKngNE1cNv9PfCFuhnHwsON=T-q084ZjD+1Aj2Zqg@mail.gmail.com>
[not found] ` <20130824175909.GA12409@Krystal>
2013-08-24 19:42 ` Jimmy Durand [this message]
2013-08-26 7:43 ` Jimmy Durand Wesolowski
2013-08-26 14:24 ` Thomas Petazzoni
2013-08-26 15:11 ` Mathieu Desnoyers
2013-08-26 15:14 ` Jimmy Durand Wesolowski
2013-08-26 15:19 ` Mathieu Desnoyers
2013-08-26 15:27 ` Mathieu Desnoyers
2013-08-26 15:53 ` Jimmy Durand Wesolowski
2013-08-26 16:00 ` Mathieu Desnoyers
2013-08-27 15:02 ` Jimmy Durand Wesolowski
2013-08-26 15:13 ` Jimmy Durand Wesolowski
2013-08-26 14:22 ` Thomas Petazzoni
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='CAMaFG-2cJ+uGdwC5hHMBHUs+HBciaPXtYQ6YAkwan5bL9O=9Og@mail.gmail.com' \
--to=jimmy.durand.wesolowski@gmail.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