On my system (pretty much a stock install of Fedora Core 6), the configure script chooses automake 1.7 over the most recent version (1.9.6) and so doesn't recognize the tar-pax option. When I uninstall 1.7, I can make clean (with a warning about not having 1.7), but then the compile fails. Part of the problem seems to be that am__api_version=" 1.7" is specified in ./configure, but automake-1.7 doesn't support tar-pax.
___________________________________
Here's the failing sequence of commands before uninstalling 1.7:
$ svn up At revision 17171
$ rpm -qa |grep automake automake-1.9.6-2.1 automake16-1.6.3-8 automake15-1.5-16 automake14-1.4p6-13 automake17-1.7.9-7
$ ./configure checking build system type... i686-redhat-linux-gnu ...
$ make clean cd . && \ /bin/sh /home/tjd/svn/inkscape/missing --run automake-1.7--foreign Makefile configure.ac:12: option `tar-pax' not recognized make: *** [Makefile.in] Error 1
___________________________________
If I remove automake-1.7, then I can make clean, but I get a warning a bunch of times. The compile then fails...
$ sudo yum remove automake17 ...
$ sudo make clean ... /home/tjd/svn/inkscape/missing: line 46: automake-1.7: command not found WARNING: `automake-1.7' is missing on your system. You should only need it if you modified `Makefile.am', `acinclude.m4' or `configure.ac'. You might want to install the `Automake' and `Perl' packages. Grab them from any GNU archive site. ...(success)
$ sudo make install ... extension/internal/libinternal.a(cairo-renderer.o): In function `sp_asbitmap_render': /home/tjd/svn/inkscape/src/extension/internal/cairo-renderer.cpp:437: undefined reference to `sp_generate_internal_bitmap(SPDocument*, char const*, double, double, double, double, unsigned int, unsigned int, double, double, unsigned long, _GSList*)' collect2: ld returned 1 exit status make[1]: *** [inkscape] Error 1 make[1]: Leaving directory `/home/tjd/svn/inkscape/src' make: *** [install-recursive] Error 1
___________________________________
Any help appreciated...
-Tom
On Jan 18, 2008 9:09 AM, Bryce Harrington <bryce@...961...> wrote:
On Fri, Jan 18, 2008 at 10:03:12AM -0600, Aaron Spike wrote:
Guillermo Espertino wrote:
I'm trying to compile r17131 and have problems with tar-pax I'm using Ubuntu Gutsy and it compiled correctly before 17091. Since that I couldn't compile anymore. First I had automake 1.9, but I didn't even start (it asked for other version of automake). I removed 1.9 and installed 1.8.5 and it apparently started, but it returned this when running autogen.sh:
<snip /> > If I try to run make clean before running autogen.sh, it complains
about
tar-pax too. Any advise to workaround this?
Would it be possible to only inform/require tar-pax for making of the tarball? So very few people make a tarball. It is a pain for others to have to make updates to their system just to run autogen.sh when they don't need the tar-pax capability. If we could move the check to `make dist` there would probably be less grief and fewer questions.
Agreed. While this tar-pax change seemed like a good idea, it appears to be forcing non-obvious build problems on folks.
Bryce
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel