similar to: R configure.in makes bad alpha assumptions (PR#1676)

I would like to always use ${CC} for linking the main binary and the shlibs. Inspection of configure.in reveals that we currently deviate in the following cases: mainld shlibld aix[2-9]* ld ld alpha*osf* ${FC} -g -nofor_main -fpe3 ${FC} hpux* ${CC} ld Does anyone recall why we do not use ${CC} in these cases? Did anyone successfully build R on these platforms with ${CC} for

Dear all- I get the same problem in compiling R-1.3.0 on Tru64 Unix (OSF 5.0). Here is the final output of the ./configure R is now configured for alphaev67-dec-osf5.0 Source directory: . Installation directory: /usr/local C compiler: gcc -mieee -g -O2 C++ compiler: c++ -g -O2 FORTRAN compiler: f77 -fpe3 -g X11 support:

Has anyone achieved a current successful build of R 1.8 or 1.9 or earlier for HPUX Tru 64 OSF 5.1? There is no binary version of R for HPUX Tru 64 OSF 5.1. The R admin manual mentions that the native make fails on "Alpha/OSF (aka Tru 64)" and gnu make must be used instead. There are problems reported with building R versions around 1.4 from 2002 on R-devel, some of which were fixed with

This is a multipart MIME message. --==_Exmh_981436288450 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi ! I have problems compiling R successfully on a DEC-UINX 4.0E. I have applied the recommended config.site, which I enclose. As can be seen from the compilation log there are linking errors... I did a 'make check' which fails for the R

>>>>> Thomas Lumley writes: > On Fri, 1 Aug 1997, Kurt Hornik wrote: >> Thomas, >> >> Could you add the "-lf2c" at the end of the line >> @$(LD) $(SHLIBLDFLAGS) -o $(LIBNAME).so $(OBJS) >> in acepack's src-c/Makefile? >> >> I ran across an identical pow_dd problem recently with another package. >> Did we always need

Builds of the R-2.0.0 release have been considerably more successful at my site than previous releases. I now have it installed on these platforms: Apple PowerPC G3 267MHz GNU/Linux 2.4.19-4a (Yellow Dog Linux release 2.3 (Dayton)) Compaq Alpha Sierra OSF/1 5.1 Compaq/DEC Alpha OSF/1 4.0F Intel Itanium-2 GNU/Linux Red Hat Linux Advanced Server release 2.1AS (Derry) Intel Pentium II FreeBSD

Full_Name: Albrecht Gebhardt Version: 0.99.0 OS: alpha, osf4.0 Submission from: (NULL) (143.205.180.40) Im not sure if this is really correct, but it has proven to work. 1. It is always a good idea to add -std1 to DEC cc's flags to force strict ANSI language mode. It was neccessary for 0.90.x to compile, so I used it for 0.99.0 too 2. I'm not sure if -fpe3 is neccessary for DEC f77,

Hello, With regards to Peter's comment, I got R to compile on OSF 4.0C, though I'm a little behind on versions. I only have 0.63.3 and haven't found anything newer... All kidding regarding typos aside, I went through that floating point exception business on the Alpha and I just didn't have time to make it work. Someone tipped me on to f2c, which I had used with my (old gcc

Recently I reviewed my RPM spec files for DU 4.0, and noticed that I forgot to post some problems + patches: 1. ./configure fails to choose a PIC flag, I simply removed the AC_MSG_ERROR and it works. There is actually no PIC flag for DEC cc (with DU 4.0E) --- ./configure.in.alpha-patch Mon Aug 23 06:36:28 1999 +++ ./configure.in Sun Sep 12 17:38:27 1999 @@ -541,7 +541,9 @@

Batch: For me, batch in its present state is broken and useless. My primary need for batch is to produce a final output file of a session after I have worked out a sequence of procedures. I save my instructions in a file that I can source, then run it in batch to have a copy of input and output together. (If there was a log file (or dribble), this problem would be solved.) At present, there are

Hi again ! Thanks for the info on updating the config.site file which I have done. I have also added -lm in the Makeconf manually because this is needed explicitly for DEC cc. However, there are still a few problems when linking some of the files as you can see from the enclosed log. Ciao, Andreas ------------------------------------------------------- R-0.63.3>make make[1]: Entering

Hi all, The systems guys here in the stat dept don't seem to be able to compile R on the Dec Alphas or on the SGIs. Can anyone give them a hand? -Greg ------------------------------------------------------------------------------- Gregory R. Warnes | It is high time that the ideal of success warnes at biostat.washington.edu | be replaced by the ideal of service.

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

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

I am grateful for the advice of Douglas Bates on my earlier problem in making R-0.62.1, but I'm afraid I'm still having problems.... I have been installing the various updates to R for quite some time on my alpha, and it is only now that I have been having really severe problems. The three or 4 versions before 0.61.1 installed without error. For 0.61.1 I needed to install GNU make. For

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'

Dear all, I have some difficulty getting R-1.3.0 to run on the alpha, with osf4.0e (Tru64, or whatever they call it... :-) ). configure reports the following configuration: R is now configured for alphaev6-dec-osf4.0e Source directory: . Installation directory: /astro/local C compiler: gcc -mieee -g -O2 C++ compiler: c++ -g -O2 FORTRAN

Dear all, I have some difficulty getting R-1.3.0 to run on the alpha, with osf4.0e (Tru64, or whatever they call it... :-) ). configure reports the following configuration: R is now configured for alphaev6-dec-osf4.0e Source directory: . Installation directory: /astro/local C compiler: gcc -mieee -g -O2 C++ compiler: c++ -g -O2 FORTRAN

Last Friday my computer monitor was messed up by on-line patches update. I had to reinstall everything from the o.s. and all applications on top of it. I have downloaded R source from the official site. I have uncompressed the archive and ran the configure as root in /usr/local/bin. The configuration procedure dies writing: *configure: error: Neither an F77 compiler nor f2c found * but actually

On Sat, 21 Aug 2004 ivo_welch-rstat8783@mailblocks.com wrote: > > peter/brian: thank you for the help. i can now report that gentoo > amd64 can compile R just fine, too; it requires the f77 USE flag and a > gcc compiler rebuild first, though. I also went to gcc 3.4.1. my > segfault troubles earlier were caused by my use of f2c. > > suggestion: would it be possible to