[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [mxe-octave] dev branch: build failure in documentation stage? (was
From: |
PhilipNienhuis |
Subject: |
Re: [mxe-octave] dev branch: build failure in documentation stage? (was Re: [mxe-octave] dev branch: build failure in install stage?) |
Date: |
Wed, 20 Jul 2016 03:40:34 -0700 (PDT) |
tmacchant wrote
> ----- Original Message -----
>
>> From: Mike Miller
>> To: Tatsuro MATSUOKA
>> Cc: "octave-maintainers> Date: 2016/7/20, Wed 03:31
>> Subject: Re: [mxe-octave] dev branch: build failure in install stage?
>>
>> On Tue, Jul 19, 2016 at 12:48:10 +0900, Tatsuro MATSUOKA wrote:
>>> [mxe-octave] dev branch: build failure in install stage?
>>>
>>>
>>> revision of mxe octave 4172:4117faf76988
>>>
>>>
>>> --enable-windows64
>>>
>>>
>>>
>>> /usr/bin/install -c -m 644 libinterp/dldfcn/PKG_ADD
>> /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave-install/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/usr/x86_64-w64-mingw32/lib/octave/4.1.0+/oct/x86_64-w64-mingw32/PKG_ADD;
>>
>> \
>>> fi
>>> cd
>> /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave-install/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/usr/x86_64-w64-mingw32/lib/octave/4.1.0+
>>
>> && \
>>> for ltlib in libinterp/dldfcn/__delaunayn__.la
>>> libinterp/dldfcn/__eigs__.la
>> libinterp/dldfcn/__fltk_uigetfile__.la libinterp/dldfcn/__glpk__.la
>> libinterp/dldfcn/__init_fltk__.la libinterp/dldfcn/__init_gnuplot__.la
>> libinterp/dldfcn/__osmesa_print__.la libinterp/dldfcn/__voronoi__.la
>> libinterp/dldfcn/amd.la libinterp/dldfcn/audiodevinfo.la
>> libinterp/dldfcn/audioread.la libinterp/dldfcn/ccolamd.la
>> libinterp/dldfcn/chol.la libinterp/dldfcn/colamd.la
>> libinterp/dldfcn/convhulln.la libinterp/dldfcn/dmperm.la
>> libinterp/dldfcn/fftw.la libinterp/dldfcn/qr.la
>> libinterp/dldfcn/symbfact.la
>> libinterp/dldfcn/symrcm.la; do \
>>> f=`echo $ltlib | /bin/sed 's,.*/,,'`; \
>>> dl=`/bin/sed -n -e
>> "s/dlname='\([^']*\)'/\1/p" < $f`; \
>>> if [ -n "$dl" ]; then \
>>> /usr/bin/install -c $dl
>> /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave-install/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/usr/x86_64-w64-mingw32/lib/octave/4.1.0+/oct/x86_64-w64-mingw32/`echo
>>
>> $f | /bin/sed 's,^lib,,; s,\.la$,.oct,'`; \
>>> else \
>>> echo "error: dlname is empty in $ltlib!"; \
>>> exit 1; \
>>> fi; \
>>> lnames=`/bin/sed -n -e
>> "s/library_names='\([^']*\)'/\1/p" < $f`;
>> \
>>> if [ -n "$lnames" ]; then \
>>> rm -f $f $lnames $dl; \
>>> fi \
>>> done
>>> /bin/mkdir -p
>> /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave-install/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/usr/x86_64-w64-mingw32/share/octave/4.1.0+/etc
>>> f=libinterp/DOCSTRINGS; \
>>> if test -f $f; then d=; else
>> d="/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/";
>>
>> fi; \
>>> /usr/bin/install -c -m 644 "$d$f"
>> /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave-install/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/usr/x86_64-w64-mingw32/share/octave/4.1.0+/etc/built-in-docstrings
>>> make[6]: *** No rule to make target `libinterp/deprecated-config.h',
>> needed by `install-deprecated-config-h'. Stop.
>>>
>>> Is the above known issue?
>>
>> No, but this should be fixed now with
>>
>> http://hg.savannah.gnu.org/hgweb/octave/rev/da413c03920c
>>
>> Thanks!
>>
>> --
>> mike
> Perhaps time lag exists between mercurial repo. and hrdra site, I have met
> the same error using default branch source download by
> mxe-octave system.
>
> I then cloned mecurial repo and executed ./bootstrap and archived as
> octave-4.1.0+.tar.gz
> and executed make zip-dist.
>
> I have met another error on documentation.
>
>
> /bin/bash run-octave --norc --silent --no-history --path
> /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/doc/interpreter/
> --eval "geometryimages ('doc/interpreter/', 'voronoi', 'txt');"
> /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/.build/libtool:
> line 11645:
> /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/.build/src/octave:
> No such file or directory
> make[4]: *** [doc/interpreter/voronoi.txt] Error 127
> make[4]: Leaving directory
> `/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/.build'
> make[3]: *** [install-recursive] Error 1
> make[3]: Leaving directory
> `/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/.build'
> make[2]: *** [install] Error 2
> make[2]: Leaving directory
> `/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/.build'
> make[1]: *** [build-only-default-octave] Error 2
> make[1]: Leaving directory
> `/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64'
Yesterday evening I've made a cross-build with the tip (incl. that cset by
Mike) and that went fine. Maybe limiting the number of make jobs might help?
(I usually limit it to 2 or 3).
I have a yet different problem with that same tip but with several
additional patches (__wglob__, light, ...):
in the very latest install stage, libtool complains that it can't find
.build/src/octave (where I think it wants octave.exe). Looking at the
patches involved I can't follow that they'd influence that part of the
build. Yet I've seen this before, some years ago.
Philip
Philip
--
View this message in context:
http://octave.1599824.n4.nabble.com/mxe-octave-dev-branch-build-failure-in-install-stage-tp4678650p4678680.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.
- [mxe-octave] dev branch: build failure in install stage?, Tatsuro MATSUOKA, 2016/07/18
- Re: [mxe-octave] dev branch: build failure in install stage?, Mike Miller, 2016/07/19
- [mxe-octave] dev branch: build failure in documentation stage? (was Re: [mxe-octave] dev branch: build failure in install stage?), Tatsuro MATSUOKA, 2016/07/20
- Re: [mxe-octave] dev branch: build failure in documentation stage? (was Re: [mxe-octave] dev branch: build failure in install stage?), Tatsuro MATSUOKA, 2016/07/21
- Re: [mxe-octave] dev branch: build failure in documentation stage? (was Re: [mxe-octave] dev branch: build failure in install stage?), Philip Nienhuis, 2016/07/22
- Re: [mxe-octave] dev branch: build failure in documentation stage? (was Re: [mxe-octave] dev branch: build failure in install stage?), Tatsuro MATSUOKA, 2016/07/22
- Re: [mxe-octave] dev branch: build failure in documentation stage? (was Re: [mxe-octave] dev branch: build failure in install stage?), PhilipNienhuis, 2016/07/22
- Re: [mxe-octave] dev branch: build failure in documentation stage? (was Re: [mxe-octave] dev branch: build failure in install stage?), Mike Miller, 2016/07/22
- Re: [mxe-octave] dev branch: build failure in documentation stage? (was Re: [mxe-octave] dev branch: build failure in install stage?), John W. Eaton, 2016/07/22
- Re: [mxe-octave] dev branch: build failure in documentation stage? (was Re: [mxe-octave] dev branch: build failure in install stage?), Tatsuro MATSUOKA, 2016/07/22