On 5/28/16 5:20 PM, 美彦 馬場 wrote:
> Dear all,
>
> May I update R related packages that are in libs/rmods to be used with the
> latest r-base33?
>
> Most of them have no maintainer, but some maitained by David Fang and myself.
>
> I will also update to the latest versions.
There's no problem with u
Dear all,
May I update R related packages that are in libs/rmods to be used with the
latest r-base33?
Most of them have no maintainer, but some maitained by David Fang and myself.
I will also update to the latest versions.
--
BABA Yoshihiko
---
Hanspeter,
2014/06/14 11:43、Hanspeter Niederstrasser のメール:
> When building another pkg that uses r-base30, I get this error:
>
> -- Using R at /sw/Library/Frameworks/R.framework/Versions/3.0/Resources/bin/R
> /sw/Library/Frameworks/R.framework/Versions/3.0/Resources/bin/R: line 191:
> /sw/bin
When building another pkg that uses r-base30, I get this error:
-- Using R at
/sw/Library/Frameworks/R.framework/Versions/3.0/Resources/bin/R
/sw/Library/Frameworks/R.framework/Versions/3.0/Resources/bin/R: line
191: /sw/bin/sed: No such file or directory
ERROR: option '-e' requires a non-empty
My mistake. I thought you had said the problem existed in the newer
versions but was latent rather than fixed.
On Tuesday, April 29, 2014, Daniel Macks wrote:
> Why would they want a bug report against such an old version? Are newer
> versions not-broken? I'm pretty sure I already mentioned exac
Why would they want a bug report against such an old version? Are newer
versions not-broken? I'm pretty sure I already mentioned exactly what
change they made in newer versions to avoid trying to access the
internals of the external libpcre.
dan
On Tue, 29 Apr 2014 13:44:34 -0400, Jack Howart
Okay, I now see that disables the use of pcre. Guess someone should open a
PR upstream, no? Do we really gain anything of use by having R-base build
against pcre?
On Tuesday, April 29, 2014, Jack Howarth wrote:
> Well, empirically it fixed the r-base214 build on 10.8 for me by just
> changing --
Well, empirically it fixed the r-base214 build on 10.8 for me by just
changing --with-system-pcre to --with-pcre=%p. It would be highly irregular
for the --with-system-pcre option not to be pushing the headers in
/usr/include to be used.
On Tuesday, April 29, 2014, Daniel Macks wrote:
> (sorry i
(sorry if this email goes out twice!)
I don't think that's the meaning of "system". R appears to have
optional onboard/internal sources of various dependencies as an
alternative to using ones existing "on the system". *Where* on the
system is a different issue. You can probably check the .d fil
Isn't this just a header mismatch? We have both a build depends on libpcre1
and --with-system-pcre which is illogical. I am testing with
--with-system-pcre changed to --with-pcre=%p. FYI, macports doesn't pass
either flag and incorrectly ignores pcre.
On Tuesday, April 29, 2014, Daniel Macks wrot
Using (apparently-)undocumented, internal implementation details that
are known to change in different versions is *always* a problem. Any
solution that doesn't involve actually not-doing-that is merely
deferring the same failure from occurring again in the future when
those details change agai
Daniel,
Isn't the real problem that r-base in fink is being built with
--with-system-pcre but the fink lib pcre.1.dylib ends up linked into libR.
I assume we need a BuildConflicts on libpcre1 in order to have the system
pcre used.
Jack
On Tuesday, April 29, 2014, Danie
On Mon, 28 Apr 2014 22:38:02 -0400, Daniel Macks wrote:
On Mon, 28 Apr 2014 20:55:18 -0400, Jack Howarth
> wrote:
> > The r-base214 packaging seems to have test suite issues when built
> > against Xcode 5.1 on darwin12…
> >
> > Testing examples for package ‘utils’
> > /sw/src/fink.build/r-base21
On Mon, 28 Apr 2014 20:55:18 -0400, Jack Howarth
wrote:
> The r-base214 packaging seems to have test suite issues when built
> against Xcode 5.1 on darwin12…
>
> Testing examples for package ‘utils’
> /sw/src/fink.build/r-base214-2.14.2-9/R-2.14.2/bin/BATCH: line 60:
> 34097 Trace/BPT trap: 5
Jack,
2014/04/29 9:55、Jack Howarth のメール:
> I have added r-base31 packaging to the 10.7 tree and updated the
> r-base215 and r-base30 packaging to build with gcc49-compiler like r-base31
> and to be aware of the new package. The r-base214 packaging seems to have
> test suite issues when b
Baba,
I have added r-base31 packaging to the 10.7 tree and updated the
r-base215 and r-base30 packaging to build with gcc49-compiler like r-base31
and to be aware of the new package. The r-base214 packaging seems to have
test suite issues when built against Xcode 5.1 on darwin12…
Testing exam
Baba,
Is it okay if I update the r-base215 packaging with the change...
--- r-base215.info 2012-10-09 09:20:22.0 -0400
+++ /sw/fink/10.7/local/main/finkinfo/r-base215.info2012-12-07
20:20:54.0 -0500
@@ -1,14 +1,14 @@
Info2: <<
Package: r-base215
-Version: 2.15.0
-Rev
Baba,
The current r-base213 package fails -m during its InfoTest on Mac OS X 10.7
against Xcode 4.3.2 in 10.7 fink (whereas r-base213 in 10.6 x86_64 fink passes
-m fine against Xcode 4.2). i can't test this until later tonight but there
is a bugzilla...
https://bugs.r-project.org/bugzilla3/show
Anyway, I suspect from your error message that you are using 10.6-i386. The R
environment, on the other hand, is making calls to gcc with no arch flag so it
defaults to x86_64, and your libraries are not compatible with that...
-- Dave
On Sep 27, 2010, at 9:43 PM, David R. Morrison wrote:
Are you using the i386 or x86_64 architecture of fink?
On Sep 27, 2010, at 9:35 PM, BABA Yoshihiko wrote:
> Hi all,
>
> I installed r-base, then tried to install its packages inside R environment,
> with the error below. The binary version of R didn't have such error. Would
> it be Fink's prob
Hi all,
I installed r-base, then tried to install its packages inside R environment,
with the error below. The binary version of R didn't have such error. Would
it be Fink's problem?
R version 2.11.0 (2010-04-22)
Copyright (C) 2010 The R Foundation for Statistical Computing
ISBN 3-900051-07-0
On Sun, Jan 18, 2009 at 06:09:31PM -0800, Adam D. I. Kramer wrote:
> Hello,
>
> Searching the internet, I came across this discussion:
>
> --
> From: Martin Costabel
> Date: 2008-03-10 00:00:45
>
> Dominique Dhumieres wrote:
> >>Do you have atlas-shlibs installed? If yes, could you try if
Hello,
Searching the internet, I came across this discussion:
--
From: Martin Costabel
Date: 2008-03-10 00:00:45
Dominique Dhumieres wrote:
>>Do you have atlas-shlibs installed? If yes, could you try if removing it
>>allows you to build r-base?
>
>
> The answer is yes to both questions
Alexander Hansen wrote:
[]
> So let's say we updated r-base to 2.8.0. It would install stuff in
> %p/Library/Frameworks/R.framework/Versions/2.8 , and then anything that
> linked to the older version of libR.dylib wouldn't be able to find it.
>
> Currently only labplot and rpy-py* depend on r-
We've had a long-standing issue with the r-base package that complicates
updates. Basically the problem is that each new major version of r-base
stashes its files in a versioned directory within its framework, and
anything that links the R library therefore requires that versioning.
For examp
25 matches
Mail list logo