I'm glad I didn't see those comments -- ;-)
Prof. Ripley also pointed out they weren't supposed to be macros.
The -bexpall (actuall -Wl,-bexpall) produced an effect: now it complains
about finding fortran libraries. gfortran was compiled with static libs
on this system. It is complaining as w
On 10/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Full_Name: Din Chen
> Version: 2.4.0
> OS: Windows XP
> Submission from: (NULL) (66.17.122.18)
>
>
> I just updated the R.2.4.0. and got the error message for random effect
> modelling, which was working on R.2.3.1.
>
> library(lme4)
> mmo
[EMAIL PROTECTED] writes:
> I asked a question that might help me track down what changed between
> 2.3.1 that did build and the 2.4.0 version that will not build. Some of
> the undefined names the linker was complaining about looked like #define
> symbols that were not picked up by configure.
On 10/16/2006 3:47 PM, [EMAIL PROTECTED] wrote:
> I asked a question that might help me track down what changed between
> 2.3.1 that did build and the 2.4.0 version that will not build.
Actually, I think your message came through as a bug report, suggesting
you were expecting someone else to f
On Mon, 16 Oct 2006, [EMAIL PROTECTED] wrote:
> This is a rather interesting, but I don't think it is a bug - it is
> just things that "you are not supposed to do"
It was a bug. It has been fixed in R 2.4.0. Unfortunately, since you
didn't quote the PR# of the original bug in the subject line yo
I asked a question that might help me track down what changed between
2.3.1 that did build and the 2.4.0 version that will not build. Some of
the undefined names the linker was complaining about looked like #define
symbols that were not picked up by configure. The first thing I was
hoping for
On Mon, 16 Oct 2006, Douglas Bates wrote:
> I am encountering segfaults when checking the lme4 package on an
> Athlon64 system if I use the acml blas. R was built as a 64-bit
> application using the GCC 4.0.3 compiler suite including gfortran.
> The version of acml is 3.5.0 gfortran64.
gcc 4.1.1
On 10/16/2006 11:09 AM, Gabor Grothendieck wrote:
> On Windows, if I set the repositories to only Omegahat using
> the
>
>Packages | Select repositories
>
> menu and then bring up the install packages menu:
>
>Packages | Install packages
>
> I find that several packages are listed twice
This is a rather interesting, but I don't think it is a bug - it is
just things that "you are not supposed to do"... you are assuming
a certain evaluation order of the 4 "$" operators in
" D$ABC[D$M] = D$V[D$M] " as in:
temp1 <- D$M # 2nd and 4th
temp2 <- D$V[temp1] # 3rd
I am not encountering segfaults either, using earlier versions of
gcc/gfortran64 (4.0.0) and acml (3.0.0) on a 64 bit build of R-2.4.0 on
Fedora Core 4
Best,
Jim
McGehee, Robert wrote:
> I am not encountering segfaults on a 64-bit build of R 2.4.0 compiled
> with gcc and g77 3.4.5 and ATLAS
I did not try the ACML but I have experienced problems both in
configure and in make on my SUSE 10.0 x86_64 with gcc 4.0.2. The
problem was due to a bug in gfortran so that I had to update to
version 4.2 (I did not update gcc though). I do not know whether this
may apply to you but updating the gfo
This is a rather interesting, but I don't think it is a bug - it is
just things that "you are not supposed to do"... you are assuming
a certain evaluation order of the 4 "$" operators in
" D$ABC[D$M] = D$V[D$M] " as in:
temp1 <- D$M # 2nd and 4th
temp2 <- D$V[temp1] # 3rd
On Windows, if I set the repositories to only Omegahat using
the
Packages | Select repositories
menu and then bring up the install packages menu:
Packages | Install packages
I find that several packages are listed twice. Why is that?
I am using Windows XP:
"R version 2.4.0 Patched (200
I am not encountering segfaults on a 64-bit build of R 2.4.0 compiled
with gcc and g77 3.4.5 and ATLAS 3.6.0 on a Red Hat Athlon64 system.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Douglas Bates
Sent: Monday, October 16, 2006 10:26 AM
To: R Developme
I am encountering segfaults when checking the lme4 package on an
Athlon64 system if I use the acml blas. R was built as a 64-bit
application using the GCC 4.0.3 compiler suite including gfortran.
The version of acml is 3.5.0 gfortran64.
I do not encounter the segfaults when I compile R with R's b
15 matches
Mail list logo
