I saw your message too late and recompiled everything, but now it works!
Thank you very much!
Le lundi 29 octobre 2018 10:06:56 UTC+1, Dima Pasechnik a écrit :
>
> maybe running ./configure followed by make will fix this.
> (as ./configure hopefully will tell Sage where to look for the "right"
maybe running ./configure followed by make will fix this.
(as ./configure hopefully will tell Sage where to look for the "right" curl)
On Mon, Oct 29, 2018 at 8:52 AM 'Paul Mercat' via sage-devel
wrote:
>
> I tried that, but I get the same error.
> Do I need to recompile everything from the
I tried that, but I get the same error.
Do I need to recompile everything from the beginning ?
Le dimanche 28 octobre 2018 22:28:28 UTC+1, Samuel Lelievre a écrit :
>
> So the solution is to change your PATH before you start building Sage,
> so that the PATH does not contain Anaconda.
>
--
You
So the solution is to change your PATH before you start building Sage,
so that the PATH does not contain Anaconda.
--
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
It is the file, thank you. And the relevant bit is:
configure:41026: checking if libcurl is version 7 and >= 7.22.0
configure:41055: gcc -o conftest -g -O2 -fPIC
-I/Users/mercatp/anaconda3/include -L/Users/mercatp/sage/local/lib
-Wl,-rpath,/Users/mercatp/sage/local/lib conftest.c
On Sun, Oct 28, 2018 at 5:27 PM 'Paul Mercat' via sage-devel
wrote:
>
> Is it this file ?
this looks like the main sage's config.log, not the one from R.
To get the latter, look at the bottom of
logs/pkgs/r-3.4.4.p0.log
for the location of the R build directory and look for config.log there.
>
>
Is it this file ?
Le dimanche 28 octobre 2018 14:33:07 UTC+1, Erik Bray a écrit :
>
> It might be more useful to see the config.log for R. I think usually
> when a build fails there is a message providing a path to the
> config.log of the build.
> This would tell us exactly what commands
It might be more useful to see the config.log for R. I think usually
when a build fails there is a message providing a path to the
config.log of the build.
This would tell us exactly what commands configure ran and why it
failed (in principle).
On Sun, Oct 28, 2018 at 12:55 PM 'Paul Mercat' via
Yes, I have
bc 1.06
Le dimanche 28 octobre 2018 12:57:58 UTC+1, Dima Pasechnik a écrit :
>
> Do you have bc installed?
> It is needed by curl-config
> (There is a trac ticket about it)
>
> On 28 Oct 2018 11:55 am, "'Paul Mercat' via sage-devel" <
> sage-...@googlegroups.com > wrote:
>
> Hi !
>
Do you have bc installed?
It is needed by curl-config
(There is a trac ticket about it)
On 28 Oct 2018 11:55 am, "'Paul Mercat' via sage-devel" <
sage-devel@googlegroups.com> wrote:
Hi !
I tried to compile sage-8.4 on my computer on OS X, and I get the following
error.
I compiled using
10 matches
Mail list logo
