chris wuthrich wrote:
>
> The original problem in this thread was resolved, but then there were
> other problems with compiling sage 7.3 on CentOS6.8.
Could you sketch them?
Missing prerequisites, and/or further outdated/too old/insufficient
versions?
FWIW, (system) Python 2.6 compatibility (t
The original problem in this thread was resolved, but then there were other
problems with compiling sage 7.3 on CentOS6.8. I decided to install the
devtools and it worked fine.
Maybe somewhere in the installation guidelines, one could add that for
CentOS it is recommended to install devtoolset
Francois Bissey wrote:
>
>> On 22/07/2016, at 09:19, Travis Scrimshaw wrote:
>>
>> Also we have
>>
>> $ as -v
>> Apple Inc version cctools-870, GNU assembler version 1.38
>>
>
> OK that’s definitely an older version of the Xcode toolchain.
> Here I have
> Mirage:~ fbissey$ as --version
> Apple L
> On 22/07/2016, at 09:19, Travis Scrimshaw wrote:
>
> Also we have
>
> $ as -v
> Apple Inc version cctools-870, GNU assembler version 1.38
>
OK that’s definitely an older version of the Xcode toolchain.
Here I have
Mirage:~ fbissey$ as --version
Apple LLVM version 7.3.0 (clang-703.0.29)
Targ
Here is the analog of /proc/cpuinfo (AFAIK):
sysctl -a | grep machdep.cpu
machdep.cpu.max_basic: 13
machdep.cpu.max_ext: 2147483656
machdep.cpu.vendor: GenuineIntel
machdep.cpu.brand_string: Intel(R) Core(TM) i7-4558U CPU @ 2.80GHz
machdep.cpu.family: 6
machdep.cpu.model: 69
machdep.cpu.extmodel:
I guess there could be the possibility that he has an older version of Xcode
somehow.
What does
as —version
report?
François
> On 22/07/2016, at 03:58, Travis Scrimshaw wrote:
>
> Here is Jang Soo's build log.
>
> Best,
> Travis
>
>
> --
> You received this message because you are subscri
PS - Applying the fix to the shared flags allowed NTL to compile.
--
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
Here is Jang Soo's build log.
Best,
Travis
--
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 em
Francois Bissey wrote:
> Works out of the box on my Mac 10.11 machine. Definitely want logs.
And the analogue of /proc/cpuinfo...
-leif
> François
>
>> On 21/07/2016, at 17:14, Travis Scrimshaw wrote:
>>
>>Another point of reference/FYI, this failed when I was trying to get Sage
>> 7.3.b
Works out of the box on my Mac 10.11 machine. Definitely want logs.
François
> On 21/07/2016, at 17:14, Travis Scrimshaw wrote:
>
>Another point of reference/FYI, this failed when I was trying to get Sage
> 7.3.beta8 from scratch to install on Mac 10.11 (IIRC) with Jang Soo Kim (who
> I h
Another point of reference/FYI, this failed when I was trying to get
Sage 7.3.beta8 from scratch to install on Mac 10.11 (IIRC) with Jang Soo
Kim (who I hope will post here his build log for NTL). For reference,
command-line tools are installed. So it doesn't seem to just be old
versions of
Travis Scrimshaw wrote:
> Just FYI - Tom Roby and I ran into this problem today trying to get
> 7.3.beta8 to build on OS X 10.9. So a fix before 7.3 is released would
> be good and appreciated.
I've made a blocker ticket [1] for Sage 7.3 with a probably preliminary
fix/work-around; a better soluti
Just FYI - Tom Roby and I ran into this problem today trying to get
7.3.beta8 to build on OS X 10.9. So a fix before 7.3 is released would be
good and appreciated.
Best,
Travis
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from
chris wuthrich wrote:
>
> Thanks a lot, leif, for the help.
>
> I will ask the sysadmin to update binutils.
Well, in this case Sage built and used its own GCC (currently 4.9.3)
because at least /the default one/ on your system is outdated as well.
You may ask the sysadmin whether already a new
On Tuesday, July 19, 2016 at 5:35:55 PM UTC+2, leif wrote:
>
> Huh, dead old toolchain on a recent Intel machine.
>
Centos/Redhat 6 is from 2010 and supported until 2020...
If you want to get good performance for recent hardware you'd need
something fresher, of course.
--
You received this me
Thanks a lot, leif, for the help.
I will ask the sysadmin to update binutils.
Your idea with SAGE_FAT_BINARY seems to get around the problem, by now.
If it still helps for #20779:
sageadm@pmlapsag01:~/sage$ as --version
GNU assembler version 2.20.51.0.2-5.44.el6 20100205
Copyright 2009 Free
leif wrote:
> leif wrote:
>> chris wuthrich wrote:
>>>
>>> Trying to compile sage 7.3.beta8 on CentOS6.8, I ran into a problem
>>> compiling ntl 9.8.1.
>>>
>>> Not sure what to include. Just ask.
>
> You may give us the output of 'as --version'.
P.P.S.: Maybe
$ head -25 /proc/cpuinfo
and perha
leif wrote:
> chris wuthrich wrote:
>>
>> Trying to compile sage 7.3.beta8 on CentOS6.8, I ran into a problem
>> compiling ntl 9.8.1.
>>
>> Not sure what to include. Just ask.
You may give us the output of 'as --version'.
> Huh, dead old toolchain on a recent Intel machine.
>
> Update binutils
chris wuthrich wrote:
>
> Trying to compile sage 7.3.beta8 on CentOS6.8, I ran into a problem
> compiling ntl 9.8.1.
>
> Not sure what to include. Just ask.
Huh, dead old toolchain on a recent Intel machine.
Update binutils (which include the GNU assember), or disable
'-march=native' in NTL. (
19 matches
Mail list logo
