similar to: R-beta: Re: dse+redhat 4.2 problem

Displaying 20 results from an estimated 8000 matches similar to: "R-beta: Re: dse+redhat 4.2 problem"

2004 Feb 26
1
unable to install dse in mac OS X 10.3
I would like to request help with the installation of dse in raqua in mac os x 10.3. I get the following error message after the messages indicating that parts were successfully installed. I would be most grateful for a solution. ----------------------------------------- * Installing *source* package 'setRNG' ... ** R ** inst ** help >>> Building/Updating help pages for
2004 Feb 15
1
Error Installing dse Package
Hi there, I ran into some trouble trying to install the dse library on os 10.3 with RAqua as the installation of the dse1 package failed. On the R console I got the error message Warning message: Installation of package dse had non-zero exit status in: install.packages(ui.pkgs, CRAN = getOption(where), lib = .libPaths()[1]) > and the console of the os x said gcc -bundle -flat_namespace
1998 Feb 03
0
fortran Makefile
My library uses compiled code which I converted from fortran to C with f2c. I put copies of the same Makefile in the both dse/src and dse/src-c. (I'm not sure why, but I niavely assumed the same Makefile might work.) Now, I haven't tried the fortran version with R. But of course the first person (as far as I know) to actually try and use the package defaulted to compiling the fortran
1998 Jan 06
2
pow_ii
I was hoping fatal: relocation error: symbol not found: pow_ii: referenced in .../dsefor.so would disappear in R 0.6x, but it has not. I believe this is suppose to come from the f2c lib, but I seem to need just a couple of routines: nm -u dsefor.so Undefined symbols from dsefor.so: .umul pow_dd pow_ii pow_ri For my own purposes I could compile with fortran but that makes it much
2004 Mar 31
2
Failure to compile source packages in Debian
As of quite recently I experience failures to compile source packages. Messages like * Installing *source* package 'dse1' ... ** libs g77 -mieee-fp -fPIC -g -O2 -c dsefor.f -o dsefor.o gcc -shared -o dse1.so dsefor.o -L/usr/lib/gcc-lib/i486-linux/3.3.3 -L/usr/lib/gcc-lib/i486-linux/3.3.3/../../.. -lfrtbegin -lg2c-pic -lm -lgcc_s -L/usr/lib/R/bin -lR /usr/bin/ld: no se puede
2000 Dec 16
1
g2c library
Working on a Red Hat (not Mandrake) Linux and trying to load my library I get (sorry, can't copy it all, working remotely) gcc -shared -o ..... /user/bin/ld: cannot find -lg2c Does anyone know what the g2c library iss, and if I can download and compile it for Red Hat (I definitely didn't mean to type f2c in the above) Thanks Jonathan
1997 Aug 28
1
R-alpha: pow_ii
>> I'm a bit confused about this discussion, but since I don't have f2c on ... >A lot of Fortran code doesn't require any libf2c routines. When routines >are needed the most common ones are the exponentiation routines pow_dd, >pow_ii and pow_di (pow_ri is for single precision reals and so is less >needed in R, which uses double precision). However, *some* fortran
1998 Dec 03
1
which compiler
Hello, This is perhaps a little off-topic, but I am curious as to what compilers people use to compile R (under unix/linux). I am primarily interested in the use of egcs or gcc, g77 or f2c, etc. It seems most of the gcc interest and development is towards egcs, and while a gcc 2.8.1/g77 combination did work and compile R on my primary linux machine, it also managed to produce kernels that did
2000 May 25
9
problem on upgrading to RH6.2 (was problem with ts pack
plummer at iarc.fr said: > On 24-May-00 Prof Brian D Ripley wrote: > On Wed, 24 May 2000, Christian Posse wrote: > >> >> I just encountered a problem with the ts package: >> >> > > library(ts) >> Error in dyn.load(x, as.logical(local), > as.logical(now)) : >> unable to load shared library >> "/usr/ >
1999 Sep 26
1
install problem -- libg2c
Hi, there I'm totally new to this. I used to use SPLUS, but think maybe useful to try R at home. But seems it doesn't like me. I got error message says ld: cannot open -lg2c: No such file or directory My OS is openlinux 2.3. I use egcs-2.91.66. I searched under /lib/egcs-2.91.66/ but found no libg2c.a. There's only a libgcc.a. Thought maybe g77 people changed
1998 Apr 02
2
f2c
I have a problem with my dynamically loaded code in R not finding pow_ii, which for some time I thought was because library f2c is not on my Sparcstation. However, I have now been experiencing the same problem in Linux, with all the proper libraries in place. My incomplete understanding of elf and shared libraries does not help, but when compiling a complete program I usually muddle through.
1999 Sep 01
1
Problems compiling R65.0 (PR#262)
Hi, I appear to have a slight problem compiling R0.65.0 under Linux (slackware) using g77. By simply typing configure then make, I obtain a binary which when "ldd" does not contain the f2c library. I therefore cannot load any libraries containing fortran code (I obtain unresolved symbol messages from R.X11 and an unable to load shared library from dyn.load(file)). If I change the
1998 Oct 07
2
R-beta: R0.62.3 installation on RedHat 5.0
I have R-0.62.3 and RedHat 5.0 with fort77. At the office R is running but when I install a package, eg. 'akima' I get a message make: f77: Command not found 'R INSTALL library' does not accept fort77, but R installation checks f77/g77/fort77. Is there an easy way to edit some file and replace f77/g77 with fort77? At home I have the same R and Linux versions, but when
2000 Jul 07
1
multiply defined symbols (PR#597)
Full_Name: Peter Lucas Version: 1.1.0 OS: redHat 6.2 Linux Submission from: (NULL) (139.133.200.15) I tried to install R 1.1.0 on my i686 PC with Redhat 6.2 Linux on it. I am using fort77 with f2c. I am not able to build R, as libc.a contains regex.o, causing a conflict with src/main/regex.o. the ONEWS mentions that this problem was solved, but it obviously was not. I am not a real Unix hacker,
2000 Jun 28
1
R-1.1.0 - f2c in configure
When trying to build R-1.1.0, the configure script reported no Fortran compiler, even though '/usr/bin/f2c' was present, and R-1.0.1 had found and successfully used this. I traced this to an apparent typo in line 2067 of configure: for name in g77 fort77 f77 f90 xlf cf77 fc; do changing this to: for name in g77 fort77 f77 f90 xlf cf77 f2c; do allowed the script to 'find'
2004 Aug 29
1
Re: [R] R on gentoo amd64 (gcc 3.3.3) is unstable --- no!
Dear Dirk, I have had the exactly same problem like Ivo and his solution worked for me. Hence the USE=f77 flag is NOT a typo but a Gentoo quirk. As far as modifying the configure script is concerned, I believe that it is certainly possible to perform said check (if 'f77 --version == f2c' then die) only on x86_64 platforms. And I'd argue it is f2c's fault. AMD64 linux distros have
2000 Oct 31
1
Compiling R in Caldera Linux
I am new to Linux and its ways, and so I am having a bit of trouble compiling R. The system I am using is Caldera Open Linux 2.4. I have egcs and g77 version 2.91.66 installed and they seem to work fine. When I try to run the configure script for R, it quits at the test of g77 with an error "Can't find -lg2c". Does this error mean I am missing a library, and if so, which one?
2004 Aug 29
1
Re: [R] R on gentoo amd64 (gcc 3.3.3) is unstable --- no!
My appologies, this estimation is about right, I spent last week at COMPSTAT in prague and didn't follow the list closely. Inspite of this fact I believe my posting is not entirely out of date. regards Diman Todorov ------------------------------ You are 8 days behind the times -- take a look at the current R-devel. On Sun, 29 Aug 2004, Diman Todorov wrote: > Dear Dirk, > I
1999 Apr 01
1
PLATFORMS
Only three entries thus far. Please keep them coming in. -k NAME Martyn Plummer EMAIL plummer@iarc.fr VERSION 0.63.3 PLATFORM i386-unknown-linux SYSTEM Redhat 5.1 CC/FC/MAKE gcc/egcs-g77/make NAME Douglas Bates EMAIL bates@stat.wisc.edu VERSION 0.63.3 PLATFORM i386-unknown-linux SYSTEM Debian 2.1 CC/FC/MAKE egcs/g77/make NAME Thomas
2001 Feb 01
1
configure bug in R-1.2.1 and earlier (PR#836)
Unless I force the Fortran compiler through --with-g77, configure fails to find and use the installed g77. I would submit a patch for configure.in, but I can't quite follow the logic in configure.in. $ ./configure creating cache ./config.cache [...] checking for main in -lm... yes checking for g77... /usr/local/gnu/bin/g77 checking for fort77... (cached) /usr/local/gnu/bin/g77 checking for