On Monday, 25 January 2016 07:31:02 UTC, Nathann Cohen wrote:
>
> >> I am sure if we were electing the best Sage bugs, you won't abstain...
> > I vote for http://trac.sagemath.org/ticket/10609
>
> Come on, it's ridiculous alright but you cannot vote for it: it's not
> even a Sage bug.
>
A
> It happened again with 7.0.
>
> Running 'make' a second time, as previously, did the job.
Happened again with the latest beta. I'll do a "make dist-clean",
hoping that it will not happen again later on.
Nathann
--
You received this message because you are subscribed to the Google Groups
On 2016-01-24 10:04, Nathann Cohen wrote:
At each
new beta I checkout develop and pull the new commits, then run 'make'
and this message happens. If I type 'make' again right after the
message does *not* appear, and the compilation goes on.
So you're not running "make distclean" at all?
Did
> Could you say more precisely *what happened exactly* again.
Do you mean more than what I reported in the first message of this
thread? Nothing changed since that time as far as I can tell. At each
new beta I checkout develop and pull the new commits, then run 'make'
and this message happens. If
> So you're not running "make distclean" at all?
No. But I did 5 seconds ago and I am now recompiling everything.
Perhaps the problem will not happen again.
> Did you verify that you're really on origin/develop, without any other
> commits or uncommited changes?
Yes yes. I am always on the
> The definition of insanity is doing the same thing over and over again,
but expecting different results ;-)
That's what I should answer the next guy who will try the "it's
irresponsible to not vote" lecture on me.
Nathann
>
>
>
>
>
>
> On Sunday, January 24, 2016 at 4:21:50 AM UTC-5, Nathann
>> I am sure if we were electing the best Sage bugs, you won't abstain...
> I vote for http://trac.sagemath.org/ticket/10609
Come on, it's ridiculous alright but you cannot vote for it: it's not
even a Sage bug.
I'm rather glad, by the way, that being unable to produce such
high-quality bugs we
> I am sure if we were electing the best Sage bugs, you won't abstain...
I hope that our first reflex with be to try to fix them instead of
voting on them :-P
> (and, interestingly, most probably next time the election results would be
> different...)
The most fitting name for what is called
On Sunday, 24 January 2016 12:09:27 UTC, Nathann Cohen wrote:
>
>
> > The definition of insanity is doing the same thing over and over again,
> but expecting different results ;-)
>
> That's what I should answer the next guy who will try the "it's
> irresponsible to not vote" lecture on me.
>
On 2016-01-24 16:01, Dima Pasechnik wrote:
I am sure if we were electing the best Sage bugs, you won't abstain...
I vote for http://trac.sagemath.org/ticket/10609
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group
>
> After this double "make" (the first that fails with the message above,
> the second that works) it is a regular directory. If it happens again
> I will post here.
>
It happened again with 7.0.
Running 'make' a second time, as previously, did the job.
Nathann
--
You received this
After you run "make distclean & make", is lib64 a symlink? If its not then
its a bug.
On Thursday, January 14, 2016 at 7:32:55 AM UTC+1, Nathann Cohen wrote:
>
> Hello everybody,
>
> For the latest beta releases, each time 'git pull && make' produced
> the following message:
>
> ...
>
> After you run "make distclean & make", is lib64 a symlink? If its not then
> its a bug.
After this double "make" (the first that fails with the message above,
the second that works) it is a regular directory. If it happens again
I will post here.
Nathann
--
You received this message because
If "make distclean" fails then its not going to do anything, duh. Delete
SAGE_LOCAL by hand or "git clean -f -d -x"
On Thursday, January 14, 2016 at 9:22:54 AM UTC+1, Nathann Cohen wrote:
>
> > After you run "make distclean & make", is lib64 a symlink? If its not
> then
> > its a bug.
>
>
> I guess you mean "make distclean && make" (double ampersand)
I did.
Nathann
--
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
On 2016-01-14 09:15, Volker Braun wrote:
After you run "make distclean & make", is lib64 a symlink? If its not
then its a bug.
I guess you mean "make distclean && make" (double ampersand)
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To
> If "make distclean" fails then its not going to do anything, duh. Delete
> SAGE_LOCAL by hand or "git clean -f -d -x"
'make distclean' did not fail: only 'make' failed. And I am not stuck:
the first call to 'make' fails with the error reported above, but the
second worked alright and I am now
17 matches
Mail list logo
