Gabor Grothendieck writes:
> Could you enlarge this to include translations of the help files
> and documentation too so there is a single location that one
> can refer to? If this is already tracked somewhere else then
> just a link at the top would be enough.
>
As far as I know this ki
Could you enlarge this to include translations of the help files
and documentation too so there is a single location that one
can refer to? If this is already tracked somewhere else then
just a link at the top would be enough.
On 9/28/05, Fernando Henrique Ferraz P. da Rosa <[EMAIL PROTECTED]> wr
Dear R-devel & Translation Teams,
In order to monitor the progress of the translation for the
pt_BR team I wrote a script to summarize the status of the translations.
It wasn't difficult to extend it to the other languages so I decided to
set up a page with the summaries of the tra
On Thu, 2005-09-22 at 10:36 +0100, Prof Brian Ripley wrote:
> Probably because it is discussed in the R-admin manual as having
> previously appeared in Debian and being traced to an erroneous patch to
> the Lapack 3.0 sources.
You wouldn't happen to have more specific details on this, would you
Peter Dalgaard wrote:
> -L/usr/lib64 I think. I have
>
> #LAPACK_LIBS="-L/usr/lib64 -llapack"
>
> (commented out now) in config.site.
I'm sorry, it was my mistake. I forgot to install blas-devel where
libblas.so is defined as a symbolic link to the correct library version.
Since the confi
On Wed, Sep 28, 2005 at 10:59:39AM +0100, Prof Brian Ripley wrote:
>
> They _are_ `first class data types', atomic vectors, just like integers.
> The intent remains that their contents should not be interpreted, just as
> in the Green Book. One comsequential difference from other atomic vectors
José Matos <[EMAIL PROTECTED]> writes:
> Peter Dalgaard wrote:
>
> > Hmm. Doesn't look like it is actually working, though. Install
> > lapack-devel, configure --with-lapack, and make check dies with
> >
> > running code in 'base-Ex.R' ...make[4]: *** [base-Ex.Rout] Error 1
> > make[4]: Leaving
Peter Dalgaard wrote:
> Hmm. Doesn't look like it is actually working, though. Install
> lapack-devel, configure --with-lapack, and make check dies with
>
> running code in 'base-Ex.R' ...make[4]: *** [base-Ex.Rout] Error 1
> make[4]: Leaving directory `/home/pd/r-devel/BUILD/tests/Examples'
> ma
On Wed, 28 Sep 2005, Prof Brian Ripley wrote:
> I am unaware that gfortran or gcc4 exist as a MinGW binary for Windows.
> You mention Cygwin, but that is not a supported platform for R.
>
> There is a g95 binary for Windows.
At www.g95.org, but I found no installation instructions relevant to
Wi
On Tue, 27 Sep 2005 [EMAIL PROTECTED] wrote:
> I've been working with raw vectors quite a bit and was wondering if
> the R team might comment on where they see raw vector support going in
> the long run. Is the intent that 'raw' will eventually become a first
> class data type on the same level a
I am unaware that gfortran or gcc4 exist as a MinGW binary for Windows.
You mention Cygwin, but that is not a supported platform for R.
There is a g95 binary for Windows.
You can find how to link on Windows from the sources: most of the rules
are in src/gnuwin32/MkRules. I suspect all you need
Hi all,
(Originally posted to r-help)
I'm porting a package that I've worked on for OS X to Windows.
The package is written in F95 so I need to compile it with gfortran
and link it with gcc4.
I've been trying to build an R with gcc4 without luck so far. If there is
a binary of such a thing info
12 matches
Mail list logo