From mboxrd@z Thu Jan 1 00:00:00 1970 From: jimmy.durand.wesolowski@gmail.com (Jimmy Durand Wesolowski) Date: Mon, 26 Aug 2013 17:13:07 +0200 Subject: [lttng-dev] [LTTNG][LTTng-ust] "Out of system" building patches. In-Reply-To: <20130826162407.1996f085@skate> References: <1377160051-12449-1-git-send-email-jimmy.durand.wesolowski@gmail.com> <20130822125523.GB26852@Krystal> <20130824175909.GA12409@Krystal> <20130826162407.1996f085@skate> Message-ID: 2013/8/26 Thomas Petazzoni > Dear Jimmy Durand Wesolowski, Dear Thomas Petazzoni, > On Mon, 26 Aug 2013 09:43:49 +0200, Jimmy Durand Wesolowski wrote: > > > Here is a quick test, without any of my modifications. I had to pass both > > CFLAGS and LDFLAGS to "./configure", as said earlier, which can be > > considered > > a normal process: > > CFLAGS="-I/include" \ > > CPPFLAGS="-I/include" \ > > LDFLAGS="-L/lib" \ > > ./configure --prefix=${PWD}/build > > As said previously, if you're cross-compiling, doing > --prefix=${PWD}/build is completely wrong. --prefix is the directory > where the software will be located when executed on the target, not the > location where the software will be installed when doing 'make install'. > Thank you for this information, I shamefully did not remember this, and I am a buildroot user myself... I will not be using --prefix for cross- compilation anymore, thank you. Nevertheless, I did not say that LTTng cannot be cross-compiled without these changes, but it needs flags at the 'configure' step, and at the 'make' one, as I said earlier, which DESTDIR will not correct, since the the flags are not given to the sub-Makefiles. Thank you for the correction, -- Jimmy Durand Wesolowski OpenWide R&D engineer OneAccess -------------- next part -------------- An HTML attachment was scrubbed... URL: