Unfortunately, didn't work correctly. Running
SAGE_INSTALL_GCC=yes make
seems to do something wrong to gmp. e.g., while building GMP-ECM...
checking if gmp.h version and libgmp version are the same... (6.1.0/5.1.3)
no
configure: error: 'gmp.h' and 'libgmp' have different versions, you have to
On Monday, September 26, 2016 at 1:02:53 AM UTC, John H Palmieri wrote:
>
> I'm having this problem with "git trac checkout 21592", for example.
>
> A question: how do I identify which version of git-trac is installed? Is
> the version actually recorded anywhere in the source code?
>
there is
jb12407@lmfdb5:~$ lscpu
Architecture: x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):64
On-line CPU(s) list: 0-63
Thread(s) per core:2
Core(s) per socket:8
Socket(s): 4
NUMA node(s): 8
Vendor ID:
On Monday, September 26, 2016 at 12:40:23 AM UTC, Jonathan Bober wrote:
>
> Is git still down, or do is the problem just that I don't know what I am
> doing?
>
> jb12407@lmfdb5:/data/local/sage/sage-7.3$ git trac checkout 21596
>
Make sure you have the latest `git trac` installed.
There is no
I'm getting a segfault on the current development branch of sage (see
below). Is this a known issue and/or effecting anyone else?
This does not happen for me in Sage 7.3, although it does happen if I try
to go "back in time" with a 'git checkout 7.3' and then rebuild. So just to
be certain I
On Mon, Sep 26, 2016 at 2:00 AM, Dima Pasechnik wrote:
surely one can mess everything up with env. vars :-)
>
Yes, of course, I should have been more specific. I mean 'standard'
environment variables (which users like me might use in wrong or 'hackish'
ways). e.g., something
I'm having this problem with "git trac checkout 21592", for example.
A question: how do I identify which version of git-trac is installed? Is
the version actually recorded anywhere in the source code?
John
On Sunday, September 25, 2016 at 5:54:54 PM UTC-7, Dima Pasechnik wrote:
>
>
>
> On
That's a good point. It looks like 5.1.0. I will try rebuilding from
scratch with SAGE_INSTALL_GCC=yes, since that's easier than actually trying
to figure out what's going on. (Also, it is past time for me to update gcc,
since it looks like I can easily have 6.1.0 on this system.) I will report
On Sunday, September 25, 2016 at 6:18:53 PM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Monday, September 26, 2016 at 1:02:53 AM UTC, John H Palmieri wrote:
>>
>> I'm having this problem with "git trac checkout 21592", for example.
>>
>> A question: how do I identify which version of git-trac is
On Sunday, September 25, 2016 at 9:33:42 PM UTC, Jonathan Bober wrote:
>
> I'm getting a segfault on the current development branch of sage (see
> below). Is this a known issue and/or effecting anyone else?
>
> This does not happen for me in Sage 7.3, although it does happen if I try
> to go
Is git still down, or do is the problem just that I don't know what I am
doing?
jb12407@lmfdb5:/data/local/sage/sage-7.3$ git trac checkout 21596
Loading ticket #21596...
Newly created local branch:
t/21596/matrix_charpoly_algorithm__flint___destroys_the_polynomial_ring_generator
Traceback (most
On Monday, September 26, 2016 at 12:06:44 AM UTC, Jonathan Bober wrote:
>
> Unfortunately, didn't work correctly. Running
>
> SAGE_INSTALL_GCC=yes make
>
> seems to do something wrong to gmp. e.g., while building GMP-ECM...
>
> checking if gmp.h version and libgmp version are the same...
On Mon, Sep 26, 2016 at 1:54 AM, Dima Pasechnik wrote:
>
>
> On Monday, September 26, 2016 at 12:40:23 AM UTC, Jonathan Bober wrote:
>>
>> Is git still down, or do is the problem just that I don't know what I am
>> doing?
>>
>> jb12407@lmfdb5:/data/local/sage/sage-7.3$ git
I recompiled with gcc 6.1.0, and get the same segfault. I did a ./sage -i
gdb to get a better crash report, which is attached. I don't know if it is
useful. Also, it mentions some gcc 5.1.0 paths, which seems odd. I don't
know if that indicates that something is broken on my end.
On Mon, Sep 26,
Most probably gcc version used to build Sage is also quite important...
On Sunday, September 25, 2016 at 10:16:23 PM UTC, Jonathan Bober wrote:
>
> jb12407@lmfdb5:~$ lscpu
> Architecture: x86_64
> CPU op-mode(s):32-bit, 64-bit
> Byte Order:Little Endian
> CPU(s):
On Sunday, September 25, 2016 at 10:48:51 PM UTC, Jonathan Bober wrote:
>
> That's a good point. It looks like 5.1.0. I will try rebuilding from
> scratch with SAGE_INSTALL_GCC=yes, since that's easier than actually trying
> to figure out what's going on.
>
it might well be that 5.1 cannot
I almost cannot use either web interface, or git server.
(however I can ssh to the host, although it is slow...)
I see a lot of apache activity...
Does anyone do anything heavy?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from
On Sun, Sep 25, 2016 at 8:13 AM, Dima Pasechnik wrote:
>
> I almost cannot use either web interface, or git server.
> (however I can ssh to the host, although it is slow...)
> I see a lot of apache activity...
>
> Does anyone do anything heavy?
I doubt this is good:
The buildbot is offline, too... http://build.sagedev.org
There shouldn't be a connection but its certainly an odd coincidence
On Sunday, September 25, 2016 at 5:22:19 PM UTC+2, William wrote:
>
> On Sun, Sep 25, 2016 at 8:13 AM, Dima Pasechnik > wrote:
> >
> > I almost
19 matches
Mail list logo