ecl build failure when building sage

133 views
Skip to first unread message

Jakub Jabłoński

unread,
Mar 31, 2020, 11:08:58 AM3/31/20
to sage-devel
Hi,

I'm trying to build sage on windows using CYGWIN_NT-10.0.
Revision I was trying to build is latest one from here:

Failure log in attachment, do you know how to fix that?
ecl-16.1.2.p5.log

Matthias Koeppe

unread,
Mar 31, 2020, 11:47:34 AM3/31/20
to sage-devel
top-level config.log and the config.log from the ecl build directory would be helpful.

ecl builds successfully on 9.1.beta9 at https://github.com/mkoeppe/sage/runs/547677310

Jakub Jabłoński

unread,
Mar 31, 2020, 5:31:21 PM3/31/20
to sage-devel
I have rebuilt everything from scratch, this time on develop branch. Attached logs. There waas no config.log in sage\build\pkgs\ecl
ecl-16.1.2.p5.log
config.log

John H Palmieri

unread,
Mar 31, 2020, 6:08:29 PM3/31/20
to sage-devel
When the build fails, there should be a message like:

The following package(s) may have failed to build...

* package:         ecl
  last build time: ...
  log file:        ...
  build directory:   /build/directory/is/here/

Check the build directory listed at the end for the file config.log. It may instead be in a subdirectory "src". My guess is that it's the file

local/var/tmp/sage/build/ecl-16.1.2.p5/src/confg.log

Matthias Koeppe

unread,
Mar 31, 2020, 6:41:14 PM3/31/20
to sage-devel

Try local/var/tmp/sage/build/ecl-16.1.2.p5/src/build/config.log

Jakub Jabłoński

unread,
Apr 1, 2020, 2:27:18 AM4/1/20
to sage-devel
Indeed it was there
config.log

Matthias Koeppe

unread,
Apr 1, 2020, 10:41:03 AM4/1/20
to sage-devel
Very strange, it looks like configure dies after running "gcc -V".

You could try the following

(cd '/home/Kuba/sage/local/var/tmp/sage/build/ecl-16.1.2.p5' && '/home/Kuba/sage/sage' --sh)
export CONFIG_SHELL="bash -x"
./spkg-install

and post output and the log file again

Jakub Jabłoński

unread,
Apr 1, 2020, 11:23:16 AM4/1/20
to sage-devel
result.txt is the output, config.log is from ecl build dir. 
result.txt
config.log

Jakub Jabłoński

unread,
Apr 1, 2020, 11:53:54 AM4/1/20
to sage-devel
And gcc -V is not working on my cygwin, "-V" is unrecognized command line option. What is it supposed to do?

Dima Pasechnik

unread,
Apr 1, 2020, 12:07:30 PM4/1/20
to sage-devel
On Wed, Apr 1, 2020 at 11:53 PM Jakub Jabłoński <goo...@gmail.com> wrote:
>
> And gcc -V is not working on my cygwin, "-V" is unrecognized command line option. What is it supposed to do?

this is normal - but it should not crash, it should exit gracefully.
The configure script it trying to figure out how to talk to your C
compiler by trying it with different options.
> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/64cd5e73-254e-4102-bb77-b72b36d50822%40googlegroups.com.

Matthias Koeppe

unread,
Apr 1, 2020, 12:17:23 PM4/1/20
to sage-devel
Could you post the output of "env" and of "set | grep BASH"?

Jakub Jabłoński

unread,
Apr 1, 2020, 12:40:55 PM4/1/20
to sage-devel
$ set|grep BASH
BASH=/bin/bash
BASHOPTS=cmdhist:complete_fullquote:expand_aliases:extquote:force_fignore:hostcomplete:interactive_comments:login_shell:progcomp:promptvars:sourcepath
BASH_ALIASES=()
BASH_ARGC=()
BASH_ARGV=()
BASH_CMDS=()
BASH_LINENO=()
BASH_SOURCE=()
BASH_VERSINFO=([0]="4" [1]="4" [2]="12" [3]="3" [4]="release" [5]="x86_64-unknown-cygwin")
BASH_VERSION='4.4.12(3)-release'
CYG_SYS_BASHRC=1
$ env
USERDOMAIN=DESKTOP-P41QQCN
OS=Windows_NT
COMMONPROGRAMFILES=C:\Program Files\Common Files
PROCESSOR_LEVEL=6
PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules
CommonProgramW6432=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
LANG=en_US.UTF-8
TZ=Europe/Warsaw
HOSTNAME=DESKTOP-P41QQCN
PUBLIC=C:\Users\Public
OLDPWD=/home/Kuba
USERNAME=Kuba
LOGONSERVER=\\DESKTOP-P41QQCN
PROCESSOR_ARCHITECTURE=AMD64
LOCALAPPDATA=C:\Users\Kuba\AppData\Local
COMPUTERNAME=DESKTOP-P41QQCN
FPS_BROWSER_APP_PROFILE_STRING=Internet Explorer
USER=Kuba
!::=::\
SYSTEMDRIVE=C:
USERPROFILE=C:\Users\Kuba
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
SYSTEMROOT=C:\Windows
USERDOMAIN_ROAMINGPROFILE=DESKTOP-P41QQCN
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 142 Stepping 10, GenuineIntel
PWD=/home/Kuba/sage/local/var/tmp/sage/build/ecl-16.1.2.p5
HOME=/home/Kuba
TMP=/tmp
SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:igncr:interactive-comments:monitor
OneDrive=C:\Users\Kuba\OneDrive
PROCESSOR_REVISION=8e0a
FPS_BROWSER_USER_PROFILE_STRING=Default
SAGE_KEEP_BUILT_SPKGS=yes
PROFILEREAD=true
NUMBER_OF_PROCESSORS=8
ProgramW6432=C:\Program Files
COMSPEC=C:\Windows\system32\cmd.exe
APPDATA=C:\Users\Kuba\AppData\Roaming
SHELL=/bin/bash
TERM=xterm
WINDIR=C:\Windows
ProgramData=C:\ProgramData
SHLVL=1
MINTTY_SHORTCUT=/cygdrive/c/Users/Public/Desktop/Cygwin64 Terminal.lnk
PRINTER=Lexmark X1100 Series
PROGRAMFILES=C:\Program Files
PyCharm=C:\Program Files\JetBrains\PyCharm 2019.2.3\bin;
ALLUSERSPROFILE=C:\ProgramData
TEMP=/tmp
DriverData=C:\Windows\System32\Drivers\DriverData
SESSIONNAME=Console
ProgramFiles(x86)=C:\Program Files (x86)
PATH=/usr/local/bin:/usr/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Windows/System32/OpenSSH:/cygdrive/c/Program Files/Git/cmd:/cygdrive/c/Program Files (x86)/Common Files/Ulead Systems/MPEG:/cygdrive/c/Toolsy/sqlite:/cygdrive/c/Program Files/TortoiseGit/bin:/cygdrive/c/Program Files/dotnet:/cygdrive/c/Users/Kuba/AppData/Local/Programs/Python/Python36/Scripts:/cygdrive/c/Users/Kuba/AppData/Local/Programs/Python/Python36:/cygdrive/c/Users/Kuba/AppData/Local/Microsoft/WindowsApps:/cygdrive/c/Program Files/JetBrains/PyCharm 2019.2.3/bin:/cygdrive/c/Program Files/Java/jdk-13/bin:/cygdrive/c/poppler-0.67.0/bin:/usr/lib/lapack
PS1=\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$
HOMEDRIVE=C:
INFOPATH=/usr/local/info:/usr/share/info:/usr/info
HOMEPATH=\Users\Kuba
ORIGINAL_PATH=/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Windows/System32/OpenSSH:/cygdrive/c/Program Files/Git/cmd:/cygdrive/c/Program Files (x86)/Common Files/Ulead Systems/MPEG:/cygdrive/c/Toolsy/sqlite:/cygdrive/c/Program Files/TortoiseGit/bin:/cygdrive/c/Program Files/dotnet:/cygdrive/c/Users/Kuba/AppData/Local/Programs/Python/Python36/Scripts:/cygdrive/c/Users/Kuba/AppData/Local/Programs/Python/Python36:/cygdrive/c/Users/Kuba/AppData/Local/Microsoft/WindowsApps:/cygdrive/c/Program Files/JetBrains/PyCharm 2019.2.3/bin:/cygdrive/c/Program Files/Java/jdk-13/bin:/cygdrive/c/poppler-0.67.0/bin
EXECIGNORE=*.dll
_=/usr/bin/env

Message has been deleted

Jakub Jabłoński

unread,
Apr 3, 2020, 3:09:52 AM4/3/20
to sage-devel
I have removed whole cygwin and reinstalled everything, now ecl is not failing. However sage is still not building. 
Building log ends with following text (can't upload logs as attachment, don't know why)
[sagelib-9.1.beta9] collect2: error: ld returned 1 exit status
[sagelib-9.1.beta9] error: command 'g++' failed with exit status 1
[sagelib-9.1.beta9] make[4]: *** [Makefile:33: sage] Error 1
[sagelib-9.1.beta9] make[4]: Leaving directory '/home/Kuba/sage/src'
[sagelib-9.1.beta9] 
[sagelib-9.1.beta9] real 7m43.455s
[sagelib-9.1.beta9] user 17m51.494s
[sagelib-9.1.beta9] sys 0m56.723s
make[3]: *** [Makefile:1942: sagelib] Error 2
make[3]: Leaving directory '/home/Kuba/sage/build/make'
make[2]: *** [Makefile:1801: all-start] Error 2
make[2]: Leaving directory '/home/Kuba/sage/build/make'

real 7m56.612s
user 17m56.122s
sys 1m5.057s
***************************************************************
Error building Sage.

Dima Pasechnik

unread,
Apr 3, 2020, 3:13:52 AM4/3/20
to sage-devel
from this part of the log it is not possible to see much, except that Sage's Python library has failed to build.

Please paste as many lines above these from the output as you can.


--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.

Jakub Jabłoński

unread,
Apr 3, 2020, 4:40:18 AM4/3/20
to sage-devel
Okay, uploaded only log which seems to be relevant (it's failing)
sagelib-9.1.beta9.log

Dima Pasechnik

unread,
Apr 3, 2020, 5:00:13 AM4/3/20
to sage-...@googlegroups.com
you are building fflas-ffpack with OpenMP on, for some reason.
it should be possible to modify its spkg-install.in file so that it does not happen, rebuild it, and sagelib itself.


On Fri, 3 Apr 2020 at 16:40, Jakub Jabłoński <goo...@gmail.com> wrote:
Okay, uploaded only log which seems to be relevant (it's failing)

--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.

Dima Pasechnik

unread,
Apr 3, 2020, 5:57:29 AM4/3/20
to sage-...@googlegroups.com
could you post the top-level config.log ?

Jakub Jabłoński

unread,
Apr 3, 2020, 6:46:49 AM4/3/20
to sage-devel


On Friday, April 3, 2020 at 11:57:29 AM UTC+2, Dima Pasechnik wrote:
could you post the top-level config.log ?

On Fri, 3 Apr 2020 at 16:59, Dima Pasechnik <dim...@gmail.com> wrote:
you are building fflas-ffpack with OpenMP on, for some reason.
it should be possible to modify its spkg-install.in file so that it does not happen, rebuild it, and sagelib itself.

On Fri, 3 Apr 2020 at 16:40, Jakub Jabłoński <goo...@gmail.com> wrote:
Okay, uploaded only log which seems to be relevant (it's failing)

--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-...@googlegroups.com.
config.log

Jakub Jabłoński

unread,
Apr 3, 2020, 7:55:57 AM4/3/20
to sage-devel
I have added --disable-openmp here in spkg-install.in:
if [ "$SAGE_FAT_BINARY" = yes ]; then
    FFLAS_FFPACK_CONFIGURE="--disable-openmp --disable-sse --disable-sse2 --disable-sse3 --disable-ssse3 --disable-sse41 --disable-sse42 --disable-fma --disable-fma4 --disable-avx --disable-avx2 --disable-avx512f --disable-avx512dq --disable-avx512vl $FFLAS_FFPACK_CONFIGURE"
fi

Previous log is after adding that, new log

Dima Pasechnik

unread,
Apr 3, 2020, 8:00:13 AM4/3/20
to sage-devel
it seems that your addition is conditional on SAGE_FAT_BINARY being set to yes.

It should not be so.

To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/62253b78-f79c-45b9-b6ea-ea80e5cd30a2%40googlegroups.com.

Jakub Jabłoński

unread,
Apr 3, 2020, 10:00:26 AM4/3/20
to sage-devel
Current version:

# If SAGE_FAT_BINARY is set, disable all processor-specific optimizations
if [ "$SAGE_FAT_BINARY" = yes ]; then
    FFLAS_FFPACK_CONFIGURE="--disable-sse --disable-sse2 --disable-sse3 --disable-ssse3 --disable-sse41 --disable-sse42 --disable-fma --disable-fma4 --disable-avx --disable-avx2 --disable-avx512f --disable-avx512dq --disable-avx512vl $FFLAS_FFPACK_CONFIGURE"
fi

FFLAS_FFPACK_CONFIGURE="--disable-openmp $FFLAS_FFPACK_CONFIGURE"

Still failing
config.log
sagelib-9.1.beta9.log

Dima Pasechnik

unread,
Apr 3, 2020, 10:13:39 AM4/3/20
to sage-devel
have you rebuilt fflas-ffpack after your addition of flags?
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/770c6ffd-e8bb-45bd-be07-a09bcfd9b688%40googlegroups.com.

Jakub Jabłoński

unread,
Apr 3, 2020, 11:03:56 AM4/3/20
to sage-devel
Sorry, didn't notice it's not rebuilding. Done it now and issue with omp still occurs. 

Dima Pasechnik

unread,
Apr 3, 2020, 11:04:57 PM4/3/20
to sage-devel
On Fri, Apr 3, 2020 at 11:04 PM Jakub Jabłoński <goo...@gmail.com> wrote:
>
> Sorry, didn't notice it's not rebuilding. Done it now and issue with omp still occurs.

hmm. Somewhere something instists on using openmp.

Perhaps, do

make distclean
make
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/5f09d635-cf55-4609-a68a-486e2ae0fe9d%40googlegroups.com.

Jakub Jabłoński

unread,
Apr 5, 2020, 4:01:55 AM4/5/20
to sage-devel
Didn't help, started installing ubuntu on virtual machine, will try here. Thanks for helping. 

Dima Pasechnik

unread,
Apr 5, 2020, 6:59:24 AM4/5/20
to sage-devel
Perhaps you can tell us what CYGWIN_NT-10.0 is, and how is it
different from the usual 64-bit Cygwin?
The most recent version 3.1.4, cf
https://sourceware.org/legacy-ml/cygwin-announce/2020-02/msg00006.html
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/f64a5b8e-5229-4ad1-b076-e78b32cf092f%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages