Re: gd package and cross compile badness

[Jamie Lenehan <lenehan@twibble.org>]

On Fri, Sep 01, 2006 at 12:01:45PM +0200, Alain2210 wrote:
[...]
> > I suspect you have one of those distro's that include the X header in
> > /usr/include only and not in /usr/X11R6/include and so it's the
> > search for the X headers that is the issue.
> 
> I have forgotten to say that I was using familiar-unstable.

Ah, that's not actually what I meant ;). In this case I was talking
about your "host distro" not the OE distro you were building for.

The check for host systems headers complains if something tries to
use headers from /usr/include but it doesn't complain if something
tries to use headers from /usr/X11R6/include. Most host distro's have
the X headers in /usr/X11R6/include - I have Fedora Core 4 x86_64 and
that's where it puts the X headers. But some disto's (whatever host
distro your using for example) have the X headers in /usr/include/X11
only. The configure scripts appear to check for /usr/X11R6/include
before /usr/include/X11/.

So most OE developers don't actually see any of the problems that are
related to the use of the X headers, so you may run into a few of
those.

The solution for the X headers that usually works is to pass
appropriate options to config. That's either:

 --without-x

if X isn't needed, or:

 --x-libraries=${STAGING_LIBDIR} --x-includes=${STAGING_INCDIR}

if X is needed.

[...]
> I get an analogous problem in tetex. And will try to solve it with the same

Yeah, tetex is looking for the X libs and headers as well:

 [nynaeve][12:09AM]%> grep /usr/.\*/include /data/oe/build/wrap-glibc/tmp/work/tetex-native-3.0-r1/temp/log.do_configure.18267
 checking for X... libraries /usr/X11R6/lib64, headers /usr/X11R6/include

On your system it'll be finding th headers in /usr/include/X11, so
the fix should be the same.

You should probably add entries in the bugtracker for each one of
these you find and fix as well.

-- 
 Jamie Lenehan <lenehan@twibble.org>