xf86-video-geode build error running jhbuild

[Matt Dew]

On Sat, May 29, 2010 at 11:33 PM, Dirk Wallenstein <halsmit at t-online.de> wrote:
> On Sat, May 29, 2010 at 10:14:21AM -0400, Gaetan Nadon wrote:
>>    On Sat, 2010-05-29 at 15:26 +0200, Dirk Wallenstein wrote:
>>
>> On Sat, May 29, 2010 at 08:47:04AM -0400, Gaetan Nadon wrote:
>> >
>> >    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?
>>
>> I think it would be possible to introduce another <autotools> attribute
>> that specifies a filename to execute, and the retval says if it is
>> eligible. Then it might be possible that those modules don't appear in
>> the modules list at all.
>> The autotools attribute would ensure that that file to execute is a
>> tracked file and not one accidentally put there.
>>
>> I think the possibility to enable/disable a module depending on external
>> conditions is generally appealing.
>>
>> That would of course require such a file in the modules that don't build
>> everywhere.
>>
>>
>>    I had similar thoughts. A simple text file would do, listing allowed
>>    and forbidden host/cpu, as a naive implementation. Perhaps an xml file
>>    could reduce coding effort to read it. Using data encapsulation as a
>>    guiding principle, a module should know where it can or cannot be
>>    built. Currently the information is in the build scripts, so it needs
>>    to be duplicated and maintained in multiple build systems.
>
> Sounds good.
>
>> For now I plan to improve the my.modules file, so that it contains
>> corresponding comments, and include the necessary steps in a future
>> setup tutorial.
>
> Ah! Much simpler. The new internal 'init' command that creates a
> repo-group local configuration, can simply fill out the list of modules
> to skip. However, that relies on module-names, it needs to be kept up to
> date, and the user has to drag it along if an alternative configuration
> for the same repo-group is wanted.
>
> That would of course allow to mix in all the libs and drivers into the
> main meta module and let 'init' sort it out. Very good.
>
> Coming soon...
>
> --
> Greetings,
> Dirk
>


Thanks guys,
   I am building on an amd64 box so that explains the geode build.

I did run into a couple others errors:
*** Building xf86-video-impact *** [136/168]
make
make  all-recursive
make[1]: Entering directory `/home/matt/xorg/driver/xf86-video-impact'
Making all in src
make[2]: Entering directory `/home/matt/xorg/driver/xf86-video-impact/src'
/bin/sh ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
-I..    -fvisibility=hidden -I/home/matt/xorg-build/include/xorg
-I/home/matt/xorg-build/include/pixman-1   -g -O2 -MT impact_cmap.lo
-MD -MP -MF .deps/impact_cmap.Tpo -c -o impact_cmap.lo impact_cmap.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -fvisibility=hidden
-I/home/matt/xorg-build/include/xorg
-I/home/matt/xorg-build/include/pixman-1 -g -O2 -MT impact_cmap.lo -MD
-MP -MF .deps/impact_cmap.Tpo -c impact_cmap.c  -fPIC -DPIC -o
.libs/impact_cmap.o
In file included from impact_cmap.c:14:
impact.h:19:27: error: xf86Resources.h: No such file or directory
make[2]: *** [impact_cmap.lo] Error 1
make[2]: Leaving directory `/home/matt/xorg/driver/xf86-video-impact/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/matt/xorg/driver/xf86-video-impact'
make: *** [all] Error 2
*** Error during phase build of xf86-video-impact: ########## Error
running make   *** [136/168]

*** Building xf86-video-sunbw2 *** [148/168]
make
make  all-recursive
make[1]: Entering directory `/home/matt/xorg/driver/xf86-video-sunbw2'
Making all in src
make[2]: Entering directory `/home/matt/xorg/driver/xf86-video-sunbw2/src'
  CC     bw2_driver.lo
  bw2_driver.c:31:25: error: xf86Version.h: No such file or directory
  bw2_driver.c:36:20: error: xf1bpp.h: No such file or directory
  bw2_driver.c: In function ‘BW2FreeRec’:
  bw2_driver.c:164: warning: ‘Xfree’ is deprecated (declared at
/home/matt/xorg-build/include/xorg/os.h:234)
  bw2_driver.c: In function ‘BW2Probe’:
  bw2_driver.c:234: warning: ‘Xfree’ is deprecated (declared at
/home/matt/xorg-build/include/xorg/os.h:234)
  bw2_driver.c:268: warning: ‘Xfree’ is deprecated (declared at
/home/matt/xorg-build/include/xorg/os.h:234)
  bw2_driver.c:270: warning: ‘Xfree’ is deprecated (declared at
/home/matt/xorg-build/include/xorg/os.h:234)
  make[2]: *** [bw2_driver.lo] Error 1
  make[2]: Leaving directory `/home/matt/xorg/driver/xf86-video-sunbw2/src'
  make[1]: *** [all-recursive] Error 1
  make[1]: Leaving directory `/home/matt/xorg/driver/xf86-video-sunbw2'
  make: *** [all] Error 2
  *** Error during phase build of xf86-video-sunbw2: ########## Error
running make   *** [148/168]

*** Building xf86-video-xgi *** [162/168]
make
make  all-recursive
make[1]: Entering directory `/home/matt/xorg/driver/xf86-video-xgi'
Making all in src
make[2]: Entering directory `/home/matt/xorg/driver/xf86-video-xgi/src'
  CC     init.lo
In file included from init.h:56,
                 from init.c:67:
vgatypes.h:59:25: error: xf86Version.h: No such file or directory
In file included from init.h:64,
                 from init.c:67:
xgi.h:201:49: error: missing binary operator before token "("
make[2]: *** [init.lo] Error 1
make[2]: Leaving directory `/home/matt/xorg/driver/xf86-video-xgi/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/matt/xorg/driver/xf86-video-xgi'
make: *** [all] Error 2
*** Error during phase build of xf86-video-xgi: ########## Error running make
*** [162/168]

Since I'm not building/running on a sgi or sun box I'm not sure these
matter.  But I'm reporting them just in case anyway.

Dirk,
 I saw a lot of files in modulesets/ but no my.modules.   Did I
misunderstand the 'my' part?

On the plus side,  it did finish building and I was able to run it!
YAY!  The only issue I had was i had to install docbook-xml-dtd
version 4.1.2.  The documentation didn't build with a newer version.

Matt