RE: [gentoo-embedded] Problem cross compiling modular X

["Ryan Baldwin" <ryan.baldwin@nexusalpha.com>]

Hi,

Thanks for your replies people. 

>why are you at all cross-compiling, you have the same arch, use simply an 
>uClibc chroot

Ultimately I want target other arch's, probably ARM. For the time being
though I happen to be targeting the same arch.

After the previous reply - 

>that all depends on whether you setup your build environment properly
>in an ideal world:
> - only RDEPEND stuff goes into /tmp/target/
> - only DEPEND stuff goes into /usr/$CTARGET/
>so to address the issue, you could do:
>ROOT=/usr/$CTARGET/ emerge <X header packages> ROOT=/tmp/target/ emerge <X
>server/etc...> -mike

I ended up finding a lot more stuff that has helped me immensely and I am
now getting quite close to my first objective. 

Something that continues to baffle me though is that on this mailing list
people have referred to cross compiling modular X and having got it up and
running. 

I can't see how this can be done without setting up a portage overlay and
modifying the ebuilds for several of the packages under x11-libs/(at least)
to take the steps detailed in http://wiki.x.org/wiki/CrossCompilingXorg . So
far I have created modified ebuilds in my overlay dir to pass
--enable-malloc0returnsnull to ./configure where required and to set
CC_FOR_BUILD and apply the patches from that page. This has then allowed me
to cross compile those packages. 

What baffles me is that from what I read on this list perhaps I shouldn't
need to do this, is there a portage overlay available somewhere that does
this already? If so I cant find it. If anyone could give many any clused
with regard to this, or let me know the steps they take to cross compile
modular X then that would be a great help.


Thanks
Ryan 

-- 
gentoo-embedded@gentoo.org mailing list