Re: [Ltib] Adding libraries to host tool chain

[Stuart Hughes]

Hi Mike,

During a build the compiler is spoofed, this means that calls to gcc 
refer to the cross compiler for the target.  This is not just an alias, 
it implicitly wires up root/usr/{include,lib} and sets up pkg-config to 
use the rootfs area.

For packages that need to build executables to run on the build machine, 
they normally refer to this in a different way (HOSTCC is a popular 
Makefile variable).  In LTIB, the build machines compiler is referenced 
using the environment variable BUILDCC, so often you'll see in spec 
files: make HOSTCC="$BUILDCC"

You can override this behaviour within the spec file using:
export PATH=$UNSPOOF_PATH you can restore it (later) using:
export PATH=$SPOOF_PATH

gdb.spec is a good example that shows this kind of thing.

NOTE: the %configure, %build, %install sections are independent of each 
other in spec files and so changes in one don't persist to another.

If you have spec file, you may submit them to the list.  Before you do 
though it would be best if you have them working locally.  Also please 
send with your email:

  * Which baseline LTIB you are using (ideally the latest Savannah CVS)
  * An explanation of what you are trying to do.

Regards, Stuart


Mike Goins wrote:
> I have been trying to fix boost to get to build.  I did create a
> boost-header.spec which just copies the headers from boost into the
> rootfs.  That in itself will give you 99% of the boost functionality.
>  I have had almost success in a full library build using the local
> copy bjam.  This was to get around  a bjam compile problem in the -m
> scbuild process in which the booststrap, jam0, ends up cross-compiled,
> but it should be natively built by the local gcc even thought the
> build  log showed the call as "gcc .......".   Is there something
> about the -m scbuild process that hides the native compiler?    Could
> there be environment variables in this process that affect native
> compiling (CFLAGS)?   If so, how do get access to my native gcc?
>
> Sorry, I seem to be full of questions.   I do have about a dozen new
> spec files and some patches that should work.  Can I just start
> submitting them to the list?
>
> Thanks again!
>
>
> On Fri, Jul 3, 2009 at 9:07 AM, Stuart Hughes<address@hidden> wrote:
> > Hi Mike,
> >
> > Take a look at the thread here:
> > http://lists.gnu.org/archive/html/ltib/2009-01/threads.html
> >
> > Boost is not selectable currently in LTIB as it's never been fully ported or
> > tested.
> >
> > I suspect that you would be better starting with a newer baseline.  It's
> > quite possible you don't need the patch anymore (it looks like it was part
> > of a Debian package).
> >
> > Maybe the easiest way to try something out it to see if you can import it
> > from here (is that version new enough?):
> > http://download.fedora.redhat.com/pub/fedora/linux/releases/9/Fedora/source/SRPMS/boost-1.34.1-13.fc9.src.rpm
> > using ./ltib -m addsrpms <path to srpm>
> > It probably will need some tinkering though.
> >
> > Also, it's possible that someone else on the list may have this package
> > building?
> >
> > Regards, Stuart
> >
> >
> > Mike Goins wrote:
> > > Sorry, they are not packages I am maintaining.   Boost is at 1.31.0-1,
> > > but I need 1.39.   I realized that I could replace the source tarball,
> > > modify the spec, and cross my fingers in hoping the patch cleanly
> > > applies.
> > >
> > > Thanks!
> > >
> > >
> > > On Fri, Jul 3, 2009 at 3:49 AM, Stuart Hughes<address@hidden> wrote:
> > > > Hi Mike,
> > > >
> > > > I'm not exactly sure what your question is?
> > > >
> > > > There's a section in the FAQ about updating packages:
> > > > http://ltib.org/documentation-LtibFaq#ref_87
> > > >
> > > > Regards, Stuart
> > > >
> > > > Mike Goins wrote:
> > > > > That's makes it much easier.   What about updating an existing package?
> > > > >
> > > > > Thanks!
> > > > >
> > > > > On Wed, Jul 1, 2009 at 3:43 AM, Stuart Hughes<address@hidden> wrote:
> > > > > > Hi Mike,
> > > > > >
> > > > > > The libraries (headers) don't belong with the cross toolchain (in
> > > > > > LTIB),
> > > > > > they get installed into rootfs/usr/{include,lib}.  Spoofing is setup so
> > > > > > that
> > > > > > without adding and -I -L and libraries will be found from that
> > > > > > interface
> > > > > > area.  Furthermore, pkg-config provided by LTIB will use this area too.
> > > > > >
> > > > > > Regards, Stuart
> > > > > >
> > > > > > Mike Goins wrote:
> > > > > > > I've been able to build and add new binaries/libraries from source to
> > > > > > > my rootfs using ltib, but I also need to add some of these libs to my
> > > > > > > host crosstool chain (to support building more binaries/libraries).
> > > > > > > Is there a procedure for this?   hostcf?
> > > > > > >
> > > > > > > Thanks
> > >
> > > _______________________________________________
> > > LTIB home page: http://ltib.org
> > >
> > > Ltib mailing list
> > > address@hidden
> > > http://lists.nongnu.org/mailman/listinfo/ltib
>
>
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib