-upload-pack
22:00:27:/usr/lib$ ls /sage
2013/12/20 Volker Braun
> Which version of git is in the system path?
>
>
> On Friday, December 20, 2013 8:48:50 PM UTC, Marco Streng wrote:
>>
>> I think one of the first two must have done the trick, as LD_LIBRARY_PATH
>>
at that is) and the
original path was
PATH=/opt/local/bin:/sage:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin
where /sage was empty (because of Jean-Pierre's remark), so the difference
in PATH is git.
Best,
Marco
2013/12/20 Jeroen Demeyer
> On 2013-12-20 11:17,
xample:
sage0._contains('2', 'QQ')
Expected:
True
Got:
False
2013/12/19 Marco Streng
>
>
>
> 2013/12/19 Jeroen Demeyer
>
>> On 2013-12-19 15:08, Marco Streng wrote:
>>
>>> New machine, new problem. On a mac recently upgraded fr
11:10:43:~/sage_built_on_mavericks/sage-6.0$ which gcc
/usr/bin/gcc
11:16:07:~/sage_built_on_mavericks/sage-6.0$ gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 5.0 (clang-500.2.79) (based on LLV
2013/12/19 Marco Streng
> 2013/12/19 Jean-Pierre Flori
>
>> Looks like
>> https://groups.google.com/d/msg/sage-release/PXtNIE_5V-4/2Upi4LoaWbIJ
>> Maybe you added the path to old Sage binaries in your path?
>>
>
>
> I did. Then fixed that, rebooted, and d
Op vrijdag 18 januari 2013 08:05:12 UTC+1 schreef Jeroen Demeyer:
>
> Looking at the log, the main issue is probably GCC. It's simply an
> invalid configuration to have gcc in your PATH but not GCC's libraries
> in LD_LIBRARY_PATH. Although I would have expected an error much
> earlier...
>
2013/12/19 Jeroen Demeyer
> On 2013-12-19 15:08, Marco Streng wrote:
>
>> New machine, new problem. On a mac recently upgraded from 10.8 to 10.9,
>> after downloading and extracting the tarball and typing "make", I get
>> the following problem (both sage 5
New machine, new problem. On a mac recently upgraded from 10.8 to 10.9,
after downloading and extracting the tarball and typing "make", I get the
following problem (both sage 5.13 and sage 6.0).
sed: /usr/include/sys/cdefs.h: No such file or directory
Marco
-
Found package gcc-4.7.3.p1
2013/12/19 Jean-Pierre Flori
> Looks like
> https://groups.google.com/d/msg/sage-release/PXtNIE_5V-4/2Upi4LoaWbIJ
> Maybe you added the path to old Sage binaries in your path?
>
I did. Then fixed that, rebooted, and downloaded fresh tarballs and am
still compiling... (but the conway polynomials
Any idea what this could be or how I could find out?
Thanks!
Marco
2013/12/19 Jeroen Demeyer
> On 2013-12-19 09:12, Marco Streng wrote:
>
>> I tried 5.13.rc0 and it had the same problem. Is that different from 5.13?
>>
> No, it's the same.
>
>
> --
> You
I tried 5.13.rc0 and it had the same problem. Is that different from 5.13?
2013/12/19 Jeroen Demeyer
> On 2013-12-19 09:03, Marco Streng wrote:
>
>> Is this supposed to build on 10.9?
>>
> Yes, it is supposed to work. Did you try Sage 5.13?
>
>
> --
> You rece
2013/12/17 Justin C. Walker
> Cloned from github. Build completed w/o problems, and all tests
> ('ptestlong') passed on two OS X systems: 10.6.8 (dual 6-core Xeons) and
> 10.9.1 (quad core Core i7).
>
Is this supposed to build on 10.9? That did not work for me.
Recently upgraded my Mac from 1
12 matches
Mail list logo