[Fixed] Trying to fix etl, synfig, synfig-studio

[gseaman]

etl, etl-devel build fine, no errors.

synfig builds fine with "./configure --prefix=/usr && make && su -c 'make install'"

I haven't tried synfigstudio yet, because the rpm for synfig won't build. I changed %configure2_5 to %configure in the spec just to match my command line effort, but no change. I googled the errors, and found references to "aclocal -I 'm4'" which did not work, and other errors which seem to have already been incorporated into the source. I haven't contaced the developers, because it seems to be an rpm / spec problem since it builds just fine. I upgraded the source files to 0.62.01 to see if bugs or build problems may have been fixed.

Any ideas on what to try next? I've attached the spec file.

Galen

Update: synfigstudio builds using ./configure --prefix && make && su -c 'make install' and runs without errors.

I don't really know anything about using this program, but it is very interesting and I hope to learn. I will use Tex's spec to build the rpm and see if there are problems with this one. (etl, synfig and synfigstudio are all required to use this program.)

[gseaman]

No go. synfigstudio has the same problem as synfig. Here's a sample of where it goes wrong:

/bin/sh ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I../.. -I../../src -I../../libltdl   -pthread -I/usr/include/synfig-0.0 -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include "-DLOCALEDIR=\"/usr/share/locale\"" -pipe -Wp,-D_FORTIFY_SOURCE=2 -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -DNDEBUG -O2 -W -Wall -MT libsynfigapp_la-activepointremove.lo -MD -MP -MF .deps/libsynfigapp_la-activepointremove.Tpo -c -o libsynfigapp_la-activepointremove.lo `test -f 'actions/activepointremove.cpp' || echo './'`actions/activepointremove.cpp
../../libtool: line 850: X--tag=CXX: command not found
../../libtool: line 850: X--tag=CXX: command not found
../../libtool: line 883: libtool: ignoring unknown tag : command not found
../../libtool: line 883: libtool: ignoring unknown tag : command not found
../../libtool: line 850: X--mode=compile: command not found
../../libtool: line 850: X--mode=compile: command not found
../../libtool: line 1017: *** Warning: inferring the mode of operation is deprecated.: command not found
../../libtool: line 1018: *** Future versions of Libtool will require --mode=MODE be specified.: command not found
../../libtool: line 1017: *** Warning: inferring the mode of operation is deprecated.: command not found
../../libtool: line 1161: Xg++: command not found
../../libtool: line 1018: *** Future versions of Libtool will require --mode=MODE be specified.: command not found

Again, this problem does not exist when running "./configure --prefix=/usr && make && su -c 'make install'".

Galen

[Texstar]

Make sure you are using the proper libtool package. There are 3 different versions 1.5.26, 2.2.6 and 2.2.6b. Download form ibiblio and store them somewhere so you can force remove and install them as needed. Most of the time I have 2.2.6b installed and use autoreconf -fi  added after the %BUILD section of the spec file.

%build
autoreconf -fi

You can also sometimes use an older libtool version by adding

%define __libtoolize    /bin/true

to your spec file.

[gseaman]

Thanks, Tex. I saw the autoreconf -fi mentioned on a site, but since it built manually, I thought that may be a dead end. I will try additional versions of libtool. If I find the one that works, do I notate it as a build dependency?

Galen

[gseaman]

This seems to be working (it's building without the previous errors).

rm -f m4/{libtool,lt*}.m4
autoreconf -fi

I adapted the first line from here:
http://libtorrent.rakshasa.no/ticket/1852

Galen

[gseaman]

This worked for synfig and synfigstudio. The program builds and runs. There are some apparently minor errors when building. I don't know if that means there will be missing features or crashes. Probably not, but if we have anyone who would like to test it would be a good idea. (It wouldn't even run before, so definitely worth replacing, however.) Thanks for the help. I'll put them in dropbox right now.

Galen