On Tuesday, 18 March 2008, at 18:49:11 (+0100),
Koen Kooi wrote:
> It's not about redefining $(includedir), it's about this situation:
>
> arm-angstrom-linuxgnueabi-gcc something-doing-math.c -I/usr/include
> - -I/data/cross/arm/usr/include -o foo
>
> something-doing-math.c looks something like:
>
> ..
> #include <optimized-header.h>
> ..
>
> The build will pick up the mmx version of the header from /usr/include
> (assuming you build on an intel system) and the compiler will choke on
> strange asm and datasizes.
Only if you fail to redefine $(includedir). If $(includedir) were set
to, say, /data/cross/arm/usr/include instead, it would work fine.
> Redefining ${includedir} won't help, since you want the software to end
> up in ${prefix} on the target when installing the package.
It will help, insofar as the problem you mention above won't occur.
If we don't include stuff in $(includedir), what is the appropriate
method for people who use, for example, --prefix=/opt/e17 to make sure
that /opt/e17/include/*.h gets picked up? Up until now, that was
handled automatically by the stuff you all just nuked. :)
Michael
--
Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTECTED]>
Linux Server/Cluster Admin, LBL.gov Author, Eterm (www.eterm.org)
-----------------------------------------------------------------------
"Love, like a road that never ends. How it leads me back again to
heartache, I don't understand."
-- Peter Cetera and Amy Grant, "Next Time I Fall"
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
