[PD-dev] moocow/libgfsm error on Fedora

[Bryan Jurish]

morning Hans, morning list,

On 2008-11-18 02:32:57, Hans-Christoph Steiner <hans at eds.org> appears to
have written:
> Anyone know why moocow is dying on Fedora with this error:
>
> http://autobuild.puredata.info/auto-build/2008-11-16/logs/
> 2008-11-16_04.30.20_linux_fedora8-i386_pd-extended_run-automated-
> builder.txt
>
> gcc -DHAVE_CONFIG_H -I.  -I. -DPIC  -O3 -pipe -fPIC -Wall  -DPD -O2 -
> mtune=i686 -march=i386 -ftree-vectorize -ftree-vectorizer-verbose=3 -
> I/home/pd/auto-build/pd-extended/pd/src -Wall -W -ggdb -I/home/pd/
> auto-build/pd-extended/Gem/src -I/home/pd/auto-build/pd-extended/
> externals/pdp/include -DUNIX -Dunix -fPIC -c atom_alphabet.c
> In file included from atom_alphabet.c:28:
> ./atom_alphabet.h:32:18: error: gfsm.h: No such file or directory
[snip]

Looks like libgfsm isn't installed on the build machine.

See here (lines 17359-17361):
> gcc -DHAVE_CONFIG_H [...] -c atom_alphabet.c
> In file included from atom_alphabet.c:28:
> ./atom_alphabet.h:32:18: error: gfsm.h: No such file or directory

See also line 17313 (output of the preceeding call of `sh
moocow/gfsm/configure`):
> checking for GFSM... no
> configure: WARNING: 
> configure: WARNING: ----------------------------------------------------------------
> configure: WARNING:                    gfsm library not found!
> configure: WARNING: 
> configure: WARNING:        Is the directory containing gfsm.pc in your
> configure: WARNING:          'PKG_CONFIG_PATH' environment variable?
> configure: WARNING: ----------------------------------------------------------------
> configure: WARNING: 

... and the echo of the actual "failing" build command as invoked by
moocow/extended/Makefile (make[3]) at line 17348:
> make DESTDIR="" -C ../gfsm all install || true

... also note that after the "failed" build of the gfsm externals, the
dummy target "moocow/extended/gfsm.build_stamp" *does* in fact get
successfully created (lines 17411-17419):
> make[7]: *** [atom_alphabet.o] Error 1
> make[7]: Leaving directory `/home/pd/auto-build/pd-extended/externals/moocow/gfsm/src'
> make[6]: *** [all-recursive] Error 1
> make[6]: Leaving directory `/home/pd/auto-build/pd-extended/externals/moocow/gfsm/src'
> make[5]: *** [all] Error 2
> make[5]: Leaving directory `/home/pd/auto-build/pd-extended/externals/moocow/gfsm/src'
> make[4]: *** [all-recursive] Error 1
> make[4]: Leaving directory `/home/pd/auto-build/pd-extended/externals/moocow/gfsm'
> touch gfsm.build_stamp

... and the build process continues (without crashing) ...

... so aside from the (admittedly ugly, but otherwise inconsequential
for the rest of the build process) errors, what's the problem?  I could
take the gfsm externals out of the list of 'moocow' build targets for
pd-extended (since libgfsm isn't likely to be installed anywhere but on
my own machines), but it ought to build successfully whenever libgfsm is
installed, and it is freely available (LGPL, from me:
http://www.ling.uni-potsdam.de/~moocow/projects/gfsm).  I suppose I
could also pack a local version of libgfsm into pd-gfsm and build it
with the externals, or move it to sourceforge and use svn:externals,
etc. etc. ... but that all seems like overkill to me... anyone have an
opinion?

marmosets,
	Bryan

-- 
Bryan Jurish                           "There is *always* one more bug."
jurish at ling.uni-potsdam.de      -Lubarsky's Law of Cybernetic Entomology