public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Kahle <tomka@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Sage, ecls, maxima
Date: Fri, 12 Oct 2012 14:09:08 -0700	[thread overview]
Message-ID: <20121012210908.GG16602@schlaumatte> (raw)
In-Reply-To: <50776DD4.20708@slingshot.co.nz>

[-- Attachment #1: Type: text/plain, Size: 2263 bytes --]

Hi,


On 14:09 Fri 12 Oct 2012, Francois Bissey wrote:
[...]
> > 
> > I conclude that my original problem with sage not working was due to
> > some upgrade breaking either maxima or ecls (but not picked up by
> > revdep-rebuild!).  When trying to rebuild I ran into the build failures
> > described above, but the combination of ecls-12.7.1 and maxima-5.26.0
> > builds and works with sage so far.
> > 
> 
> OK ecls is fine sbcl isn't. I would like you to try without unicode for
> both ecls and maxima. ecls with unicode can cause trouble in sage we
> thought we had a solution with Paulo (formerly from Mandriva) but it
> is not fool-proof.

ecls fails to install with USE="-unicode".  Here's the error:

>>> Test phase [not enabled]: dev-lisp/ecls-12.2.1

>>> Install ecls-12.2.1 into /var/tmp/portage/dev-lisp/ecls-12.2.1/image/ category dev-lisp
make -j5 -l5 DESTDIR=/var/tmp/portage/dev-lisp/ecls-12.2.1/image/ install 
cd build; make install
make[1]: Entering directory `/var/tmp/portage/dev-lisp/ecls-12.2.1/work/ecl-12.2.1/build'
# Here we would use the option -s but the install program in sourceforge-solaris
# is broken.
/bin/sh /var/tmp/portage/dev-lisp/ecls-12.2.1/work/ecl-12.2.1/src/gc/mkinstalldirs /var/tmp/portage/dev-lisp/ecls-12.2.1/image//usr/bin/ /var/tmp/portage/dev-lisp/ecls-12.2.1/image//usr/lib64/ \
  /var/tmp/portage/dev-lisp/ecls-12.2.1/image//usr/lib64/ecl-12.2.1/ /var/tmp/portage/dev-lisp/ecls-12.2.1/image//usr/include/ /var/tmp/portage/dev-lisp/ecls-12.2.1/image//usr/include//ecl
mkdir -p -- /var/tmp/portage/dev-lisp/ecls-12.2.1/image//usr/bin/ /var/tmp/portage/dev-lisp/ecls-12.2.1/image//usr/lib64/ /var/tmp/portage/dev-lisp/ecls-12.2.1/image//usr/lib64/ecl-12.2.1/ /var/tmp/portage/dev-lisp/ecls-12.2.1/image//usr/include/ /var/tmp/portage/dev-lisp/ecls-12.2.1/image//usr/include//ecl
for i in bin/ecl; do \
  /usr/bin/install -c $i /var/tmp/portage/dev-lisp/ecls-12.2.1/image//usr/bin/; \
done
/usr/bin/install: cannot stat ‘bin/ecl’: No such file or directory
make[1]: *** [install] Error 1
make[1]: Leaving directory `/var/tmp/portage/dev-lisp/ecls-12.2.1/work/ecl-12.2.1/build'
make: *** [install] Error 2
emake failed



-- 
Thomas Kahle
http://dev.gentoo.org/~tomka/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  reply	other threads:[~2012-10-13  0:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 22:42 [gentoo-science] Sage, ecls, maxima Thomas Kahle
2012-10-11  0:04 ` Thomas Kahle
2012-10-11  8:42   ` Francois Bissey
2012-10-11 23:21     ` Thomas Kahle
2012-10-12  1:09       ` Francois Bissey
2012-10-12 21:09         ` Thomas Kahle [this message]
2012-10-13  4:46           ` Francois Bissey
2012-10-14 22:24             ` Thomas Kahle
2012-10-11 17:58   ` Steven Trogdon
2012-10-11 18:37     ` Francois Bissey
2012-10-11 23:08       ` Thomas Kahle
2012-10-12  4:18       ` Andrey G. Grozin
2012-10-12  4:16     ` Andrey G. Grozin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121012210908.GG16602@schlaumatte \
    --to=tomka@gentoo.org \
    --cc=gentoo-science@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox