Gunter Königsmann
2017-07-20 07:01:10 UTC
Dear all,
Currently the Maxima build seems on some systems to run into an error:
/<<PKGBUILDDIR>>/share/draw//drawutils.texi:151: Prev field of node `Venn diagrams' not pointed to. /<<PKGBUILDDIR>>/share/draw//drawutils.texi:36: This node (Vector fields) has the bad Next. /<<PKGBUILDDIR>>/share/draw//drawutils.texi:36: Next field of node `Vector fields' not pointed to (perhaps incorrect sectioning?). /<<PKGBUILDDIR>>/share/draw//drawutils.texi:196: This node (Function and variable index) has the bad Prev. makeinfo: Removing output file `/<<PKGBUILDDIR>>/share/draw/drawutils.info' due to errors; use --force to preserve. make[3]: *** [drawutils.info] Error 1
The full build log can be found at:
https://launchpadlibrarian.net/329818561/buildlog_ubuntu-precise-i386.maxima_5.40.0-0~201707200453~ubuntu12.04.1_BUILDING.txt.gz
The good news is that with massive help from the Debian developers I have now managed to fix the Debian build issues:
The presence of a directory named "binary" made the Debian build system think that the packages had already been built and installed in debian/tmp
Kind regards,
Gunter.
Currently the Maxima build seems on some systems to run into an error:
/<<PKGBUILDDIR>>/share/draw//drawutils.texi:151: Prev field of node `Venn diagrams' not pointed to. /<<PKGBUILDDIR>>/share/draw//drawutils.texi:36: This node (Vector fields) has the bad Next. /<<PKGBUILDDIR>>/share/draw//drawutils.texi:36: Next field of node `Vector fields' not pointed to (perhaps incorrect sectioning?). /<<PKGBUILDDIR>>/share/draw//drawutils.texi:196: This node (Function and variable index) has the bad Prev. makeinfo: Removing output file `/<<PKGBUILDDIR>>/share/draw/drawutils.info' due to errors; use --force to preserve. make[3]: *** [drawutils.info] Error 1
The full build log can be found at:
https://launchpadlibrarian.net/329818561/buildlog_ubuntu-precise-i386.maxima_5.40.0-0~201707200453~ubuntu12.04.1_BUILDING.txt.gz
The good news is that with massive help from the Debian developers I have now managed to fix the Debian build issues:
The presence of a directory named "binary" made the Debian build system think that the packages had already been built and installed in debian/tmp
Kind regards,
Gunter.
--
Diese Nachricht wurde von meinem Android-GerÀt mit K-9 Mail gesendet.
Diese Nachricht wurde von meinem Android-GerÀt mit K-9 Mail gesendet.