[sage-devel] Re: python3 status report (mi-april of last python2 year)
Sorry: "Should we do this?" should be "Should I do this?"
Martin
Am Samstag, 20. April 2019 06:31:20 UTC+2 schrieb Martin R:
>
> In my opinion, `Set` should not be used in library code. It is slow,
> unnecessary, and can hide subtle bugs when the underlying object is not
> hashable. (https://trac.sagemath.org/ticket/23324)
>
> For the concrete issue at hand, the use of `Set` could be easily removed
> in all methods except `SetPartition.base_set` and
> `SetPartitions_set.base_set`, because in these two cases calling code might
> expect a `Set`.
>
> Should we do this?
>
> I should add that this (probably) doesn't solve the underlying issue, and
> moreover may affect a lot of doctests, because it might change the ordering
> of the parts returned in _repr_.
>
> Martin
>
>
> Am Samstag, 20. April 2019 04:14:53 UTC+2 schrieb Nils Bruin:
>>
>> On Friday, April 19, 2019 at 5:25:13 PM UTC-7, John H Palmieri wrote:
>>>
>>> What does
>>>
>>> sage: C
>>> Set partitions of {'a', 'c', 'b'}
>>>
>>>
>>> reveal? Is it helpful, or can it be omitted?
>>>
>>> Adding to that: perhaps it reveals something for the documentation
>> reader. But in that case the output doesn't need to be tested. The test
>> comes later by showing that further methods on C have the desired effect.
>> In that case,
>>
>> sage: C # random print order
>> Set partitions of {'a', 'c', 'b'}
>> sage: C.cardinality()
>> 5
>>
>> does the trick AND we keep the output displayed for documentation
>> purposes.
>>
>>
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: python3 status report (mi-april of last python2 year)
In my opinion, `Set` should not be used in library code. It is slow,
unnecessary, and can hide subtle bugs when the underlying object is not
hashable. (https://trac.sagemath.org/ticket/23324)
For the concrete issue at hand, the use of `Set` could be easily removed in
all methods except `SetPartition.base_set` and
`SetPartitions_set.base_set`, because in these two cases calling code might
expect a `Set`.
Should we do this?
I should add that this (probably) doesn't solve the underlying issue, and
moreover may affect a lot of doctests, because it might change the ordering
of the parts returned in _repr_.
Martin
Am Samstag, 20. April 2019 04:14:53 UTC+2 schrieb Nils Bruin:
>
> On Friday, April 19, 2019 at 5:25:13 PM UTC-7, John H Palmieri wrote:
>>
>> What does
>>
>> sage: C
>> Set partitions of {'a', 'c', 'b'}
>>
>>
>> reveal? Is it helpful, or can it be omitted?
>>
>> Adding to that: perhaps it reveals something for the documentation
> reader. But in that case the output doesn't need to be tested. The test
> comes later by showing that further methods on C have the desired effect.
> In that case,
>
> sage: C # random print order
> Set partitions of {'a', 'c', 'b'}
> sage: C.cardinality()
> 5
>
> does the trick AND we keep the output displayed for documentation purposes.
>
>
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] problem compiling the latest development version
Hi Dima, I reinstalled xcode and now sage compiles again. Thanks for your help! Anne On Friday, April 19, 2019 at 12:09:35 PM UTC-7, Dima Pasechnik wrote: > > On Fri, Apr 19, 2019 at 7:20 PM Anne Schilling > > wrote: > > > > Thank you all for your suggestions! Dima's suggestion did not seem to > fix my problem. > > I did pull from develop again and now the elliptic problem is gone. But > the pillow problem > > is still there: > > do you actually have /usr/lib/system/libsystem_darwin.dylib on your > system? > I suspect it must be present, or else it > > > > [sagelib-8.8.beta3] byte-compiling > /Applications/sage/local/lib/python2.7/site-packages/sage_setup/optional_extension.py > > to optional_extension.pyc > > [sagelib-8.8.beta3] byte-compiling > /Applications/sage/local/lib/python2.7/site-packages/sage_setup/util.py to > util.pyc > > [sagelib-8.8.beta3] running install_egg_info > > [sagelib-8.8.beta3] Writing > /Applications/sage/local/lib/python2.7/site-packages/sage-8.8.beta3-py2.7.egg-info > > > > [sagelib-8.8.beta3] Cleaning up stale installed files > > [sagelib-8.8.beta3] - cleaning > /Applications/sage/local/lib/python2.7/site-packages > > [sagelib-8.8.beta3] - cleaning build/lib.macosx-10.9-x86_64-2.7 > > [sagelib-8.8.beta3] Finished cleaning, time: 0.22 seconds. > > [sagelib-8.8.beta3] if [ "$UNAME" = "CYGWIN" ]; then > \ > > [sagelib-8.8.beta3] sage-rebase.sh "$SAGE_LOCAL" 2>/dev/null; > \ > > [sagelib-8.8.beta3] fi > > [sagelib-8.8.beta3] > > [sagelib-8.8.beta3] real8m42.417s > > [sagelib-8.8.beta3] user31m53.513s > > [sagelib-8.8.beta3] sys0m58.010s > > make[2]: *** [all-start] Error 2 > > > > real8m42.712s > > user32m26.636s > > sys1m9.140s > > *** > > Error building Sage. > > > > The following package(s) may have failed to build (not necessarily > > during this run of 'make all-start'): > > > > * package: pillow-5.3.0.p0 > > log file: /Applications/sage/logs/pkgs/pillow-5.3.0.p0.log > > build directory: > /Applications/sage/local/var/tmp/sage/build/pillow-5.3.0.p0 > > > > The build directory may contain configuration files and other > potentially > > helpful information. WARNING: if you now run 'make' again, the build > > directory will, by default, be deleted. Set the environment variable > > SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. > > > > make[1]: *** [all-start] Error 1 > > make: *** [all] Error 2 > > > > https://www.math.ucdavis.edu/~anne/pillow-5.3.0.p0.log > What is the output of > > otool -L /usr/lib/libSystem.B.dylib > > On my OSX 10.14 system it includes /usr/lib/system/libsystem_darwin.dylib > > (libSystem.B.dylib is a very important system library...) > > Is /usr/lib/system/libsystem_darwin.dylib present on your system? > If not, then you might need to reinstall your OS, or find this file > somewhere... > > If yes, then it's not found by your ld, so you need to fix this somehow. > Probably something like > > sudo update_dyld_shared_cache > > HTH > Dima > > > Dima > > > > > Best, > > > > Anne > > > > On Friday, April 19, 2019 at 9:26:34 AM UTC-7, E. Madison Bray wrote: > >> > >> On Fri, Apr 19, 2019 at 8:30 AM Dima Pasechnik > wrote: > >> > > >> > On Fri, Apr 19, 2019 at 7:33 AM Anne Schilling > >> > wrote: > >> > > > >> > > This was after I ran 'make distclean'. You can view the logs here: > >> > > > >> > > https://www.math.ucdavis.edu/~anne/elliptic_curves-0.8.p0.log > >> > > >> > ImportError: No module named _sqlite3 > >> > > >> > This look like a silent failure in building sqlite3, which is a > >> > standard package. > >> > >> I guess, besides the toolchain issue, it looks like having a working > >> _sqlite3 module is a dependency of the elliptic_curves package > >> install. > >> > >> In light of https://trac.sagemath.org/ticket/26899 we discussed at > >> some point adding zlib to the list of extension modules that Python > >> absolutely must build successfully. But it seems that never got done. > >> I've opened a ticket for this and mentioned adding _sqlite3 to the > >> list as well: https://trac.sagemath.org/ticket/27705 > >> > >> This would not immediately solve the problem Anne had but at least > >> the root of the problem would be caught earlier. Then, hopefully, the > >> solution Dima mentioned should work. This seems to be more-or-less > >> the same problem as with zlib, and XCode no longer including standard > >> headers in /usr/include by default. > >> > >> > >> > >> > > https://www.math.ucdavis.edu/~anne/pillow-5.3.0.p0.log > >> > this looks like a problem with your toolchain > >> > > >> > ld: file not found: /usr/lib/system/libsystem_darwin.dylib for > >> > architecture x86_64 > >> > > >> > discussed e.g. on > >> > https://github.com/Homebrew/homebrew-php/issues/4590 > >> > this and other
Re: [sage-devel] Re: building doc: u'\xe9' in position 19: ordinal not in range(128)
Indeed, this is due to french settings and the offending line is a
good news stated in a funny mix of english and french: "build réussi".
Changing the offending line to Volker's suggestion does work.
I opened ticket [#27706] for that purpose but I am not sure
about the Python3 compatible way to implement it.
[#27706] https://trac.sagemath.org/ticket/27706
Thank you!
Vincent
Le 19/04/2019 à 18:14, Volker Braun a écrit :
Can you change the offending line to
self._stream.write(line.encode('utf-8'))
On Friday, April 19, 2019 at 4:09:00 PM UTC+2, vdelecroix wrote:
Dear all,
I freshly cloned and compile SageMath. Everything went fine until the
documentation where each time sphinx tries to write something I see
[dochtml] Traceback (most recent call last):
[dochtml] File
"/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
line 287, in write
[dochtml] self._write(str)
[dochtml] File
"/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
line 261, in _write
[dochtml] self._log_line(line)
[dochtml] File
"/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
line 227, in _log_line
[dochtml] self._stream.write(line)
[dochtml] UnicodeEncodeError: 'ascii' codec can't encode character
u'\xe9' in position 19: ordinal not in range(128)
[dochtml] Traceback (most recent call last):
[dochtml] File
"/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
line 287, in write
[dochtml] self._write(str)
[dochtml] File
"/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
line 261, in _write
[dochtml] self._log_line(line)
[dochtml] File
"/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
line 227, in _log_line
[dochtml] self._stream.write(line)
[dochtml] UnicodeEncodeError: 'ascii' codec can't encode character
u'\xe9' in position 19: ordinal not in range(128)
[dochtml] Traceback (most recent call last):
[dochtml] File
"/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
line 287, in write
[dochtml] self._write(str)
[dochtml] File
"/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
line 261, in _write
[dochtml] self._log_line(line)
[dochtml] File
"/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
line 227, in _log_line
[dochtml] self._stream.write(line)
[dochtml] UnicodeEncodeError: 'ascii' codec can't encode character
u'\xe9' in position 19: ordinal not in range(128)
There is a tone of them in the attached log but which is not very
helpful for debugging.
Any help is appreciated.
Vincent
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: python3 status report (mi-april of last python2 year)
On Friday, April 19, 2019 at 5:25:13 PM UTC-7, John H Palmieri wrote:
>
> What does
>
> sage: C
> Set partitions of {'a', 'c', 'b'}
>
>
> reveal? Is it helpful, or can it be omitted?
>
> Adding to that: perhaps it reveals something for the documentation reader.
But in that case the output doesn't need to be tested. The test comes later
by showing that further methods on C have the desired effect. In that case,
sage: C # random print order
Set partitions of {'a', 'c', 'b'}
sage: C.cardinality()
5
does the trick AND we keep the output displayed for documentation purposes.
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: python3 status report (mi-april of last python2 year)
What does
sage: C
Set partitions of {'a', 'c', 'b'}
reveal? Is it helpful, or can it be omitted? Maybe it's good enough to do
sage: C = SetPartitions(["a", "b", "c"])
sage: C.cardinality()
5
sage: sorted(C)
[{{'a'}, {'b'}, {'c'}},
{{'a'}, {'b', 'c'}},
{{'a', 'b'}, {'c'}},
{{'a', 'b', 'c'}},
{{'a', 'c'}, {'b'}}]
You should use your judgment about whether the doctest prints useful output
for a reader, for example. If it needs different cases for py2 and py3, is
it more helpful to print it or is it more confusing?
On Friday, April 19, 2019 at 4:10:28 PM UTC-7, Andrew wrote:
>
> What the accepted best practice for fixing the failing python3 doc-tests?
> For example, in `combinat/tutorial.py` I can fix one of the failing
> doc-tests with:
>
> sage: C = SetPartitions(["a", "b", "c"])
> sage: C #py2
> Set partitions of {'a', 'c', 'b'}
> sage: C #py3
> Set partitions of {'a', 'b', 'c'}
>
> but this does not address the underlying problem. At first sight this
> looks like an issue with `SetPartitions` and, indeed,
> `combinat/setpartition.py` has several failing doc-tests but as far as I
> can see this is actually an issue with `Set` even though `sets/set.py`
> passes all doc-tests. You can see this because
>
> Set(['a', 'b', 'c'])
>
> gives different output with each sage session, at least when `sage` is
> compiled with python3.
>
> On Monday, 15 April 2019 21:56:54 UTC+10, Frédéric Chapoton wrote:
>>
>> Hello,
>>
>> sage-with-python3 (now using python 3.7.3) has now *less than 100 files*
>> (94 precisely) with failing doctests, for a total of *324 failing
>> doctests*. Among these, 34 files have a single failing doctest.
>>
>> A detailed summary can be found here :
>> https://trac.sagemath.org/ticket/26212
>>
>> There remains many hard-to-fix issues. Please help if you can.
>>
>> * Matroid, dynamics and combinat people should care for their code. The
>> cluster code needs particular work.
>>
>> * We should also strive to make all tests pass in rings/
>>
>> * An expert is required on src/sage/misc/classcall_metaclass.pyx
>>
>> Frédéric
>>
>>
>>
>>
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: python3 status report (mi-april of last python2 year)
What the accepted best practice for fixing the failing python3 doc-tests?
For example, in `combinat/tutorial.py` I can fix one of the failing
doc-tests with:
sage: C = SetPartitions(["a", "b", "c"])
sage: C #py2
Set partitions of {'a', 'c', 'b'}
sage: C #py3
Set partitions of {'a', 'b', 'c'}
but this does not address the underlying problem. At first sight this looks
like an issue with `SetPartitions` and, indeed, `combinat/setpartition.py`
has several failing doc-tests but as far as I can see this is actually an
issue with `Set` even though `sets/set.py` passes all doc-tests. You can
see this because
Set(['a', 'b', 'c'])
gives different output with each sage session, at least when `sage` is
compiled with python3.
On Monday, 15 April 2019 21:56:54 UTC+10, Frédéric Chapoton wrote:
>
> Hello,
>
> sage-with-python3 (now using python 3.7.3) has now *less than 100 files*
> (94 precisely) with failing doctests, for a total of *324 failing
> doctests*. Among these, 34 files have a single failing doctest.
>
> A detailed summary can be found here :
> https://trac.sagemath.org/ticket/26212
>
> There remains many hard-to-fix issues. Please help if you can.
>
> * Matroid, dynamics and combinat people should care for their code. The
> cluster code needs particular work.
>
> * We should also strive to make all tests pass in rings/
>
> * An expert is required on src/sage/misc/classcall_metaclass.pyx
>
> Frédéric
>
>
>
>
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] problem compiling the latest development version
On Fri, Apr 19, 2019 at 9:09 PM Dima Pasechnik wrote: > > On Fri, Apr 19, 2019 at 7:20 PM Anne Schilling > wrote: > > > > Thank you all for your suggestions! Dima's suggestion did not seem to fix > > my problem. > > I did pull from develop again and now the elliptic problem is gone. But the > > pillow problem > > is still there: > > do you actually have /usr/lib/system/libsystem_darwin.dylib on your system? > I suspect it must be present, or else it > > > > [sagelib-8.8.beta3] byte-compiling > > /Applications/sage/local/lib/python2.7/site-packages/sage_setup/optional_extension.py > > to optional_extension.pyc > > [sagelib-8.8.beta3] byte-compiling > > /Applications/sage/local/lib/python2.7/site-packages/sage_setup/util.py to > > util.pyc > > [sagelib-8.8.beta3] running install_egg_info > > [sagelib-8.8.beta3] Writing > > /Applications/sage/local/lib/python2.7/site-packages/sage-8.8.beta3-py2.7.egg-info > > [sagelib-8.8.beta3] Cleaning up stale installed files > > [sagelib-8.8.beta3] - cleaning > > /Applications/sage/local/lib/python2.7/site-packages > > [sagelib-8.8.beta3] - cleaning build/lib.macosx-10.9-x86_64-2.7 > > [sagelib-8.8.beta3] Finished cleaning, time: 0.22 seconds. > > [sagelib-8.8.beta3] if [ "$UNAME" = "CYGWIN" ]; then > > \ > > [sagelib-8.8.beta3] sage-rebase.sh "$SAGE_LOCAL" 2>/dev/null; > > \ > > [sagelib-8.8.beta3] fi > > [sagelib-8.8.beta3] > > [sagelib-8.8.beta3] real8m42.417s > > [sagelib-8.8.beta3] user31m53.513s > > [sagelib-8.8.beta3] sys0m58.010s > > make[2]: *** [all-start] Error 2 > > > > real8m42.712s > > user32m26.636s > > sys1m9.140s > > *** > > Error building Sage. > > > > The following package(s) may have failed to build (not necessarily > > during this run of 'make all-start'): > > > > * package: pillow-5.3.0.p0 > > log file: /Applications/sage/logs/pkgs/pillow-5.3.0.p0.log > > build directory: > > /Applications/sage/local/var/tmp/sage/build/pillow-5.3.0.p0 > > > > The build directory may contain configuration files and other potentially > > helpful information. WARNING: if you now run 'make' again, the build > > directory will, by default, be deleted. Set the environment variable > > SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. > > > > make[1]: *** [all-start] Error 1 > > make: *** [all] Error 2 > > > > https://www.math.ucdavis.edu/~anne/pillow-5.3.0.p0.log > What is the output of > > otool -L /usr/lib/libSystem.B.dylib > > On my OSX 10.14 system it includes /usr/lib/system/libsystem_darwin.dylib > > (libSystem.B.dylib is a very important system library...) > > Is /usr/lib/system/libsystem_darwin.dylib present on your system? > If not, then you might need to reinstall your OS, or find this file > somewhere... > > If yes, then it's not found by your ld, so you need to fix this somehow. > Probably something like > > sudo update_dyld_shared_cache by the way, your log file is huge, 167Mb, it does contain output of "just" 9 tries to build the package, so 15Mb per try, whereas on my OSX 10.4 this log is 100K. You have a hell of a lot of warnings there (I'd read each of them as "upgrade your OS" :-)) > > HTH > Dima > > > Dima > > > > > Best, > > > > Anne > > > > On Friday, April 19, 2019 at 9:26:34 AM UTC-7, E. Madison Bray wrote: > >> > >> On Fri, Apr 19, 2019 at 8:30 AM Dima Pasechnik wrote: > >> > > >> > On Fri, Apr 19, 2019 at 7:33 AM Anne Schilling > >> > wrote: > >> > > > >> > > This was after I ran 'make distclean'. You can view the logs here: > >> > > > >> > > https://www.math.ucdavis.edu/~anne/elliptic_curves-0.8.p0.log > >> > > >> > ImportError: No module named _sqlite3 > >> > > >> > This look like a silent failure in building sqlite3, which is a > >> > standard package. > >> > >> I guess, besides the toolchain issue, it looks like having a working > >> _sqlite3 module is a dependency of the elliptic_curves package > >> install. > >> > >> In light of https://trac.sagemath.org/ticket/26899 we discussed at > >> some point adding zlib to the list of extension modules that Python > >> absolutely must build successfully. But it seems that never got done. > >> I've opened a ticket for this and mentioned adding _sqlite3 to the > >> list as well: https://trac.sagemath.org/ticket/27705 > >> > >> This would not immediately solve the problem Anne had but at least > >> the root of the problem would be caught earlier. Then, hopefully, the > >> solution Dima mentioned should work. This seems to be more-or-less > >> the same problem as with zlib, and XCode no longer including standard > >> headers in /usr/include by default. > >> > >> > >> > >> > > https://www.math.ucdavis.edu/~anne/pillow-5.3.0.p0.log > >> > this looks like a problem with your toolchain > >> > > >> > ld: file not found: /usr/lib/system/libsystem_darwin.dylib for > >> > architecture x86_64 > >> > > >> > discussed e.g. on > >> >
Re: [sage-devel] problem compiling the latest development version
On Fri, Apr 19, 2019 at 7:20 PM Anne Schilling wrote: > > Thank you all for your suggestions! Dima's suggestion did not seem to fix my > problem. > I did pull from develop again and now the elliptic problem is gone. But the > pillow problem > is still there: do you actually have /usr/lib/system/libsystem_darwin.dylib on your system? I suspect it must be present, or else it > > [sagelib-8.8.beta3] byte-compiling > /Applications/sage/local/lib/python2.7/site-packages/sage_setup/optional_extension.py > to optional_extension.pyc > [sagelib-8.8.beta3] byte-compiling > /Applications/sage/local/lib/python2.7/site-packages/sage_setup/util.py to > util.pyc > [sagelib-8.8.beta3] running install_egg_info > [sagelib-8.8.beta3] Writing > /Applications/sage/local/lib/python2.7/site-packages/sage-8.8.beta3-py2.7.egg-info > [sagelib-8.8.beta3] Cleaning up stale installed files > [sagelib-8.8.beta3] - cleaning > /Applications/sage/local/lib/python2.7/site-packages > [sagelib-8.8.beta3] - cleaning build/lib.macosx-10.9-x86_64-2.7 > [sagelib-8.8.beta3] Finished cleaning, time: 0.22 seconds. > [sagelib-8.8.beta3] if [ "$UNAME" = "CYGWIN" ]; then \ > [sagelib-8.8.beta3] sage-rebase.sh "$SAGE_LOCAL" 2>/dev/null; >\ > [sagelib-8.8.beta3] fi > [sagelib-8.8.beta3] > [sagelib-8.8.beta3] real8m42.417s > [sagelib-8.8.beta3] user31m53.513s > [sagelib-8.8.beta3] sys0m58.010s > make[2]: *** [all-start] Error 2 > > real8m42.712s > user32m26.636s > sys1m9.140s > *** > Error building Sage. > > The following package(s) may have failed to build (not necessarily > during this run of 'make all-start'): > > * package: pillow-5.3.0.p0 > log file: /Applications/sage/logs/pkgs/pillow-5.3.0.p0.log > build directory: /Applications/sage/local/var/tmp/sage/build/pillow-5.3.0.p0 > > The build directory may contain configuration files and other potentially > helpful information. WARNING: if you now run 'make' again, the build > directory will, by default, be deleted. Set the environment variable > SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. > > make[1]: *** [all-start] Error 1 > make: *** [all] Error 2 > > https://www.math.ucdavis.edu/~anne/pillow-5.3.0.p0.log What is the output of otool -L /usr/lib/libSystem.B.dylib On my OSX 10.14 system it includes /usr/lib/system/libsystem_darwin.dylib (libSystem.B.dylib is a very important system library...) Is /usr/lib/system/libsystem_darwin.dylib present on your system? If not, then you might need to reinstall your OS, or find this file somewhere... If yes, then it's not found by your ld, so you need to fix this somehow. Probably something like sudo update_dyld_shared_cache HTH Dima Dima > > Best, > > Anne > > On Friday, April 19, 2019 at 9:26:34 AM UTC-7, E. Madison Bray wrote: >> >> On Fri, Apr 19, 2019 at 8:30 AM Dima Pasechnik wrote: >> > >> > On Fri, Apr 19, 2019 at 7:33 AM Anne Schilling >> > wrote: >> > > >> > > This was after I ran 'make distclean'. You can view the logs here: >> > > >> > > https://www.math.ucdavis.edu/~anne/elliptic_curves-0.8.p0.log >> > >> > ImportError: No module named _sqlite3 >> > >> > This look like a silent failure in building sqlite3, which is a >> > standard package. >> >> I guess, besides the toolchain issue, it looks like having a working >> _sqlite3 module is a dependency of the elliptic_curves package >> install. >> >> In light of https://trac.sagemath.org/ticket/26899 we discussed at >> some point adding zlib to the list of extension modules that Python >> absolutely must build successfully. But it seems that never got done. >> I've opened a ticket for this and mentioned adding _sqlite3 to the >> list as well: https://trac.sagemath.org/ticket/27705 >> >> This would not immediately solve the problem Anne had but at least >> the root of the problem would be caught earlier. Then, hopefully, the >> solution Dima mentioned should work. This seems to be more-or-less >> the same problem as with zlib, and XCode no longer including standard >> headers in /usr/include by default. >> >> >> >> > > https://www.math.ucdavis.edu/~anne/pillow-5.3.0.p0.log >> > this looks like a problem with your toolchain >> > >> > ld: file not found: /usr/lib/system/libsystem_darwin.dylib for >> > architecture x86_64 >> > >> > discussed e.g. on >> > https://github.com/Homebrew/homebrew-php/issues/4590 >> > this and other similar places suggest to do >> > >> > sudo xcode-select -s /Library/Developer/CommandLineTools >> > >> > HTH >> > Dima >> > >> > >> > > >> > > Anne >> > > >> > > On Thursday, April 18, 2019 at 10:07:28 PM UTC-7, Dima Pasechnik wrote: >> > >> >> > >> How about posting logs of packages that failed to build? >> > >> >> > >> It would also be great to know whether it was a build from scratch. >> > >> >> > >> On Fri, 19 Apr 2019 07:03 Anne Schilling, wrote: >> > >>> >> > >>> Hi! >> > >>> >> > >>> I have trouble compiling
Re: [sage-devel] problem compiling the latest development version
Thank you all for your suggestions! Dima's suggestion did not seem to fix my problem. I did pull from develop again and now the elliptic problem is gone. But the pillow problem is still there: [sagelib-8.8.beta3] byte-compiling /Applications/sage/local/lib/python2.7/site-packages/sage_setup/optional_extension.py to optional_extension.pyc [sagelib-8.8.beta3] byte-compiling /Applications/sage/local/lib/python2.7/site-packages/sage_setup/util.py to util.pyc [sagelib-8.8.beta3] running install_egg_info [sagelib-8.8.beta3] Writing /Applications/sage/local/lib/python2.7/site-packages/sage-8.8.beta3-py2.7.egg-info [sagelib-8.8.beta3] Cleaning up stale installed files [sagelib-8.8.beta3] - cleaning /Applications/sage/local/lib/python2.7/site-packages [sagelib-8.8.beta3] - cleaning build/lib.macosx-10.9-x86_64-2.7 [sagelib-8.8.beta3] Finished cleaning, time: 0.22 seconds. [sagelib-8.8.beta3] if [ "$UNAME" = "CYGWIN" ]; then \ [sagelib-8.8.beta3] sage-rebase.sh "$SAGE_LOCAL" 2>/dev/null;\ [sagelib-8.8.beta3] fi [sagelib-8.8.beta3] [sagelib-8.8.beta3] real8m42.417s [sagelib-8.8.beta3] user31m53.513s [sagelib-8.8.beta3] sys0m58.010s make[2]: *** [all-start] Error 2 real8m42.712s user32m26.636s sys1m9.140s *** Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all-start'): * package: pillow-5.3.0.p0 log file: /Applications/sage/logs/pkgs/pillow-5.3.0.p0.log build directory: /Applications/sage/local/var/tmp/sage/build/pillow-5.3.0.p0 The build directory may contain configuration files and other potentially helpful information. WARNING: if you now run 'make' again, the build directory will, by default, be deleted. Set the environment variable SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. make[1]: *** [all-start] Error 1 make: *** [all] Error 2 https://www.math.ucdavis.edu/~anne/pillow-5.3.0.p0.log Best, Anne On Friday, April 19, 2019 at 9:26:34 AM UTC-7, E. Madison Bray wrote: > > On Fri, Apr 19, 2019 at 8:30 AM Dima Pasechnik > wrote: > > > > On Fri, Apr 19, 2019 at 7:33 AM Anne Schilling > > > wrote: > > > > > > This was after I ran 'make distclean'. You can view the logs here: > > > > > > https://www.math.ucdavis.edu/~anne/elliptic_curves-0.8.p0.log > > > > ImportError: No module named _sqlite3 > > > > This look like a silent failure in building sqlite3, which is a > > standard package. > > I guess, besides the toolchain issue, it looks like having a working > _sqlite3 module is a dependency of the elliptic_curves package > install. > > In light of https://trac.sagemath.org/ticket/26899 we discussed at > some point adding zlib to the list of extension modules that Python > absolutely must build successfully. But it seems that never got done. > I've opened a ticket for this and mentioned adding _sqlite3 to the > list as well: https://trac.sagemath.org/ticket/27705 > > This would not immediately solve the problem Anne had but at least > the root of the problem would be caught earlier. Then, hopefully, the > solution Dima mentioned should work. This seems to be more-or-less > the same problem as with zlib, and XCode no longer including standard > headers in /usr/include by default. > > > > > > https://www.math.ucdavis.edu/~anne/pillow-5.3.0.p0.log > > this looks like a problem with your toolchain > > > > ld: file not found: /usr/lib/system/libsystem_darwin.dylib for > > architecture x86_64 > > > > discussed e.g. on > > https://github.com/Homebrew/homebrew-php/issues/4590 > > this and other similar places suggest to do > > > > sudo xcode-select -s /Library/Developer/CommandLineTools > > > > HTH > > Dima > > > > > > > > > > Anne > > > > > > On Thursday, April 18, 2019 at 10:07:28 PM UTC-7, Dima Pasechnik > wrote: > > >> > > >> How about posting logs of packages that failed to build? > > >> > > >> It would also be great to know whether it was a build from scratch. > > >> > > >> On Fri, 19 Apr 2019 07:03 Anne Schilling, > wrote: > > >>> > > >>> Hi! > > >>> > > >>> I have trouble compiling the latest development version of Sage on > MacOS 10.12.6: > > >>> > > >>> al/share/icons/hicolor/64x64/mimetypes > > >>> [giac-1.5.0.37.p1] mkdir > /Applications/sage/local/var/tmp/sage/build/giac-1.5.0.37.p1/inst/Applications/sage/local/share/icons/hicolor/32x32/mimetypes > > > > >>> [giac-1.5.0.37.p1] mkdir > /Applications/sage/local/var/tmp/sage/build/giac-1.5.0.37.p1/inst/Applications/sage/local/share/icons/hicolor/16x16/mimetypes > > > > >>> [giac-1.5.0.37.p1] > > >>> [giac-1.5.0.37.p1] real7m58.316s > > >>> [giac-1.5.0.37.p1] user24m11.636s > > >>> [giac-1.5.0.37.p1] sys0m54.736s > > >>> [giac-1.5.0.37.p1] Copying package files from temporary location > /Applications/sage/local/var/tmp/sage/build/giac-1.5.0.37.p1/inst to
Re: [sage-devel] problem compiling the latest development version
On Fri, Apr 19, 2019 at 8:30 AM Dima Pasechnik wrote: > > On Fri, Apr 19, 2019 at 7:33 AM Anne Schilling > wrote: > > > > This was after I ran 'make distclean'. You can view the logs here: > > > > https://www.math.ucdavis.edu/~anne/elliptic_curves-0.8.p0.log > > ImportError: No module named _sqlite3 > > This look like a silent failure in building sqlite3, which is a > standard package. I guess, besides the toolchain issue, it looks like having a working _sqlite3 module is a dependency of the elliptic_curves package install. In light of https://trac.sagemath.org/ticket/26899 we discussed at some point adding zlib to the list of extension modules that Python absolutely must build successfully. But it seems that never got done. I've opened a ticket for this and mentioned adding _sqlite3 to the list as well: https://trac.sagemath.org/ticket/27705 This would not immediately solve the problem Anne had but at least the root of the problem would be caught earlier. Then, hopefully, the solution Dima mentioned should work. This seems to be more-or-less the same problem as with zlib, and XCode no longer including standard headers in /usr/include by default. > > https://www.math.ucdavis.edu/~anne/pillow-5.3.0.p0.log > this looks like a problem with your toolchain > > ld: file not found: /usr/lib/system/libsystem_darwin.dylib for > architecture x86_64 > > discussed e.g. on > https://github.com/Homebrew/homebrew-php/issues/4590 > this and other similar places suggest to do > > sudo xcode-select -s /Library/Developer/CommandLineTools > > HTH > Dima > > > > > > Anne > > > > On Thursday, April 18, 2019 at 10:07:28 PM UTC-7, Dima Pasechnik wrote: > >> > >> How about posting logs of packages that failed to build? > >> > >> It would also be great to know whether it was a build from scratch. > >> > >> On Fri, 19 Apr 2019 07:03 Anne Schilling, wrote: > >>> > >>> Hi! > >>> > >>> I have trouble compiling the latest development version of Sage on MacOS > >>> 10.12.6: > >>> > >>> al/share/icons/hicolor/64x64/mimetypes > >>> [giac-1.5.0.37.p1] mkdir > >>> /Applications/sage/local/var/tmp/sage/build/giac-1.5.0.37.p1/inst/Applications/sage/local/share/icons/hicolor/32x32/mimetypes > >>> [giac-1.5.0.37.p1] mkdir > >>> /Applications/sage/local/var/tmp/sage/build/giac-1.5.0.37.p1/inst/Applications/sage/local/share/icons/hicolor/16x16/mimetypes > >>> [giac-1.5.0.37.p1] > >>> [giac-1.5.0.37.p1] real7m58.316s > >>> [giac-1.5.0.37.p1] user24m11.636s > >>> [giac-1.5.0.37.p1] sys0m54.736s > >>> [giac-1.5.0.37.p1] Copying package files from temporary location > >>> /Applications/sage/local/var/tmp/sage/build/giac-1.5.0.37.p1/inst to > >>> /Applications/sage/local > >>> [giac-1.5.0.37.p1] Successfully installed giac-1.5.0.37.p1 > >>> [giac-1.5.0.37.p1] Deleting temporary build directory > >>> [giac-1.5.0.37.p1] > >>> /Applications/sage/local/var/tmp/sage/build/giac-1.5.0.37.p1 > >>> [giac-1.5.0.37.p1] Finished installing giac-1.5.0.37.p1.spkg > >>> make[2]: *** [all-start] Error 2 > >>> > >>> real9m56.979s > >>> user33m21.853s > >>> sys2m8.502s > >>> *** > >>> Error building Sage. > >>> > >>> The following package(s) may have failed to build (not necessarily > >>> during this run of 'make all-start'): > >>> > >>> * package: elliptic_curves-0.8.p0 > >>> log file: /Applications/sage/logs/pkgs/elliptic_curves-0.8.p0.log > >>> build directory: > >>> /Applications/sage/local/var/tmp/sage/build/elliptic_curves-0.8.p0 > >>> > >>> * package: pillow-5.3.0.p0 > >>> log file: /Applications/sage/logs/pkgs/pillow-5.3.0.p0.log > >>> build directory: > >>> /Applications/sage/local/var/tmp/sage/build/pillow-5.3.0.p0 > >>> > >>> The build directory may contain configuration files and other potentially > >>> helpful information. WARNING: if you now run 'make' again, the build > >>> directory will, by default, be deleted. Set the environment variable > >>> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. > >>> > >>> make[1]: *** [all-start] Error 1 > >>> make: *** [all] Error 2 > >>> > >>> Does anyone know why? > >>> > >>> Thank you, > >>> > >>> Anne > >>> > >>> -- > >>> 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. > >>> To post to this group, send email to sage-...@googlegroups.com. > >>> Visit this group at https://groups.google.com/group/sage-devel. > >>> For more options, visit https://groups.google.com/d/optout. > > > > -- > > 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+unsubscr...@googlegroups.com. > > To post to this group, send email to sage-devel@googlegroups.com. > > Visit this group at
[sage-devel] Re: building doc: u'\xe9' in position 19: ordinal not in range(128)
Can you change the offending line to
self._stream.write(line.encode('utf-8'))
On Friday, April 19, 2019 at 4:09:00 PM UTC+2, vdelecroix wrote:
>
> Dear all,
>
> I freshly cloned and compile SageMath. Everything went fine until the
> documentation where each time sphinx tries to write something I see
>
> [dochtml] Traceback (most recent call last):
> [dochtml] File
> "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
>
>
> line 287, in write
> [dochtml] self._write(str)
> [dochtml] File
> "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
>
>
> line 261, in _write
> [dochtml] self._log_line(line)
> [dochtml] File
> "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
>
>
> line 227, in _log_line
> [dochtml] self._stream.write(line)
> [dochtml] UnicodeEncodeError: 'ascii' codec can't encode character
> u'\xe9' in position 19: ordinal not in range(128)
> [dochtml] Traceback (most recent call last):
> [dochtml] File
> "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
>
>
> line 287, in write
> [dochtml] self._write(str)
> [dochtml] File
> "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
>
>
> line 261, in _write
> [dochtml] self._log_line(line)
> [dochtml] File
> "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
>
>
> line 227, in _log_line
> [dochtml] self._stream.write(line)
> [dochtml] UnicodeEncodeError: 'ascii' codec can't encode character
> u'\xe9' in position 19: ordinal not in range(128)
> [dochtml] Traceback (most recent call last):
> [dochtml] File
> "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
>
>
> line 287, in write
> [dochtml] self._write(str)
> [dochtml] File
> "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
>
>
> line 261, in _write
> [dochtml] self._log_line(line)
> [dochtml] File
> "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py",
>
>
> line 227, in _log_line
> [dochtml] self._stream.write(line)
> [dochtml] UnicodeEncodeError: 'ascii' codec can't encode character
> u'\xe9' in position 19: ordinal not in range(128)
>
> There is a tone of them in the attached log but which is not very
> helpful for debugging.
>
> Any help is appreciated.
>
> Vincent
>
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] building doc: u'\xe9' in position 19: ordinal not in range(128)
French locale settings, no? (other reports of this error come from France, too, IIRC) On Fri, Apr 19, 2019 at 4:09 PM Vincent Delecroix <20100.delecr...@gmail.com> wrote: > > Dear all, > > I freshly cloned and compile SageMath. Everything went fine until the > documentation where each time sphinx tries to write something I see > > [dochtml] Traceback (most recent call last): > [dochtml] File > "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py", > line 287, in write > [dochtml] self._write(str) > [dochtml] File > "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py", > line 261, in _write > [dochtml] self._log_line(line) > [dochtml] File > "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py", > line 227, in _log_line > [dochtml] self._stream.write(line) > [dochtml] UnicodeEncodeError: 'ascii' codec can't encode character > u'\xe9' in position 19: ordinal not in range(128) > [dochtml] Traceback (most recent call last): > [dochtml] File > "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py", > line 287, in write > [dochtml] self._write(str) > [dochtml] File > "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py", > line 261, in _write > [dochtml] self._log_line(line) > [dochtml] File > "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py", > line 227, in _log_line > [dochtml] self._stream.write(line) > [dochtml] UnicodeEncodeError: 'ascii' codec can't encode character > u'\xe9' in position 19: ordinal not in range(128) > [dochtml] Traceback (most recent call last): > [dochtml] File > "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py", > line 287, in write > [dochtml] self._write(str) > [dochtml] File > "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py", > line 261, in _write > [dochtml] self._log_line(line) > [dochtml] File > "/opt/sage-clang/local/lib/python2.7/site-packages/sage_setup/docbuild/sphinxbuild.py", > line 227, in _log_line > [dochtml] self._stream.write(line) > [dochtml] UnicodeEncodeError: 'ascii' codec can't encode character > u'\xe9' in position 19: ordinal not in range(128) > > There is a tone of them in the attached log but which is not very > helpful for debugging. > > Any help is appreciated. > > Vincent > > -- > 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+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Automatic Differentiation - Taylor Arithmetics
Dear all, I was planning in doing a Cython implementation of Forward automatic differentiation and Taylor arithmetics as in https://press.princeton.edu/titles/9488.html to use to implement a library for Sage with rigorous quadrature and integration of ODE. I'm trying to understand which parent class could be the best for these objects for them to be compatible with Sage coercion model. What is the usual procedure, I read through http://doc.sagemath.org/html/en/reference/structure/sage/structure/element.html but I'm still confused. Best wishes Isaia -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] problem compiling the latest development version
On Fri, Apr 19, 2019 at 7:36 AM Anne Schilling wrote: > > > > On Thursday, April 18, 2019 at 10:09:20 PM UTC-7, François Bissey wrote: >> >> And it has to be 8.8.beta2 or lower not beta3 which is the latest. >> elliptic_curves has been >> bumped to 0.8.1 in beta3. > > > I did > > git pull > make distclean > make without knowing what git remote -v says, it's hard to tell where you pull from. It seems that the github mirror of trac is sometimes behind trac... Cheers, Dima > > in the develop branch. So I assumed it is the latest develop version. > > Anne > > -- > 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+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] problem compiling the latest development version
On Fri, Apr 19, 2019 at 7:33 AM Anne Schilling wrote: > > This was after I ran 'make distclean'. You can view the logs here: > > https://www.math.ucdavis.edu/~anne/elliptic_curves-0.8.p0.log ImportError: No module named _sqlite3 This look like a silent failure in building sqlite3, which is a standard package. > https://www.math.ucdavis.edu/~anne/pillow-5.3.0.p0.log this looks like a problem with your toolchain ld: file not found: /usr/lib/system/libsystem_darwin.dylib for architecture x86_64 discussed e.g. on https://github.com/Homebrew/homebrew-php/issues/4590 this and other similar places suggest to do sudo xcode-select -s /Library/Developer/CommandLineTools HTH Dima > > Anne > > On Thursday, April 18, 2019 at 10:07:28 PM UTC-7, Dima Pasechnik wrote: >> >> How about posting logs of packages that failed to build? >> >> It would also be great to know whether it was a build from scratch. >> >> On Fri, 19 Apr 2019 07:03 Anne Schilling, wrote: >>> >>> Hi! >>> >>> I have trouble compiling the latest development version of Sage on MacOS >>> 10.12.6: >>> >>> al/share/icons/hicolor/64x64/mimetypes >>> [giac-1.5.0.37.p1] mkdir >>> /Applications/sage/local/var/tmp/sage/build/giac-1.5.0.37.p1/inst/Applications/sage/local/share/icons/hicolor/32x32/mimetypes >>> [giac-1.5.0.37.p1] mkdir >>> /Applications/sage/local/var/tmp/sage/build/giac-1.5.0.37.p1/inst/Applications/sage/local/share/icons/hicolor/16x16/mimetypes >>> [giac-1.5.0.37.p1] >>> [giac-1.5.0.37.p1] real7m58.316s >>> [giac-1.5.0.37.p1] user24m11.636s >>> [giac-1.5.0.37.p1] sys0m54.736s >>> [giac-1.5.0.37.p1] Copying package files from temporary location >>> /Applications/sage/local/var/tmp/sage/build/giac-1.5.0.37.p1/inst to >>> /Applications/sage/local >>> [giac-1.5.0.37.p1] Successfully installed giac-1.5.0.37.p1 >>> [giac-1.5.0.37.p1] Deleting temporary build directory >>> [giac-1.5.0.37.p1] >>> /Applications/sage/local/var/tmp/sage/build/giac-1.5.0.37.p1 >>> [giac-1.5.0.37.p1] Finished installing giac-1.5.0.37.p1.spkg >>> make[2]: *** [all-start] Error 2 >>> >>> real9m56.979s >>> user33m21.853s >>> sys2m8.502s >>> *** >>> Error building Sage. >>> >>> The following package(s) may have failed to build (not necessarily >>> during this run of 'make all-start'): >>> >>> * package: elliptic_curves-0.8.p0 >>> log file: /Applications/sage/logs/pkgs/elliptic_curves-0.8.p0.log >>> build directory: >>> /Applications/sage/local/var/tmp/sage/build/elliptic_curves-0.8.p0 >>> >>> * package: pillow-5.3.0.p0 >>> log file: /Applications/sage/logs/pkgs/pillow-5.3.0.p0.log >>> build directory: >>> /Applications/sage/local/var/tmp/sage/build/pillow-5.3.0.p0 >>> >>> The build directory may contain configuration files and other potentially >>> helpful information. WARNING: if you now run 'make' again, the build >>> directory will, by default, be deleted. Set the environment variable >>> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. >>> >>> make[1]: *** [all-start] Error 1 >>> make: *** [all] Error 2 >>> >>> Does anyone know why? >>> >>> Thank you, >>> >>> Anne >>> >>> -- >>> 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. >>> To post to this group, send email to sage-...@googlegroups.com. >>> Visit this group at https://groups.google.com/group/sage-devel. >>> For more options, visit https://groups.google.com/d/optout. > > -- > 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+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
