On Sunday, April 29, 2018 at 12:22:18 AM UTC+1, Christelle Vincent wrote:
>
> Done! Thanks!
>
> On Saturday, April 28, 2018 at 6:45:31 PM UTC-4, Samuel Lelievre wrote:
>>
>> Congratulations for building SageMath!
>>
>> You can now rename /local/bin_bak, /local/share_bak and /local/lib_bak
>>
On Saturday, April 28, 2018 at 7:41:49 PM UTC-5, Erik Bray wrote:
>
> I just finished a full build from scratch on Ubuntu 18.04 and it went
> fine. This was of 8.2.rc4.
>
> I don't recall off the top of my head whether anything changed between
> rc1 and rc4 that might have effected this, but
I just finished a full build from scratch on Ubuntu 18.04 and it went
fine. This was of 8.2.rc4.
I don't recall off the top of my head whether anything changed between
rc1 and rc4 that might have effected this, but you might try bumping a
rc4 just in case.
On Sun, Apr 29, 2018 at 1:03 AM, Erik
Done! Thanks!
On Saturday, April 28, 2018 at 6:45:31 PM UTC-4, Samuel Lelievre wrote:
>
> Congratulations for building SageMath!
>
> You can now rename /local/bin_bak, /local/share_bak and /local/lib_bak
> back to their original names. (And just temporarily rename them to the
> _bak version when
Thanks for the report--I have yet to try doing anything on Ubuntu
18.04, but I'll try it now and see if I get the same.
On Sat, Apr 28, 2018 at 5:47 AM, Nathan Dunfield wrote:
> Dear Sage folks,
>
> I tried building Sage 8.2rc1 on a clean Docker container running the newly
Congratulations for building SageMath!
You can now rename /local/bin_bak, /local/share_bak and /local/lib_bak
back to their original names. (And just temporarily rename them to the
_bak version when you need to build SageMath.
Happy SageMath usage and development!
2018-04-29 0:20 GMT+02:00
Thanks!
I actually went ahead and tried and built 8.1 and that worked!! So I think
that whatever you suggested before with exporting the path and renaming
local/bin, local/share and local/lib worked!
Thank you so much to everyone who helped with this, I really appreciate
finally being able to
Try 8.2.rc2 with https://trac.sagemath.org/ticket/25118
on top of it. This would not build gcc, but rather use Xcode's C compiler.
In his infinite wisdom the release manager decided to wait till 8.3 with it...
--
You received this message because you are subscribed to the Google Groups
I had not typed that. In general if something was not explicitly said then
I didn't do it, because while I can develop for Sage I'm not good enough
with the guts of a computer to know to do anything extra.
Anyway, after make distclean, I couldn't build gcc-7.2.0, which at the very
beginning
A few comments.
1. Giving someone a surprising or undesirable result because
a GCD computation is considered expensive sounds like a really
bad idea. (I believe I'm overstating the situation here, but that's
sort of what it sounds like.
2. (Judging from Macsyma/Maxima) it is ok, workable, and
Hi,
I have code on https://github.com/okazymyrov/sbox. It works fine with sage
7.1 . However, in SageMath 8.1 I get warnings like:
/Users/okazymyrov/bin/sage8.1/local/lib/python2.7/site-packages/sage/misc/
cython.py:313: DeprecationWarning: the Sage-specific Cython pragma '#clang'
is
after these changes in /usr/local, did you do
make distclean
without it, stuff in /usr/local that you moved away could be still linked to,
and could cause all sorts of errors.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
12 matches
Mail list logo