On Wed, Nov 24, 2004 at 07:18:48PM -0500, Paul Smith wrote:
But I need to be able to copy that entire image to another location, set
ROOT to that location, and cross-compile code using that image in that
new location.
export ROOT=/tmp/ppc-image
./configure --prefix=/usr CC=ppc-gcc
On Wed, Nov 24, 2004 at 07:18:48PM -0500, Paul Smith wrote:
My environment involves running in an x86 host running Linux, and
cross-compiling everything for a different target. A few extra things
about this are (a) that we do not use chroot or any similar technology,
and (b) the entire thing
* Paul Smith wrote on Thu, Nov 25, 2004 at 01:18:48AM CET:
Hi all. I'm having a severe problem with libtool-ized packages, of
which there are more and more these days, in my environment. I'm
wondering if anyone here can suggest how I should proceed; whether
there's something in libtool that
%% Ralf Wildenhues [EMAIL PROTECTED] writes:
rw Only one question for now (I don't know enough about the problem space
rw yet), concerning notation:
rw _Relocatable_ IMHO is a package which can be installed (literally
rw copied to) in /usr or /usr/local without any difference.
rw You
%% Noah Misch [EMAIL PROTECTED] writes:
nm Several individuals have communicated similar requirements here.
nm Some had partial workarounds you may find useful; check the
nm archives.
OK, I'll see what I can find.
nm Roughly. The .la does not need to encode the $ROOT, but libtool
nm
Hi all. I'm having a severe problem with libtool-ized packages, of
which there are more and more these days, in my environment. I'm
wondering if anyone here can suggest how I should proceed; whether
there's something in libtool that will help me, or whether libtool needs
enhancements, or what.
