cascent / neovim-cygwin

cygport files to build neovim and dependencies for Cygwin, and binary releases
25 stars 3 forks source link

libuv : *** ERROR: autoreconf failed => libtoolize: copying file './ltmain.sh' #4

Open SebastienD75 opened 6 years ago

SebastienD75 commented 6 years ago

Hello,

After : cygport libuv/libuv.cygport fetch cygport libuv/libuv.cygport all

I have the following error when I try to build with cyport (with libuv 1.18 or 1.19) :

$ cygport libuv/libuv.cygport all
>>> Preparing libuv-1.19.1-0.x86_64
>>> Unpacking source libuv-1.19.1.tar.gz
>>> Preparing working source directory
*** Info: applying patch libuv-1.19.1-0.src.patch (-p0):
patching file m4/libuv-extra-automake-flags.m4
>>> Compiling libuv-1.19.1-0.x86_64
autoreconf-2.69: Entering directory `.'
autoreconf-2.69: configure.ac: not using Gettext
autoreconf-2.69: running: aclocal --force -I m4
autoreconf-2.69: configure.ac: tracing
autoreconf-2.69: running: libtoolize --copy --force
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
autoreconf-2.69: libtoolize failed with exit status: 1
*** ERROR: autoreconf failed

Any Idea ? Thanks !

Sébastien

cascent commented 6 years ago

I assume it's a missing build-time dependency, but not sure what it would be

I've attached the output of cygcheck -c on the VM I used to build the binaries: packages.txt I tried not to install too many packages.

cascent commented 6 years ago

here's what the start of the build output looks like for me:

>>> Preparing libuv-1.19.1-0.x86_64
>>> Unpacking source libuv-1.19.1.tar.gz
>>> Preparing working source directory
*** Info: applying patch libuv-1.19.1-0.src.patch (-p0):
patching file m4/libuv-extra-automake-flags.m4
>>> Compiling libuv-1.19.1-0.x86_64
autoreconf-2.69: Entering directory `.'
autoreconf-2.69: configure.ac: not using Gettext
autoreconf-2.69: running: aclocal --force -I m4
autoreconf-2.69: configure.ac: tracing
autoreconf-2.69: running: libtoolize --copy --force
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
autoreconf-2.69: running: /usr/bin/autoconf-2.69 --force
autoreconf-2.69: configure.ac: not using Autoheader
autoreconf-2.69: running: automake --add-missing --copy --force-missing
configure.ac:38: installing './ar-lib'
configure.ac:25: installing './compile'
configure.ac:22: installing './config.guess'
configure.ac:22: installing './config.sub'
configure.ac:21: installing './install-sh'
configure.ac:21: installing './missing'
Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
autoreconf-2.69: Leaving directory `.'
/tmp/neovim-cygwin/libuv/libuv-1.19.1-0.x86_64/src/libuv-1.19.1/configure --srcdir=/tmp/neovim-cygwin/libuv/libuv-1.19.1-0.x86_64/src/libuv-1.19.1 --prefix=/usr --exec-prefix=/usr --localstatedir=/var --sysconfdir=/etc --docdir=/usr/share/doc/libuv --htmldir=/usr/share/doc/libuv/html -C --enable-shared --disable-static
configure: loading site script /usr/share/config.site
configure: loading cache config.cache
SebastienD75 commented 6 years ago

Thanks for your quick reply.

I don't see much difference with my config, maybe cygport 3.31 VS 3.25 ?! but my cygwin setup don't have access to 3.25 version..., here are the main package differences :

3c3
< _autorebase               001007-1            OK
---
> _autorebase               001006-1            OK
25,26c26,28
< ca-certificates           2.22-1              OK
< calm                      20180131-1          OK
---
> ca-certificates           2.16-1              OK
> calm                      20171204-1          OK
> cmake                     3.6.2-1             OK
29c31
< cygport                   0.31.0-1            OK
---
> cygport                   0.25.0-1            OK
32,33c34,35
< cygwin                    2.10.0-1            OK
< cygwin-devel              2.10.0-1            OK
---
> cygwin                    2.9.0-3             OK
> cygwin-devel              2.9.0-3             OK
40c42
< file                      5.32-1              OK
---
> file                      5.30-1              OK
43,45c45,47
< gawk                      4.2.1-1             OK
< gcc-core                  6.4.0-5             OK
< gcc-g++                   6.4.0-5             OK
---
> gawk                      4.2.0-1             OK
> gcc-core                  6.4.0-4             OK
> gcc-g++                   6.4.0-4             OK

Unfortunately I don't have much time to find out what's going on... If I'm the only one to have problem it's probably my config.

Anyway thanks again for your work !

cascent commented 6 years ago

aw :( i don't know how many other people build this, but have been able to build on three different cygwin installs myself (all except my build VM customized to my own liking) I just updated all the packages installed in my build vm, and was able to rebuild libuv

is there any chance you have non-cygwin tools on your PATH? have you tried to build any other autoconf/automake packages with cygport?

SebastienD75 commented 6 years ago

I tried with a the minimal PATH : <'/usr/bin:/usr/local/bin'> and it gives the same error for libuv. I didn't try to build any other package with cyport, but I tried to build <unibilium> and I have an error too, not the same one :

(...)
pod2man -c "unibilium" -s3 -r "unibilium-2.0.0" doc/unibi_int_from_var.pod | gzip > man/unibi_int_from_var.3.gz
pod2man -c "unibilium" -s3 -r "unibilium-2.0.0" doc/unibi_short_name_str.pod | gzip > man/unibi_short_name_str.3.gz
make: *** [Makefile:69: unibilium.lo] Error 1
make: *** Attente des tâches non terminées....
make: *** [Makefile:69: uninames.lo] Error 1
make: *** [Makefile:72: uniutil.lo] Error 1
*** ERROR: make failed

If I go to unibilium/unibilium-2.0.0-0.x86_64/src/ and try to build it with 'make', everything goes almost well, i just have a warning with static/dynamic build: libtool: warning: undefined symbols not allowed in x86_64-unknown-cygwin shared libraries; building static only libtool: link: ar cru .libs/libunibilium.a unibilium.o uninames.o uniutil.o :

(...)
libtool --mode=compile --tag=CC cc -I. -DTERMINFO_DIRS='""' -Wall -std=c99 -O2  -o uniutil.lo -c uniutil.c
libtool: compile:  cc -I. -DTERMINFO_DIRS=\"\" -Wall -std=c99 -O2 -c uniutil.c  -DDLL_EXPORT -DPIC -o .libs/uniutil.o
libtool: compile:  cc -I. -DTERMINFO_DIRS=\"\" -Wall -std=c99 -O2 -c uniutil.c -o uniutil.o >/dev/null 2>&1
libtool --mode=link --tag=CC cc  -rpath '/usr/local/lib' -version-info 4:0:0 -o libunibilium.la unibilium.lo uninames.lo uniutil.lo
libtool: warning: undefined symbols not allowed in x86_64-unknown-cygwin shared libraries; building static only
libtool: link: ar cru .libs/libunibilium.a  unibilium.o uninames.o uniutil.o
libtool: link: ranlib .libs/libunibilium.a

=> so libunibilium.a OK and unibilium.lo KO, but i don't kwnow if there is a link with libuv problems... (I'm running cygwin with windows10 )