Quantcast
Channel: MobileRead Forums - Kobo Developer's Corner
Viewing all articles
Browse latest Browse all 1561

kobo-reader sdk installation buged on WSL2

$
0
0
Hello,

I'm trying to install the kobo sdk/toolchain (https://github.com/kobolabs/Kobo-Reader) on my WSL2 (so it is 32 bits compatible) debian (64 bits). But I'm stuck on some automake error when trying to build lcms. I'm stuck with the following log and I don't know automake enough to fix it by my own for now :

Code:

aramir@SHODAN:~/kobo/tmp$ ~/kobo/KoboLabs/build/build-all.sh
No need to rebuild openssl
No need to rebuild iconv
No need to rebuild expat
No need to rebuild dbus
No need to rebuild gettext
No need to rebuild glib
No need to rebuild libusb
No need to rebuild zlib
No need to rebuild libzip
No need to rebuild libxml2
No need to rebuild dosfstools
No need to rebuild wireless_tools
No need to rebuild wpa_supplicant
No need to rebuild libpng
No need to rebuild jpegsrc
No need to rebuild busybox
No need to rebuild libtool
No need to rebuild attr
No need to rebuild acl
No need to rebuild udev
No need to rebuild lcms
patching file autogen.sh
~/kobo/tmp/libmng-1.0.10 ~/kobo/tmp
copying configure.in
copying automake template
running aclocal
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:18: error: automatic de-ANSI-fication support has been removed
/usr/share/aclocal-1.16/obsolete.m4:26: AM_C_PROTOTYPES is expanded from...
configure.in:18: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: error: echo failed with exit status: 1
running libtoolize
running automake
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in: error: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE,
configure.in: that aclocal.m4 is present in the top-level directory,
configure.in: and that aclocal.m4 was recently regenerated (using aclocal)
configure.in:23: installing './install-sh'
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
Makefile.am:12: error: Libtool library used but 'LIBTOOL' is undefined
Makefile.am:12:  The usual way to define 'LIBTOOL' is to add 'LT_INIT'
Makefile.am:12:  to 'configure.in' and run 'aclocal' and 'autoconf' again.
Makefile.am:12:  If 'LT_INIT' is in 'configure.in', make sure
Makefile.am:12:  its definition is in aclocal's search path.
building configure script
configure.in:9: error: possibly undefined macro: AM_INIT_AUTOMAKE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:18: error: possibly undefined macro: AM_C_PROTOTYPES
configure.in:22: error: possibly undefined macro: AM_PROG_LIBTOOL
Build failed at libmng.sh, aborting

Did someone managed to install the sdk ?

I obviously already had tons of little problems prior to that point. Just to name a few :
- tons of libs are not mentioned in the requirements, just read the errors as they come and install what's necessary
- there seem to be a syntax error in openssl pod files so I tweaked its script and changed install -> install_sw to skip the .pod files. So I won't have openssl doc but who cares
- the obscure CodeSourcery require a Java jre AND a x11 server to launch its graphical installer (so I had to configure VcXsrv)
- CodeSourcery refused to run if DASH is the default shell, so I had to turn it off for a short time with dpkg-reconfigure -plow dash
- the damn CodeSourcery arm compiler tools are all named arm-none-linux-gnueabi-SOMETHING instead of arm-linux-SOMETHING so I had to write symbolic links for each of them
-for some reason on debian, libtool doesn't install the libtool binaries, you have to install libtool-bin
- etc

Also I'm trying to install this one because it's the offiicial one and from what I could gather in this thread (https://www.mobileread.com/forums/sh...d.php?t=330120) every other ones have some trade off :
- koxtoolchain (https://github.com/koreader/koxtoolchain) : has a whole paragraph on their github page about a nickel TC version for kobo that basically shouldn't be used. Maybe there is a proper "kobo" version in addition to that "nickel TC" version. It's not really clear so please correct me if I'm in the wrong
- nickelTC (https://github.com/pgaskin/NickelTC) wich sounds just like the "do not use version" mentioned above. Also it's a docker thing, and I don't really like docker, I don't want a VM in my VM in my VM in my VM, etc but meh ok


Thanks for reading so far, any help is appreciated.

Viewing all articles
Browse latest Browse all 1561

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>