On Sat, 2010-05-29 at 18:33 +0800, Matt Dew wrote: > On Fri, May 28, 2010 at 8:16 PM, Dirk Wallenstein <[email protected]> wrote: > > On Fri, May 28, 2010 at 07:39:48PM +0800, Matt Dew wrote: > >> > >> Hi Dirk, > >> Nice work on this. As a newbie, I appreciate it. Any chance > >> you have time to update the wiki page with the info in your email? > >> > >> I'm running jhbuild for the first time now, > >> Matt > > > > Absolutely, just not yet. There are some major features yet to come. The > > git-like repogroup-local-configuration is a comprehensive change, and > > the jhbuild patches should be available in the mainline. > > > > The repogroup-local-configuration will enable diverse mini-features, > > like repogroup and module display in the prompt and easy inter-module > > navigation, eg: > > (test|libX11|master) $> cdx xserver > > (test|xserver|master) $> > > > > I will edit the wiki when the behavior is stable. > > Thanks, for testing. > > > > -- > > Greetings, > > Dirk > > > > Hi Dirk, > I ran into this error while using jhbuild. I let it build everything. > > *** Building xf86-video-geode *** [133/168] > make > make all-recursive > make[1]: Entering directory `/home/matt/xorg/driver/xf86-video-geode' > Making all in src > make[2]: Entering directory `/home/matt/xorg/driver/xf86-video-geode/src' > CC durango.lo > durango.c: Assembler messages: > durango.c:203: Error: suffix or operands invalid for `push' > durango.c:208: Error: suffix or operands invalid for `mov' > durango.c:209: Error: suffix or operands invalid for `mov' > durango.c:210: Error: suffix or operands invalid for `mov' > durango.c:214: Error: suffix or operands invalid for `pop' > make[2]: *** [durango.lo] Error 1 > make[2]: Leaving directory `/home/matt/xorg/driver/xf86-video-geode/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/matt/xorg/driver/xf86-video-geode' > make: *** [all] Error 2 > *** Error during phase build of xf86-video-geode: ########## Error > running make *** [133/168] > >
Geode is hardware specific. It does not build on AMD64, 32 bit only. Look at util/modular/build.sh to find out about platform restrictions. I haven't look at jhbuild yet, but I don't think it handles platform filtering. Does this mean you need to maintain one module set for every permutation of host/cpu? > Matt > _______________________________________________ > [email protected]: X.Org development > Archives: http://lists.x.org/archives/xorg-devel > Info: http://lists.x.org/mailman/listinfo/xorg-devel
signature.asc
Description: This is a digitally signed message part
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
