Error: FLINT failed to pass on Opensuse 13.1

[Carl Robitaille]

Hello,

I tried to compile sage for the first time and got an error. Following the instructions in the log, I'm posting here about the error I got in /home2/downloads/sage-6.5/logs/pkgs/flint-2.4.4.log

==========
mkdir -p build/interfaces/test
make[4]: Entering directory `/home2/downloads/sage-6.5/local/var/tmp/sage/build/flint-2.4.4/src'
    CXX   build/interfaces/test/t-NTL-interface
g++: error: build/interfaces/NTL-interface.o: No such file or directory
make[4]: *** [build/interfaces/test/t-NTL-interface] Error 1
make[4]: Leaving directory `/home2/downloads/sage-6.5/local/var/tmp/sage/build/flint-2.4.4/src'
/bin/sh: line 2: build/interfaces/test/t-NTL-interface: No such file or directory
make[3]: *** [check] Error 127
make[3]: Leaving directory `/home2/downloads/sage-6.5/local/var/tmp/sage/build/flint-2.4.4/src'
Error: FLINT failed to pass its test suite.

real    9m15.980s
user    30m0.970s
sys     0m59.023s
************************************************************************
Error testing package flint-2.4.4
************************************************************************
Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the relevant part of the log file
  /home2/downloads/sage-6.5/logs/pkgs/flint-2.4.4.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/home2/downloads/sage-6.5/local/var/tmp/sage/build/flint-2.4.4 and type 'make check' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/home2/downloads/sage-6.5/local/var/tmp/sage/build/flint-2.4.4' && '/home2/downloads/sage-6.5/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.
************************************************************************
Found local metadata for flint-2.4.4
Found local sources at /home2/downloads/sage-6.5/upstream/flint-2.4.4.tar.gz
Checksum: 71075ce6d851af6244110644479bf29b4403212c vs 71075ce6d851af6244110644479bf29b4403212c
flint-2.4.4
====================================================
Setting up build directory for flint-2.4.4
Finished set up
****************************************************
Host system:
Linux h1n1 3.11.10-25-desktop #1 SMP PREEMPT Wed Dec 17 17:57:03 UTC 2014 (8210f77) x86_64 x86_64 x86_64 GNU/Linux
****************************************************
C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/4.8/lto-wrapper
Target: x86_64-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.8 --enable-ssp --disable-libssp --disable-plugin --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --disable-libgcj --disable-libmudflap --with-slibdir=/lib64 --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --enable-linker-build-id --program-suffix=-4.8 --enable-linux-futex --without-system-libunwind --with-arch-32=i586 --with-tune=generic --build=x86_64-suse-linux
Thread model: posix
gcc version 4.8.1 20130909 [gcc-4_8-branch revision 202388] (SUSE Linux)
****************************************************
==========


If you have suggestions on how to look for the problem, I could test it for you on my system.

Thanks

Carl

[François Bissey]

You have SAGE_CHECK enabled. I know we had that failure in
sage-on-gentoo because we produce a .lo file not a .o one. I didn't think
that was happening in vanilla sage.
Try adding
https://raw.githubusercontent.com/cschwan/sage-on-gentoo/master/sci-mathematics/flint/files/flint-2.4.4-test.patch
in build/pkgs/flint/patches/


Francois

> --
> 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
> <mailto:sage-devel+...@googlegroups.com>.
> To post to this group, send email to sage-...@googlegroups.com
> <mailto:sage-...@googlegroups.com>.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

[Carl Robitaille]

Bonjour François,

Thank you very much for your 1 character patch :-)

Trying it right now, but I have no doubt that this will fix the problem after reading the Makefile.

Is there a bug report already filed for this?

Carl

[François Bissey]

I don't think so but I almost certainly reviewed a number of flint
upgrade tickets in which it should have been spotted.
I'd like to hear from your results before opening the ticket and we
have a new version bump for flint and I'll have to check if it has
been fixed there before acting in any case.

Francois

[Carl Robitaille]

It didn't work. But then again, I did a "make distclean", so the Makefile probably got recreated. I have to familiarise myself with the Makefiles, directories, etc, before I can find what would be the fix. Rebuilding and running the tests takes too long. I read the installation documentation and I'm trying to limit the number of things getting tested and tested.

=====
tar xvfz sage-6.5.tar.gz
cd sage-6.5
export MAKE="make -j8"                                                                
export SAGE_CHECK_PACKAGES="flint"
export SAGE_KEEP_BUILT_SPKGS="yes"
make build
=====

Once it's built, I'll have a closer look at the error and report back.

Carl

[Carl Robitaille]

Doh! I just saw that your patch was for Makefile.in and not Makefile..... of course!!! ;-) That explains de problem with the distclean.

Rebuilding..... and will report back.

Carl

[Carl Robitaille]

You can open the ticket. The patch worked and all the tests for flint passed. Here's what I did in order to test it:

========

tar xvfz sage-6.5.tar.gz
cd sage-6.5

# MANUALLY PATCHED Makefile.in in upstream/flint-2.4.4.tar.gz
# MANUALLY PATCHED build/pkgs/flint/checksums.ini to reflect the changes in flint-2.4.4.tar.gz
export MAKE="make -j8"                                                                
export SAGE_CHECK="yes"
make
========

That said, when using SAGE_CHECK="yes", I get another error:

========
sage-6.5> grep -H "^Error" *.log logs/*log logs/pkgs/*.log
config.log:Error: Non-numeric character in statement label at (1)
config.log:Error: Unclassifiable statement at (1)
config.log:Error: Expected expression in PRINT statement at (1)
config.log:Error: Invalid character in name at (1)
logs/install.log:Error testing package python-2.7.8
logs/install.log:Error building Sage.
logs/pkgs/config.log:Error: Non-numeric character in statement label at (1)
logs/pkgs/config.log:Error: Unclassifiable statement at (1)
logs/pkgs/config.log:Error: Expected expression in PRINT statement at (1)
logs/pkgs/config.log:Error: Invalid character in name at (1)
logs/pkgs/python-2.7.8.log:Error testing package python-2.7.8
========

The errors in config.log are present even if SAGE_CHECK is not set to yes, but it doesn't stop sage from being built.

Carl

[Mike Zabrocki]

I also ran into this error and was about to post a question about how to resolve it and I saw this posting.  Thanks.

The patch + setting SAGE_CHECK to yes also seems to resolve the problem for me.

-Mike