From: "François Bissey" <f.r.bissey@massey.ac.nz>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] [sage-on-gentoo] genus2reduction - pari.h
Date: Sat, 1 May 2010 08:38:58 +1200 [thread overview]
Message-ID: <201005010838.58473.f.r.bissey@massey.ac.nz> (raw)
In-Reply-To: <1272639661.26964.2@ledaig>
> Hello,
>
> It appears that genus2reduction will no longer compile here. I get
>
> >>> Checking genus2reduction-0.3.p6.tar.bz2's mtime...
> >>> WORKDIR is up-to-date, keeping...
> >>> It appears that 'genus2reduction-0.3_p6' is already prepared;
> >>> skipping.
> >>> Remove
> >>> '/var/tmp/portage/sci-mathematics/genus2reduction-0.3_p6/.prepared'
> >>> to force prepare.
> >>> Configuring source in
> >>> /var/tmp/portage/sci-mathematics/genus2reduction-0.3_p6/work/genus2redu
> >>> ction-0.3.p6/src ...
> >>> Source configured.
> >>> Compiling source in
> >>> /var/tmp/portage/sci-mathematics/genus2reduction-0.3_p6/work/genus2redu
> >>> ction-0.3.p6/src ...
>
> genus2reduction.c:18:18: error: pari.h: No such file or directory
>
> ...
>
> ERROR: sci-mathematics/genus2reduction-0.3_p6 failed:
> Compile failed!
>
> Call stack:
> ebuild.sh, line 54: Called src_compile
> environment, line 1225: Called die
> The specific snippet of code:
> $(tc-getCC ) ${CFLAGS} -o ${PN} ${PN}.c -lpari -lgmp -lm ||
> die "Compile failed!";
>
Hi Steve,
fixed in the overlay. The bug was in src_prepare because we used to inherit
the eutils eclass from somewhere. No eutils eclass no epatch command.
It would have been better if you had given the full log after ebuild clean so
we could have spotted the problem in src_prepare straight away.
Francois
next prev parent reply other threads:[~2010-04-30 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 14:57 [gentoo-science] [sage-on-gentoo] genus2reduction - pari.h Steven Trogdon
2010-04-30 20:38 ` François Bissey [this message]
2010-04-30 21:07 ` Steven Trogdon
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=201005010838.58473.f.r.bissey@massey.ac.nz \
--to=f.r.bissey@massey.ac.nz \
--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