Dear Volker,

I am not *totally* SOL : I re-started with a fresh copy pf the RC3 tarball 
and recompiled, installed a few modules (database_gap, dot2tex and 
sage_mode).

The first attempt to ptestlong gave me the same problem ; however, moving 
$SAGE_ROOT/local/bin/libtinfo* out of the way allowed me to ptestlong (all 
tests passed, by the way). Thanks a lot for the hint !

However, I still think that this kind of problems should be solved before 
the next release. How should a ticket be written in order to find a good 
solution ?

HTH,

--
Emmanuel Charpentier

Le samedi 10 octobre 2015 12:06:22 UTC+2, Volker Braun a écrit :
>
> Thats a general problem with [DY]LD_LIBRARY_PATH; if one of the preloaded 
> libraries conflicts with one used by bash or other Sage dependencies then 
> you are thoroughly screwed. As the reply states, you can try to 
> delete usr/local/sage/local/lib/libtinfo.so.5 and cross your fingers. If 
> you are lucky then Sage works with the system libtinfo.so; if not then you 
> are SOL.
>
>
>
> On Saturday, October 10, 2015 at 10:13:10 AM UTC+2, Emmanuel Charpentier 
> wrote:
>>
>> On a machine running Debian testing, I have been able to upgrade my sage 
>> installation from 6.9beta1 to 6.9beta3 then to 6.9rc3, but I have a 
>> (probably small) problem with sage-specific version of ncurses which break 
>> the testing suite.
>>
>> Launching "make ptestlong gives me the following :
>>
>> [ ...Snipping the mandatory doc reinstallation... ]
>>
>> Done updating paths.
>> Running doctests with ID 2015-10-10-09-44-21-4e3d6f95.
>> git: /usr/local/sage/local/lib/libcrypto.so.1.0.0: no version information 
>> available (required by git)
>> Git branch: develop
>> Using --optional=database_gap,dot2tex,mpir,openssl,python2,sage,sage_mode
>> Doctesting entire Sage library.
>> Sorting sources by runtime so that slower doctests are run first....
>> Doctesting 3192 files using 8 threads.
>> sage -t --long --warn-long 72.4 
>> src/sage/schemes/elliptic_curves/ell_rational_field.py
>> **********************************************************************
>> File "src/sage/schemes/elliptic_curves/ell_rational_field.py", line 300, 
>> in 
>> sage.schemes.elliptic_curves.ell_rational_field.EllipticCurve_rational_field._set_modular_degree
>> Failed example:
>>     E.modular_degree()
>> Expected:
>>     1984
>> Got:
>>     bash: /usr/local/sage/local/lib/libtinfo.so.5: no version information 
>> available (required by bash)
>>     1984
>> **********************************************************************
>> File "src/sage/schemes/elliptic_curves/ell_rational_field.py", line 1388, 
>> in 
>> sage.schemes.elliptic_curves.ell_rational_field.EllipticCurve_rational_field.analytic_rank
>> Failed example:
>>     E.analytic_rank(algorithm='sympow')
>> Expected:
>>     2
>> Got:
>>     bash: /usr/local/sage/local/lib/libtinfo.so.5: no version information 
>> available (required by bash)
>>     2
>> **********************************************************************
>> File "src/sage/schemes/elliptic_curves/ell_rational_field.py", line 1394, 
>> in 
>> sage.schemes.elliptic_curves.ell_rational_field.EllipticCurve_rational_field.analytic_rank
>> Failed example:
>>     E.analytic_rank(algorithm='all')
>> Expected:
>>     2
>> Got:
>>     bash: /usr/local/sage/local/lib/libtinfo.so.5: no version information 
>> available (required by bash)
>>     2
>> ^CKilling test src/sage/rings/function_field/function_field.py
>> Killing test src/sage/schemes/elliptic_curves/ell_number_field.py
>> Killing test 
>> src/sage/combinat/root_system/non_symmetric_macdonald_polynomials.py
>> Killing test src/sage/schemes/elliptic_curves/ell_rational_field.py
>> Killing test src/sage/groups/perm_gps/permgroup_named.py
>> Killing test src/sage/combinat/similarity_class_type.py
>> Killing test src/sage/combinat/ncsf_qsym/ncsf.py
>> Killing test 
>> src/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py
>> ----------------------------------------------------------------------
>> Doctests interrupted: 0/3192 files tested
>> ----------------------------------------------------------------------
>> Total time for all tests: 18.5 seconds
>>     cpu time: 0.0 seconds
>>     cumulative wall time: 0.0 seconds
>> Makefile:108: recipe for target 'ptestlong' failed
>> make: *** [ptestlong] Error 128
>>
>> real    1m26.187s
>> user    1m55.516s
>> sys    0m16.344s
>>
>> Thinking that this was possibly a problem with my library system, I filed 
>> the #799910 bug report to Debian, which got me an answer :
>>
>> > Package: libtinfo5
>> > Version: 6.0+20150810
>> > Severity: normal
>> ...
>> > Since a recent upgrade, bash complains about this library lacking 
>> version
>> > information.
>> > 
>> > the following message is printed a *lot* during some bash scripts 
>> execution :
>> > 
>> > bash: /usr/local/sage/local/lib/libtinfo.so.5: no version information 
>> available
>> > (required by bash)
>>
>> Possibly LD_LIBRARY_PATH is set in user's environment, causing bash
>> to become confused about which library to use.  I seem to recall that
>> a Debian guideline for packaging says to not use the rpath feature
>> (which would prevent this problem).  It is not a bug in ncurses, but
>> a problem with the user's environment or custom configuration.
>>
>> As it is, there are a few possible solutions (by the user):
>>
>>         + repair the environment (i.e., dropping
>>           /usr/local/sage/local/lib from LD_LIBRARY_PATH)
>>
>>         + remove the conflicting library from /usr/local/sage/local/lib
>>
>> Then a second :
>>
>> [ ... Snipping the previous messages ]
>> This is a local version of libtinfo.so.5, the one shipped in the
>> libtinfo5 package does have this version information.  Move your locally
>> installed ncurses libraries out of the way, or rebuild them passing
>> "--with-versioned-syms" to the configure script.
>>
>> I checked that this happens also when I force installing Sage's GCC (
>> SAGE_INSTALL_GCC=YES) in a scratch installation (i. e. after make 
>> distclean). I also checked that this happens on another Debian 
>> installation (somewhat different).
>>
>> So a couple of questions :
>>
>>
>>    1. Is this specific to my installation(s) ?
>>    2. Whar should I do ?
>>    3. Should I file a Trac ticket ?
>>    
>>
>>  Sincerely yours,
>>
>> --
>> Emmanuel Charpentier
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to