Le vendredi 20 octobre 2017 05:38:57 UTC+2, Timo Kaufmann a écrit :
>
> After adding one more depencency (hevea) the compilation succeeds. Thank
> you for your help.
>
> It needs quite some dependencies that are not mentioned on the README's
> instructions though (like hevea and texlive). Are t
I am essentially building like this:
```
autoreconf --install --force --verbose
./configure --disable-dependency-tracking --prefix=${out}
make -j4 -l4 SHELL="$(which bash)"
```
And yes, in the failing builds texlive was present (in an minimal
configuration). Do you think texlives presence also t
On 20/10/2017 05:38, Timo Kaufmann wrote:
After adding one more depencency (hevea) the compilation succeeds. Thank
you for your help.
It needs quite some dependencies that are not mentioned on the README's
instructions though (like hevea and texlive). Are those just undocumented
or does it depen
On Friday, October 20, 2017 at 4:38:57 AM UTC+1, Timo Kaufmann wrote:
>
> After adding one more depencency (hevea) the compilation succeeds. Thank
> you for your help.
>
> It needs quite some dependencies that are not mentioned on the README's
> instructions though (like hevea and texlive). Are
After adding one more depencency (hevea) the compilation succeeds. Thank
you for your help.
It needs quite some dependencies that are not mentioned on the README's
instructions though (like hevea and texlive). Are those just undocumented
or does it depend on some build options?
--
You receive
> On 20/10/2017, at 09:58, Timo Kaufmann wrote:
>
> So do you think that sed command actually fixed the first error?
Yes, I think your second error was way after compiling the file giving
you the first error.
François
--
You received this message because you are subscribed to the Google Gro
Okay, I've added automake-1.11 and a full texlive install to the deps. I'll
rerun the build and see how it turns out.
So do you think that sed command actually fixed the first error?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
> On 20/10/2017, at 09:43, François Bissey wrote:
>
> textile
texlive - thank you autocorrect.
--
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 sage-devel+unsu
> On 20/10/2017, at 09:36, Timo Kaufmann wrote:
>
> With that change the build still fails, just for a different reason:
>
> ```
> Making install in doc
> make[1]: Entering directory
> '/home/timo/nix/shell/sage-8.0/local/var/tmp/sage/build/giac-1.2.3.47.p0/src/doc'
> Making install in en
> m
With that change the build still fails, just for a different reason:
```
Making install in doc
make[1]: Entering directory
'/home/timo/nix/shell/sage-8.0/local/var/tmp/sage/build/giac-1.2.3.47.p0/src/doc'
Making install in en
make[2]: Entering directory
'/home/timo/nix/shell/sage-8.0/local/var/t
No, the build started
from https://github.com/sagemath/sage/archive/8.0.tar.gz
The weird looking path names are normal in nixos[1], since it writes every
package under a path containing the hash of its build inputs.
[1]: https://nixos.org/
Am Donnerstag, 19. Oktober 2017 15:18:56 UTC-5 schrieb
Thanks for taking a look at it. Yes, the spkg-install is modified:
```
--- old/build/pkgs/giac/spkg-install 2017-07-21 14:10:00.0 -0500
+++ new/build/pkgs/giac/spkg-install 2017-10-15 15:55:55.321237645 -0500
@@ -4,6 +4,8 @@
## Giac
###
+find . -
have you by any chance started from a binary Sage install rather than from the
source (these weird looking path names in the log suggest this)?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emai
It looks to me like your spkg-install for giac has custom modifications. From
the log
Host system:
Linux pad 4.9.56 #1-NixOS SMP Thu Oct 12 19:24:22 UTC 2017 x86_64 GNU/Linux
C compiler: gcc
C
14 matches
Mail list logo
