From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org, markusle@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-lang/R: ChangeLog R-2.6.0.ebuild R-2.4.1.ebuild R-2.5.0.ebuild
Date: Sun, 7 Oct 2007 01:53:23 -0700 [thread overview]
Message-ID: <20071007085323.GF31103@supernova> (raw)
In-Reply-To: <E1IeAX2-0007JL-Dx@stork.gentoo.org>
On 14:21 Sat 06 Oct , Markus Dittrich (markusle) wrote:
> 1.1 dev-lang/R/R-2.6.0.ebuild
>
> file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-lang/R/R-2.6.0.ebuild?rev=1.1&view=markup
> plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-lang/R/R-2.6.0.ebuild?rev=1.1&content-type=text/plain
> pkg_setup() {
> # Test for a 64 bit architecture - f2c won't work on 64 bit archs with R.
> # Thanks to vapier for providing the test.
> cd "${T}"
> echo 'int main(){}' > test.c
> $(tc-getCC) -c test.c -o test.o
> if file test.o | grep -qs 64-bit ; then
> einfo "64 bit architecture detected, using g77 or gfortran."
... or ifc?
> FORTRAN="gfortran g77 ifc"
> else
> FORTRAN="gfortran g77 f2c"
How come ifc isn't down here, too?
> # R-2.5.0 started to have issues with parallel make
> emake -j1 || die "emake failed"
Got an upstream bug filed?
> make \
If emake doesn't work, please add a comment to that effect.
> prefix=${D}/usr \
> mandir=${D}/usr/share/man \
> infodir=${D}/usr/share/info \
> libdir=${D}/usr/$(get_libdir) \
> rhome=${D}/usr/$(get_libdir)/R \
> -i ${D}/usr/$(get_libdir)/R/bin/R \
> -i ${D}/usr/$(get_libdir)/R/bin/R \
> sed -e "s:${D}::" -i ${D}/usr/$(get_libdir)/pkgconfig/libR.pc \
> cd ${D}/usr/bin/
> > ${D}/etc/env.d/99R
> cd ${S}
Quote variables that can have spaces in them: D, S, T, WORKDIR,
FILESDIR, DESTDIR, ROOT.
Thanks,
Donnie
--
gentoo-dev@gentoo.org mailing list
parent reply other threads:[~2007-10-07 9:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1IeAX2-0007JL-Dx@stork.gentoo.org>]
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=20071007085323.GF31103@supernova \
--to=dberkholz@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=markusle@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