Re: [Inkscape-devel] cannot compile r17091
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:
============================================================================= When you report a trouble about building SVN version of inkscape, Please report following information about distro and tools version, too.
--1. distribution------------------------------------------------------------ Debian GNU/Linux release lenny/sid
--2. tools------------------------------------------------------------------- /usr/bin/m4: m4 (GNU M4) 1.4.10 /usr/bin/autoconf: autoconf (GNU Autoconf) 2.61 /usr/bin/autoheader: autoheader (GNU Autoconf) 2.61 /usr/bin/automake: automake (GNU automake) 1.8.5 /usr/bin/automake-1.7: automake (GNU automake) 1.7.9 /usr/bin/automake-1.8: automake (GNU automake) 1.8.5 automake-1.9: not found /usr/bin/aclocal: aclocal (GNU automake) 1.8.5 /usr/bin/aclocal-1.7: aclocal (GNU automake) 1.7.9 /usr/bin/aclocal-1.8: aclocal (GNU automake) 1.8.5 aclocal-1.9: not found /usr/bin/intltoolize: intltoolize (GNU intltool) 0.36.2 /usr/bin/gettextize: /usr/bin/gettextize (GNU gettext-tools) 0.16.1
--3. environment variables--------------------------------------------------- LD_LIBRARY_PATH=/usr/lib WINDOWPATH=7 GDM_LANG=es_AR.UTF-8 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=es_AR.UTF-8
=============================================================================
I am testing that you have the required versions of autoconf, automake, glib-gettextize and intltoolize. This test is not foolproof and if anything goes wrong, there may be guidance in the file HACKING.txt
checking for autoconf >= 2.52 ... yes (version 2.61) checking for automake >= 1.7 ... yes (version 1.8.5) checking for glib-gettextize >= 2.0.0 ... yes (version 2.14.1) checking for intltool >= 0.17 ... yes (version 0.36.2)
Running aclocal ... Running autoheader ... Running automake --copy --force --add-missing ... configure.ac:12: option `tar-pax' not recognized Please fix the error conditions and try again.
------------------
If I try to run make clean before running autogen.sh, it complains about tar-pax too. Any advise to workaround this?
Regards, Gez.
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.
Aaron Spike
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
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
Have you run ./autogen.sh again?
-Josh
Tom Davidson wrote:
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 http://configure.ac:12: option `tar-pax' not recognized make: *** [Makefile.in http://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... mailto: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 <mailto:Inkscape-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/inkscape-devel <https://lists.sourceforge.net/lists/listinfo/inkscape-devel>
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
No, my bad. Previously I'd just been running the ./configure that was in SVN. Autogen does successfully diagnose the problem (see below).
I guess this is just a fedora core 6 corner case, as there is no automake 1.8 or >1.9.6 RPM available from the usual sources. One working hack is just to remove the new 'tar-pax' argument from configure.ac (since I don't build tarballs), and compile as before (using 1.7). Probably I'll stick with this until I upgrade my distro...
Thanks for the help, Tom
$ ./autogen.sh ============================================================================= When you report a trouble about building SVN version of inkscape,
Please report following information about distro and tools version, too.
--1. distribution------------------------------------------------------------ Fedora Core release 6 (Zod)
--2. tools------------------------------------------------------------------- /usr/bin/m4: /usr/bin/autoconf: autoconf (GNU Autoconf) 2.59 /usr/bin/autoheader: autoheader (GNU Autoconf) 2.59 /usr/bin/automake: automake (GNU automake) 1.9.6 /usr/bin/automake-1.7: automake (GNU automake) 1.7.9 automake-1.8: not found /usr/bin/automake-1.9: automake (GNU automake) 1.9.6 /usr/bin/aclocal: aclocal (GNU automake) 1.9.6 /usr/bin/aclocal-1.7: aclocal (GNU automake) 1.7.9 aclocal-1.8: not found /usr/bin/aclocal-1.9: aclocal (GNU automake) 1.9.6 /usr/bin/intltoolize: intltoolize (GNU intltool) 0.35.0 gettextize: not found
--3. environment variables--------------------------------------------------- PATH=/home/tjd/cvs/mwsoft/build/mwl-wilson-software/bin:/home/tjd/bin/emusicj-linux:/home/tjd/bin/firefox:/home/tjd/cvs/mwsoft/build/mwl-wilson-software/bin:/home/tjd/bin:/usr/bin:/usr/local/bin:/usr/sbin:/usr/ucb:/local/bin:/usr/etc:/bin:/sbin:/usr/X11R6/bin:/usr/kerberos/bin LANG=en_US.UTF-8
=============================================================================
I am testing that you have the required versions of autoconf, automake, glib-gettextize and intltoolize. This test is not foolproof and if anything goes wrong, there may be guidance in the file HACKING.txt
checking for autoconf >= 2.52 ... yes (version 2.59) checking for automake >= 1.7 ... yes (version 1.9.6)
You must have automake less than 1.9.0 or newer than 1.9.6 Get ftp://ftp.gnu.org/pub/gnu/automake/automake-1.8.5.tar.gz (or a newer version of 1.8 if it is available) checking for glib-gettextize >= 2.0.0 ... yes (version 2.12.9) checking for intltool >= 0.17 ... yes (version 0.35.0)
Please install/upgrade the missing tools and call me again.
On Jan 23, 2008 2:09 PM, Josh Andler <scislac@...400...> wrote:
Have you run ./autogen.sh again?
-Josh
Tom Davidson wrote:
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 http://configure.ac:12: option `tar-pax' not
recognized
make: *** [Makefile.in http://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... mailto: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, itappears
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 <mailto:Inkscape-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/inkscape-devel <https://lists.sourceforge.net/lists/listinfo/inkscape-devel>
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
participants (5)
-
Aaron Spike -
Bryce Harrington -
Guillermo Espertino -
Josh Andler -
Tom Davidson