On 2018-04-29 16:54, Christelle Vincent wrote:
Doctests interrupted: 2203/3630 files tested
You didn't accidentally press CTRL-C, did you?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails
On Tuesday, May 1, 2018 at 10:59:55 AM UTC+1, Dima Pasechnik wrote:
>
>
>
> On Sunday, April 29, 2018 at 3:54:08 PM UTC+1, Christelle Vincent wrote:
>>
>> Well, I don't know if you want to know... But make ptest did end with an
>> error:
>>
>> Doctests interrupted: 2203/3630 files tested
>>
>
>
On Sunday, April 29, 2018 at 3:54:08 PM UTC+1, Christelle Vincent wrote:
>
> Well, I don't know if you want to know... But make ptest did end with an
> error:
>
> Doctests interrupted: 2203/3630 files tested
>
Is this reproducible?
(i.e., does it fail at the same spot if you re-run this?)
To
Well, I don't know if you want to know... But make ptest did end with an
error:
Doctests interrupted: 2203/3630 files tested
--
Total time for all tests: 12716.1 seconds
cpu time: 7631.7 seconds
cumulative wall time:
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
>>
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
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
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
I was able to do
$ mv /usr/local/lib /usr/local/lib_bak
$ mv /usr/local/include /usr/local/include_bak
$ mv /usr/local/bin /usr/local/bin_bak
(with sudo) and I was able to successfully install python3-3.6.1 but
then the build failed on pyzmq-17.0.0b3. I'm attaching the log but the
problem
On Friday, April 27, 2018 at 4:07:52 PM UTC-7, Samuel Lelievre wrote:
>
>
>
> 2018-04-27 22:18 GMT+02:00 John H Palmieri:
> >
> > On Friday, April 27, 2018 at 12:56:37 PM UTC-7, Dima Pasechnik wrote:
> >>
> >> On Friday, April 27, 2018 at 8:16:32 PM UTC+1, Christelle Vincent wrote:
> >>>
> >>>
2018-04-27 22:18 GMT+02:00 John H Palmieri:
>
> On Friday, April 27, 2018 at 12:56:37 PM UTC-7, Dima Pasechnik wrote:
>>
>> On Friday, April 27, 2018 at 8:16:32 PM UTC+1, Christelle Vincent wrote:
>>>
>>> It says: Should I install the database then?
>>
>> that's OK to do so.
>>
>> I bet the
On Friday, April 27, 2018 at 12:56:37 PM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Friday, April 27, 2018 at 8:16:32 PM UTC+1, Christelle Vincent wrote:
>>
>> It says: Should I install the database then?
>>
>
> that's OK to do so.
>
> I bet the offending library is in /usr/local
> (headers in
On Friday, April 27, 2018 at 8:16:32 PM UTC+1, Christelle Vincent wrote:
>
> It says: Should I install the database then?
>
that's OK to do so.
I bet the offending library is in /usr/local
(headers in /usr/local/include, the library in /usr/local/lib, have a look)
Move them out of the way.
It says: Should I install the database then?
WARNING: The locate database (/var/db/locate.database) does not exist.
To create the database, run the following command:
sudo launchctl load -w
/System/Library/LaunchDaemons/com.apple.locate.plist
Please be aware that the database can take
One difference between your OS X installation and mine: near the start of
your log, I see
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
whereas these say "no" on my machine. What does "locate libintl" say (when you
run it from the
It still didn't work. To recap, this time I tried to install sage-8.2.rc4,
and first I ran
$ export
PATH='/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Library/TeX/texbin'
Make still failed at installing python3-3.6.1.p1, the log looks the same
but I am attaching it again in case I'm missing
Just started over with Samuel's instructions, will update when it's done!
On Friday, April 27, 2018 at 8:57:36 AM UTC-4, Samuel Lelievre wrote:
>
> Tips for building under macOS:
>
> - Check the number of cores you have with the command
>
> $ sysctl -n hw.ncpu
>
> - Before running `make`,
Tips for building under macOS:
- Check the number of cores you have with the command
$ sysctl -n hw.ncpu
- Before running `make`, run the following two lines:
$ export
PATH='/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Library/TeX/texbin'
(this is to remove /usr/local/bin from
You have /usr/local/bin first (or at all) in your PATH. This might be asking
for trouble while building/running Sage, depending upon what you have installed
there.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group
I don't know enough about OpenSSL to weigh in on that part of the
discussion. Maybe that would make it impossible to download some python3
package?
In any case, I am attaching for Dima (thank you for all your help by the
way) the output of set. I also downloaded and just started making
More precisely, the shell simply interprets
if ![ -z "$OPENSSL_INCLUDE" ]
as
if false
so the typo just breaks support for "OPENSSL_INCLUDE".
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving
On 2018-04-26 14:45, Erik Bray wrote:
Line 66 (really line 34 in the unwrapped sources) of spkg-build for
Python 3 shows:
if ![ -z "$OPENSSL_INCLUDE" ]; then
I think that's clearly a typo. Looks like it's been there for a long
time too.
Since #21944 for the record. The question is:
I think you're all barking up the wrong tree. Her build log contains:
./spkg-build: line 66: ![: command not found
Line 66 (really line 34 in the unwrapped sources) of spkg-build for
Python 3 shows:
if ![ -z "$OPENSSL_INCLUDE" ]; then
I think that's clearly a typo. Looks like it's been
it is probably better to use the latest Sage pre-release, 8.2.rc4.
note that 8.1 was not tested on osx 10.13, so it really is not supported...
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving
Perhaps it did not uninstall cleanly. Could you post the output of
set
(run it in terminal at the shell prompt)
--
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
I just uninstalled Homebrew completely (I don't think I need it), deleted
my old attempt at making Sage, restarted my laptop and started making Sage
again. That did not help any, I still get exactly the same error.
On Wednesday, April 25, 2018 at 12:22:08 PM UTC-4, Samuel Lelievre wrote:
>
>
Typically Homebrew installs stuff in /usr/local or /opt/local.
Personally I have Homebrew installed, and I just get it out
of the way when I build Sage, by doing
sudo mv /usr/local /usr/localbackup
sudo mv /opt/local /opt/localbackup
and then when I'm done building Sage I revert that
On Wednesday, April 25, 2018 at 3:05:13 PM UTC+3, Christelle Vincent wrote:
>
> I do have Homebrew installed! Is there any way to stop it from seeing the
> wrong library? Can I uninstall Homebrew? I originally installed it at the
> suggestion of someone who was trying to help me fix a problem
I do have Homebrew installed! Is there any way to stop it from seeing the
wrong library? Can I uninstall Homebrew? I originally installed it at the
suggestion of someone who was trying to help me fix a problem I had
installing Sage 8.0 (which never worked by the way, I've been having these
I guess you have Homebrew/MacPorts/Anaconda installed, and a wrong library
is picked up from one of these.
On Wednesday, April 25, 2018 at 1:49:19 PM UTC+3, Christelle Vincent wrote:
>
> I upgraded through the Apple Developer website. I also did open Xcode
> again after the installation, but I
I upgraded through the Apple Developer website. I also did open Xcode again
after the installation, but I can't remember if any additional components
were installed.
On Tuesday, April 24, 2018 at 1:23:01 PM UTC-4, John H Palmieri wrote:
>
> In my experience, it can help to run Xcode once after
In my experience, it can help to run Xcode once after upgrading so that it
can install some "additional components". Did you re-install command line
tools by upgrading through the app store, or some other way?
On Tuesday, April 24, 2018 at 8:57:30 AM UTC-7, Christelle Vincent wrote:
>
> Hi,
>
35 matches
Mail list logo
