Le 29/12/2017 à 03:50, Muddleglum Smith a écrit :
But the simpler and most reasonable is to install intltool which
will definitely be packaged in Fedora.
Instead of intltoolize? New one on me. I
had thought, according to the
script, that the -ize was needed. Live and learn, unlearn, semi-learn.
intltoolize is a script that most of the time comes with the rest of the
intltool suite, so yeah it's generally in the "intltool" package.
Thank you for that hint, Colomban. I got a step
I'm now here -- Installed intltool and reran:
(I numbered the lines I will comment.)
1. You should add the contents of '/usr/share/aclocal/intltool.m4' to
autoreconf: Entering directory `.'
2. autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I build/cache -I build -I
build/bundled -I geanypy/m4 --install
3. build/i18n.m4:15: warning: macro 'AM_GLIB_GNU_GETTEXT' not found in library
aclocal: installing 'build/cache/nls.m4' from
aclocal: installing 'build/cache/pkg.m4' from
autoreconf: configure.ac: tracing
4. autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
5. configure.ac:15: error: possibly undefined macro: AC_DISABLE_STATIC
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:16: error: possibly undefined macro: AC_PROG_LIBTOOL
configure:5224: error: possibly undefined macro: AM_GLIB_GNU_GETTEXT
autoreconf: /usr/bin/autoconf failed with exit status: 1
1. First line, right off, is a need to know. I should do this?
Shouldn't be needed, not sure the warning has any relevance, and might
come from the fact you ran autogen when you didn't have intltool.
Should be fine to ignore now.
2. Guessing this is fine. It is installed so the
developer choose not
to use gettext.
It's actually misleading because we do use gettext, but yeah it's fine
and to be expected, no problem there.
3. Seems important. The parameters indicate that only
markdown will be
installed. Then why is i18n.m4 being asked to the party?
You should really check Geany's docs telling you what to install before
running autogen, it'll make it simpler as it's the sale for
Geany-Plugins (I'm not sure if we have the same docs there, would be
worth checking): https://github.com/geany/geany/#requirements
Basically you need automake, autoconf, libtool, intltool glib-devel,
gtk2-devel (or gtk3-devel, depending on which version you need, and
that'll depend how Geany itslef was built: you can check in geany's
debug messages or you package manager's dependency lists for geany),
plus Markdown plugin's own dependencies, maybe libmarkdown and webkitgtk
(again, either webkit1gtk for GTK2, or webkitgtk3 for GTK3) -- beware:
webkitgtk is NOT the same as webkit2gtk as is no compatible.
4. Again, guessing that this line is fine. I don't
have it installed,
not having much to do with using shared libraries. I suppose I should
go back to using C++ instead of using bash scripts just to become
acquainted with this. Getting close to a stack overflow, though.
5. Seems like there is a need to use use m4_pattern_allow. Either
that, or there are too many other problems looming in the murky haze.
Again, dependencies are missing. Yeah it's not very clear from the
messages, but there not much we can do on our part there (it's Autoconf
here), but manually checking you have everything beforehand.
Any help out of this dungeon?
Hope this will give you a few doors down, and a chance to take on the
final boss :)