From: "Ryan Baldwin" <ryan.baldwin@nexusalpha.com>
To: <gentoo-embedded@lists.gentoo.org>
Subject: RE: [gentoo-embedded] Problem cross compiling modular X
Date: Thu, 6 Jul 2006 15:37:07 +0100 [thread overview]
Message-ID: <003601c6a109$a8733d20$1a06a8c0@LXP0004> (raw)
In-Reply-To: <001201c6a0f4$194451d0$1a06a8c0@LXP0004>
Hi,
>This then leads onto the next problem emerge'ing 'libX11'.
>
> 'checking whether malloc(0) returns NULL... configure: error: cannot
>run test program while cross compiling'.
>
>I'm quite new to cross compiling. I can see what the problem is - configure
>cant run any programs in the target environment to fill out config.guess -
>because its running on the host. Is there any well known way of working
>around this other then trying to manually write a config.guess for the
>packages that can't configure themselves for the target environment?
I have resolved this problem I think by referring to the Xorg cross
compilation guide. It seems I need to pass --enable-malloc0returnsnull to
configure, set CC_FOR_BUILD and apply a few patches.
This appears to indicate though that cross compiling Xorg is not really
supported under gentoo? Presumably this would be done when the 'cross' USE
flag is set otherwise? Is this the case or am I missing something obvious ?
>Since sending my last post I have found:
>
> cp -r /tmp/target/usr/include/X11
>/usr/i686-pc-linux-uclibc/sys-include/
>
>'fools' it into building. Does anyone know a 'proper' way of getting this
>working ?
This though despite much searching I can't seem to find out what I
should(the proper way) do to make these header files available to the cross
compiler ?
Thanks
Ryan
--
gentoo-embedded@gentoo.org mailing list
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-06 14:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 11:05 [gentoo-embedded] Problem cross compiling modular X Ryan Baldwin
2006-07-06 12:02 ` Ryan Baldwin
2006-07-06 14:37 ` Ryan Baldwin [this message]
2006-07-06 19:21 ` Mike Frysinger
2006-08-24 19:19 ` Enrico Weigelt
2006-08-24 20:31 ` Leonardo Shiguemi Dinnouti
2006-08-28 6:51 ` Peter S. Mazinger
2006-08-24 19:17 ` Enrico Weigelt
2006-08-25 3:39 ` Mike Frysinger
2006-07-10 10:41 ` Peter S. Mazinger
2006-07-10 11:01 ` Ryan Baldwin
2006-07-10 17:44 ` [gentoo-embedded] nslu2 non turbo slug emerge gcc freezes / locks up nick thompson
2006-07-11 12:37 ` Ned Ludd
2006-07-14 3:40 ` nick thompson
2006-07-15 2:39 ` Mike Frysinger
2006-07-14 20:21 ` [gentoo-embedded] Problem cross compiling modular X Chuck Robey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003601c6a109$a8733d20$1a06a8c0@LXP0004' \
--to=ryan.baldwin@nexusalpha.com \
--cc=gentoo-embedded@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox