On 2017-02-22 08:55, Ralf Stephan wrote:
Can you reproduce it manually (I can't)?
Yes, it is 100% reproducible. And I just checked that 7.6.beta3 is OK,
so it's a regression introduced in 7.6.beta4. I will bisect to see where
the problem was introduced.
--
You received this message because
I just noticed that this doctest was actually introduced in 7.6.beta4 in
#22174, so bisecting will not help...
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to s
Please followup at https://github.com/pynac/pynac/issues/231
On Wed, Feb 22, 2017 at 9:46 AM Jeroen Demeyer
wrote:
> I just noticed that this doctest was actually introduced in 7.6.beta4 in
> #22174, so bisecting will not help...
>
> --
> You received this message because you are subscribed to t
just in case, these tests work for me, so it could be that sage4 has some
weirdness built-in...
On Wednesday, February 22, 2017 at 8:46:38 AM UTC, Jeroen Demeyer wrote:
>
> I just noticed that this doctest was actually introduced in 7.6.beta4 in
> #22174, so bisecting will not help...
>
--
Yo
Hi!
In preparation of next week's SageDays, I am installing SageMath on yet
another laptop. It is Ubuntu 16.04.2 LTS, and gcc is version 5.4.0, and
I typed "make" in the current development branch.
Currently, it builds the gcc-5.4.0 package. Why? I have the same version
on my system!
Cheers,
Sim
On 2017-02-22 11:59, Simon King wrote:
Currently, it builds the gcc-5.4.0 package. Why?
In SAGE_ROOT, run ./configure
It should tell you why.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving e
Hi Jeroen,
On 2017-02-22, Jeroen Demeyer wrote:
> In SAGE_ROOT, run ./configure
>
> It should tell you why.
Do I understand correctly that doing "make" should be enough for
building SageMath, as it was the case in the past? Or is "./configure"
now needed, as for most other software?
And is it s
On 2017-02-22 12:32, Simon King wrote:
Hi Jeroen,
On 2017-02-22, Jeroen Demeyer wrote:
In SAGE_ROOT, run ./configure
It should tell you why.
Do I understand correctly that doing "make" should be enough for
building SageMath, as it was the case in the past?
Yes, it is safe simply because "
Hi Jeroen,
On 2017-02-22, Jeroen Demeyer wrote:
> The reason that I asked you to run ./configure is just to answer the
> *why* question.
Since I am not patient enough to wait till the build has finished:
Shouldn't the reason be visible in install.log? What keywords should
I search in install.l
On 2017-02-22 14:50, Simon King wrote:
Hi Jeroen,
On 2017-02-22, Jeroen Demeyer wrote:
The reason that I asked you to run ./configure is just to answer the
*why* question.
Since I am not patient enough to wait till the build has finished:
Shouldn't the reason be visible in install.log?
No:
Hi Jeroen,
On 2017-02-22, Jeroen Demeyer wrote:
> No: ./configure is run *before* that log file is created.
OK, I did ./configure now.
$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -
On 2017-02-22 16:50, Simon King wrote:
So, it seems that the problem lies in Fortran compiler, right? But I did do
sudo apt-get install gcc-fortran
following the advice of the manual.
To verify, run
gfortran --version
--
You received this message because you are subscribed to the Google Gr
On 2017-02-22 16:50, Simon King wrote:
In other words, I still don't see why gcc should be rebuilt (unless the
developer's manual needs update).
Can you post the config.log file?
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe
Am Mittwoch, 22. Februar 2017 17:04:21 UTC+1 schrieb Jeroen Demeyer:
>
> On 2017-02-22 16:50, Simon King wrote:
> > In other words, I still don't see why gcc should be rebuilt (unless the
> > developer's manual needs update).
>
> Can you post the config.log file?
>
>
Voilà!
Cheers,
Simon
-
Am Mittwoch, 22. Februar 2017 17:04:48 UTC+1 schrieb Jeroen Demeyer:
>
> On 2017-02-22 16:50, Simon King wrote:
> > So, it seems that the problem lies in Fortran compiler, right? But I did
> do
> >sudo apt-get install gcc-fortran
> > following the advice of the manual.
>
> To verify, run
On 22 February 2017 at 16:08, Simon King wrote:
>
>
> Am Mittwoch, 22. Februar 2017 17:04:48 UTC+1 schrieb Jeroen Demeyer:
>>
>> On 2017-02-22 16:50, Simon King wrote:
>> > So, it seems that the problem lies in Fortran compiler, right? But I did
>> > do
>> >sudo apt-get install gcc-fortran
>>
PS:
On 2017-02-22, Simon King wrote:
> Aha. Although I did "apt-get install gcc-fortran", gfortran is not there.
And the reason is that apparently I didn't read the development manual
with enough care. It advises to install gfortran (resp gcc-gfortran on
redhat), and probably I tried gcc-fortra
Hi John,
On 2017-02-22, John Cremona wrote:
> It would be helpful for anyone in Simon's position if, after
> configure, there was a message saying something like "your build will
> be faster if you install the following system-wide: gfortran, ... "
> but I'm sure it will be hard to have such a me
Hi Simon,
Le mercredi 22 février 2017 17:13:51 UTC+1, Simon King a écrit :
>
> PS:
>
> On 2017-02-22, Simon King > wrote:
> > Aha. Although I did "apt-get install gcc-fortran", gfortran is not
> there.
>
> And the reason is that apparently I didn't read the development manual
> with enough
Hi Eric,
On 2017-02-22, Eric Gourgoulhon wrote:
> I think that, for Ubuntu 16.04, you should install the package gfortran5,
> not gfortran.
> Indeed gfortran5 corresponds to gcc 5.4.0.
> More generally, the list of packages required for building Sage on Ubuntu
> 16.04 is at
> https://wiki.sage
After installing gfortran (not gfortan5 or gfortran5, which doesn't seem to
exist), I still see various errors in config.log concerning fortran (see
attachment) --- I don't know if Sage would still build its own gcc, but
perhaps you can see from the new config.log what would happen.
Cheers,
Sim
I think there is nothing wrong there, it is typical configure output, checking
for various options that are not crucial.
Looks like gcc spkg will not be built, just as you want.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe fro
Hi Dima,
On 2017-02-22, Dima Pasechnik wrote:
> Looks like gcc spkg will not be built, just as you want.
OK, then all is good.
Best regards,
Simon
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiv
Looks fine to me...
On 2017-02-22 18:31, Simon King wrote:
configure:5266: checking for gfortran
configure:5282: found /usr/bin/gfortran
configure:5293: result: gfortran
configure:5319: checking for Fortran compiler version
configure:5328: gfortran --version >&5
GNU Fortran (Ubuntu 5.4.0-6ubuntu
24 matches
Mail list logo
