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:
>
> ...
>
I used to have this problem too... So I didn't know how to correct it
now I create a new git to each version and I have no more problem...
(but that's not a way to improve correcting problems ! )
Henri
Le 14/01/2016 08:41, Nathann Cohen a écrit :
Yo,
This should if and only if you upgrade
> 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
>
>
> As mentioned before, there are no incremental updates from 6.x. You need
> to compile from scratch, e.g. after cleaning with "make distclean" or "git
> clean -f -d -x". If you are still working on tickets based on 6.x then you
> might want to use a separate git tree for sage 7.
>
>
>
I
