ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] how to compile an ltib-format app dir without using ltib?


From: Stuart Hughes
Subject: Re: [Ltib] how to compile an ltib-format app dir without using ltib?
Date: Fri, 05 Sep 2008 13:58:12 +0100

Hi Robert,

Try:

$ ./ltib -m shell

This will put you into the same build environment that LTIB has when
it's running the %prep/%build/%install sections of the rpm spec files.
Spoofing will be setup for you.  To exit, type 'exit'.  Take a look at
f_shell in the ltib script to get an idea of what else gets setup for
you.

Regards, Stuart


On Thu, 2008-08-28 at 16:11 -0400, Robert P. J. Day wrote:
>    for reasons i don't have time to get into, i'd like to be able
> to just compile a source directory that's been set up to be built
> by ltib, but do it without actually invoking ltib.  to this end,
> i'm trying to invoke the "spoofed" wrappers directly, and setting
> up all of the shell environment beforehand so that i am effectively
> invoking that spoof wrapper with everything it would normally expect
> to see if it had been called via ltib.
> 
>    to that end, i've set up a little script file that i can source
> to establish what i think are the appropriate environment variables
> thusly:
> 
> ==========
> 
> export  
> TOOLCHAIN_PATH=/opt/freescale/usr/local/gcc-4.1-glibc-2.3/m68k-glibc/freescale-coldfire-4.1
> 
> PATH=${TOOLCHAIN_PATH}/m68k-linux-gnu/bin:${PATH}
> PATH=${TOOLCHAIN_PATH}/libexec/gcc/m68k-linux-gnu/4.1.1:${PATH}
> 
> export TOOLCHAIN_FLAGS="-mcf4ve"
> export TOOLCHAIN_PREFIX=m68k-linux-gnu-
> 
> export DEV_IMAGE=<rootfs directory>
> 
> ==========
> 
>    note that what i'm trying to do above is to set the env info
> just the way spoof_wrapper expects to see it from ltib.  there's the
> TOOLCHAIN_PATH, followed by a couple prepends to PATH to find gcc
> and cc1, respectively.  i've explicitly added the flags and prefix
> that spoof_wrapper, and one more for DEV_IMAGE.
> 
>    at that point, i go to the source directory and, rather than
> using ltib, i just type "make all", at which point i get:
> 
> xxx.c:41:19: error: ctype.h: No such file or directory
> In file included from xxx.c:42:
> xxx.h:15:20: error: stdlib.h: No such file or directory
> xxx.h:16:18: error: time.h: No such file or directory
> xxx.h:17:20: error: limits.h: No such file or directory
> xxx.h:84:20: error: stdarg.h: No such file or directory
> ... etc etc ...
> make[1]: *** [obj/wildmat.d] Error 1
> make: *** [all] Error 2
> 
>    what i'm *assuming* is that the m68k cross-compiler is being
> invoked properly, as is cc1.  but the header file include
> path is not set properly.  i'm assuming that the standard headers
> that should be pulled in are from the cross-compiler toolchain,
> and would be found in the appropriate directory under
> /opt/freescale/...  and so on.  but obviously that's not happening.
> 
>    i've verified that the cross-compiler gcc is being called, now
> i just need to figure out how to get it to look at its *own*
> header files.  thoughts?
> 
> rday
> 
> 
> 
> 
> _______________________________________________
> LTIB home page: http://bitshrine.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib





reply via email to

[Prev in Thread] Current Thread [Next in Thread]