Hi,
I would like to contribute to the inkscape development, but I have problems compiling the cvs checkout. I got the checkout with the command
cvs -z3 -d:pserver:anonymous@...54...:/cvsroot/inkscape co inkscape
running the autogen.sh script gives the following output
checking for autoconf >= 2.52 ... yes (version 2.59) checking for automake >= 1.7 ... yes (version 1.7.9) checking for glib-gettextize >= 2.0.0 ... yes (version 2.2.3) checking for intltool >= 0.17 ... yes (version 0.31.1)
Running aclocal-1.7 ... Running autoheader ... Running automake-1.7 --add-missing ... configure.in:25: required file `./ltmain.sh' not found Please fix the error conditions and try again.
The file ltmain.sh is nowhere to be found among the downloaded files. What am I doing wrong?
Martin.
Running aclocal-1.7 ... Running autoheader ... Running automake-1.7 --add-missing ... configure.in:25: required file `./ltmain.sh' not found Please fix the error conditions and try again.
The file ltmain.sh is nowhere to be found among the downloaded files. What am I doing wrong?
As a workaround, copy or symlink ltmain.sh from usr/share/libtool to your inkscape dir.
Developers: This is approximately the 10th report of this problem. Will someone please finally fix it?
Martin Wiebusch wrote:
Hi,
I would like to contribute to the inkscape development, but I have problems compiling the cvs checkout. I got the checkout with the command
cvs -z3 -d:pserver:anonymous@...54...:/cvsroot/inkscape co inkscape
running the autogen.sh script gives the following output
checking for autoconf >= 2.52 ... yes (version 2.59) checking for automake >= 1.7 ... yes (version 1.7.9) checking for glib-gettextize >= 2.0.0 ... yes (version 2.2.3) checking for intltool >= 0.17 ... yes (version 0.31.1)
Running aclocal-1.7 ... Running autoheader ... Running automake-1.7 --add-missing ... configure.in:25: required file `./ltmain.sh' not found Please fix the error conditions and try again.
The file ltmain.sh is nowhere to be found among the downloaded files. What am I doing wrong?
Martin.
It should not be necessary, but try running "libtoolize" first, then autogen.sh again. This should install ltmain.sh for you.
Bob
On Wed, 11 Aug 2004, Martin Wiebusch wrote:
I would like to contribute to the inkscape development, but I have problems compiling the cvs checkout. I got the checkout with the command
cvs -z3 -d:pserver:anonymous@...54...:/cvsroot/inkscape co inkscape
running the autogen.sh script gives the following output
checking for autoconf >= 2.52 ... yes (version 2.59) checking for automake >= 1.7 ... yes (version 1.7.9) checking for glib-gettextize >= 2.0.0 ... yes (version 2.2.3) checking for intltool >= 0.17 ... yes (version 0.31.1)
Running aclocal-1.7 ... Running autoheader ... Running automake-1.7 --add-missing ... configure.in:25: required file `./ltmain.sh' not found Please fix the error conditions and try again.
The file ltmain.sh is nowhere to be found among the downloaded files. What am I doing wrong?
You're doing nothing wrong; this is an automake quirk. I've documented the work around to this and a couple other issues you may run into after this on the CompilingInkscape page in Inkscape's Wiki, so go check that out. (Basically, copy that file from its cannonical location - see the wiki page for details).
Good luck, and welcome aboard! :-)
Bryce
Bryce Harrington wrote:
configure.in:25: required file `./ltmain.sh' not found
You're doing nothing wrong; this is an automake quirk. I've documented the work around to this and a couple other issues you may run into after this on the CompilingInkscape page in Inkscape's Wiki, so go check that out. (Basically, copy that file from its cannonical location - see the wiki page for details).
Good luck, and welcome aboard! :-)
Bryce
On http://www.inkscape.org/cgi-bin/wiki.pl?CompilingInkscape , section "Developer Compilation", I added "libtoolize --copy --force" (that's Revision 58 of CompilingInkscape) to the example after finding out somewhere that this solves the problem. (At least it did for me.) This line might need to be added to other sections (the missing ltmain.sh seems to be described there though) and INSTALL as well...
Unfortunately (?) by looking for this solution I also found out that I'm not the only one not being able to fully understand the autotools - it's sadly rather the other way round as it seems - i.e., almost nobody seems to understand it.
In summary (describing what I remember from some articles I read), automake seems to be the most troublesome of the autotools toolchain, but you can't really replace it or the toolchain because there's already so terribly much work and knowledge invested into it so that newer autotools replacements are automatically disqualified because of their recency.
What do you folks think? Was there already a discussion on shifting the Inkscape build environment to something else on Jabber / this list / somewhere else? What was the result?
cu, - Felix
On Wed, 11 Aug 2004, Felix Rabe wrote:
On http://www.inkscape.org/cgi-bin/wiki.pl?CompilingInkscape , section "Developer Compilation", I added "libtoolize --copy --force" (that's Revision 58 of CompilingInkscape) to the example after finding out somewhere that this solves the problem. (At least it did for me.) This line might need to be added to other sections (the missing ltmain.sh seems to be described there though) and INSTALL as well...
Cool thanks. Can you post a patch to the patch tracker for adding the correct info to the INSTALL file?
Unfortunately (?) by looking for this solution I also found out that I'm not the only one not being able to fully understand the autotools - it's sadly rather the other way round as it seems - i.e., almost nobody seems to understand it.
Yeah, there's a known cargo-culting issue with automake. :-/
In summary (describing what I remember from some articles I read), automake seems to be the most troublesome of the autotools toolchain, but you can't really replace it or the toolchain because there's already so terribly much work and knowledge invested into it so that newer autotools replacements are automatically disqualified because of their recency.
Right.
What do you folks think? Was there already a discussion on shifting the Inkscape build environment to something else on Jabber / this list / somewhere else? What was the result?
We've not discussed moving away from automake afaik. I doubt we'd ever seriously consider that due to issues such as the ones you've outlined about newer solutions being too new. Probably the best solution is for some of us to just to bite the bullet and learn it. I know at least a couple people have been doing this. This is definitely one of the weaker skill areas in Inkscape, so anyone interested in developing those skills would be very encouraged to do so.
Bryce
Bryce Harrington wrote:
On Wed, 11 Aug 2004, Felix Rabe wrote:
On http://www.inkscape.org/cgi-bin/wiki.pl?CompilingInkscape , section "Developer Compilation", I added "libtoolize --copy --force" (that's Revision 58 of CompilingInkscape) to the example after finding out somewhere that this solves the problem. (At least it did for me.) This line might need to be added to other sections (the missing ltmain.sh seems to be described there though) and INSTALL as well...
Cool thanks. Can you post a patch to the patch tracker for adding the correct info to the INSTALL file?
If somebody can do this sooner than me (my personal priority for working on private computer projects is very low at the moment), that would be great. Otherwise, I'll look at it when I can, which might be at the weekend.
- Felix
Bryce Harrington wrote:
On Wed, 11 Aug 2004, Felix Rabe wrote:
On http://www.inkscape.org/cgi-bin/wiki.pl?CompilingInkscape , section "Developer Compilation", I added "libtoolize --copy --force" (that's Revision 58 of CompilingInkscape) to the example after finding out somewhere that this solves the problem. (At least it did for me.) This line might need to be added to other sections (the missing ltmain.sh seems to be described there though) and INSTALL as well...
Cool thanks. Can you post a patch to the patch tracker for adding the correct info to the INSTALL file?
Just wanted to look at it, but the INSTALL file is autotools boilerplate, it's not in CVS, and I think most people ignore it anyway for the FSF copyright and the "These are generic installation instructions." line.
So the best thing would be to "move" INSTALL to INSTALL.gnu (this move needs to be implemented in the Inkscape-local autotools files) and have INSTALL be a copy of a Wiki page (CompilingInkscape?) instead.
What do you think?
- Felix
participants (5)
-
Bob Jamison -
Bryce Harrington -
bulia byak -
Felix Rabe -
Martin Wiebusch