similar to: R-2.2.0: malloc probelm in regex code (PR#8287)

Full_Name: Michael Hoffman Version: 2.0.0-beta-20041001 OS: OSF1 V5.1 Submission from: (NULL) (193.62.199.8) Hello. Building R 2.0.0-beta-20041001 on OSF1 V5.1 failed because the default configure sets R_XTRA_CFLAGS to "-std1 -ieee_with_inexact." The bzip2 directory includes C99 code that requires -std1 to not be set in order to compile. This halts the overall build process.

Full_Name: Gordon Lack Version: 2.4.0 OS: OSF1 v5.1 Submission from: (NULL) (198.28.92.5) Changes to the bin/R front-end interlude script at 2.4.0 (cf: 2.2.0) have broken R on (Dec/Compaq/HP) OSF1. There are 3 occurrences of "${@}", but this is the incorrect syntax for adding $@, as on older Bourne shells this will add an empty (but present) parameter. The result is that the build

R ran find on our Sun until it was stolen. I have now set up R on one of our Dec Alphas OSF1 V4.0 386. R-0.49 configures builds and runs fine except that the glm command crashes R. R-0.60.1 configures builds and runs until a cis entered. I think the problem is the floating point conventions but before I get in over my head a question Has anyone used glm successfully on Alphas OSF1 V4.0 386?

I could not find this question anywhere, but I apologize if it is and I just missed it. Running an Alpha, OSF1 V5.1 1885 configure went fine. compile failed: cc -I. -I. -g -DHAVE_CONFIG_H -I./popt -c lib/getaddrinfo.c -o lib/getaddrinfo.o cc: Error: lib/getaddrinfo.c, line 182: In this statement, "EAI_MAX" is not declared. (undeclared) if (ecode < 0 || ecode > EAI_MAX)

Full_Name: Kjetil Kjernsmo Version: 1.0.1 OS: osf1 Submission from: (NULL) (129.240.28.227) Ouch, another obscure bug... I just had a bus error crash, with a core dump, a small one this time. Usual <URL:http://www.astro.uio.no/~kjetikj/tmp/core>. I had done a few simulations, and done a chisq.test() on them. These simulations also write about 190MB's to file, but I have no idea whether

Dear R Development Core Team, I've been trying to install R ver. 0.64.0 on a Dec-Alpha machine w/OSF1. A couple of things go wrong. After I type "make", the installation process bombs while trying to compile the R.binary. It reports the following: f77 -o ../../bin/R.binary {*** for brevity, I've deleted the filenames printed here ***} ld:

Hi, I have built R 2.1.1 on Solaris and OSF1, and used the operating system's native compiler set. This worked fine. However, when I try using install.packages() it insists on using g77 etc., which doesn't exist on those systems. How can I specify which compilers to use? What about other compile-time options like LDFLAGS etc.? NB! Please include me in the CC list, since I'm not a

Full_Name: John Garvin Version: 1.9.0 OS: OSF1 Alpha ev6 Submission from: (NULL) (128.42.129.78) I configured R 1.9.0 with --enable-R-shlib on Alpha. 'make check' fails with an unresolved symbol. Here's the relevant output: running code in 'reg-tests-1.R' ...529442:/home/garvin/research/tel/R-alpha/unpatched/R-1.9.0/lib/R/bin/R.bin: /sbin/loader: Fatal Error: call to

Hi, We have 2 problems with rsync over ssh that we haven't been able to replicate all the time. Basically, we have a developement server running Solaris 2.5.1 and another running Solaris 2.6, the development tree is shared via nfs. When minor changes are made they are distibuted to various mirror sites via a perl script which does some checks (path, etc) and runs 'rsync -e ssh ....'

Full_Name: Kjetil Kjernsmo Version: 1.0.1 OS: osf1 Submission from: (NULL) (129.240.28.227) Hello! I'm getting strange numbers from a random number generation function again. I was wondering if it could be the same problem as I reported in (PR#439). I'm using the functions (some comments deleted for brevity): qamp <- function(p, type=c("point", "nolens")) {

http://bugzilla.mindrot.org/show_bug.cgi?id=319 Summary: Privilege Separation failing on OSF1 v5.1 Product: Portable OpenSSH Version: -current Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

First I tried 'setenv R_SHELL /usr/local/bin/bash', as bash is the weapon of choice for the faculty wishing to use R, then ran ./configure as before. The ./configure output line using as R_SHELL for scripts ... /usr/local/bin/bash would seem to indicate that the R_SHELL environment variable was recognized and acknowledged. However, I got the same build error: gnumake[2]: Entering

Does anyone know why I cannot compile the 3.0.0 release of Samba on Compaq Tru64 4.0f (aka DEC OSF1 version 4.0f) I have read the mailing list quite a lot and have done the chmod adjustment to the "install-sh" file, and then ran "./configure" I am not using gcc nor am I using GNU make, I am using the default compiler and make supplied with the OS. the "./configure"

http://bugzilla.mindrot.org/show_bug.cgi?id=745 Summary: agent-ptrace.sh fails Product: Portable OpenSSH Version: -current Platform: All OS/Version: OSF/1 Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-bugs at mindrot.org ReportedBy: mmokrejs at

Running on an Alpha machine which reports (uname -a) OSF1 bsdx01.bs.ehu.es V4.0 878 alpha and using the binary distribution put together by Albrecht Gebhardt (in http://cran.at.r-project.org/bin/osf/osf4.0/tar/alpha_ev5/) I obtain core dumps whenever I try to use package rpart. I have R REMOVE'd the rpart package, downloaded the source rpart_1.0-7.tar from CRAN and

Hello, I have following setup: User homedir are on server B and I have samba running on server A and B (B is dec/osf1, A is HPUX). In Luke's reply to "Spiros B" (tue 12 aug 97) he said: > because (and this is the bit about the home.map support that i don't > exactly understand, and don't quite follow) when you do a domain logon > to server A, the home.map support

Full_Name: Kjetil Kjernsmo Version: Version 1.0.0 OS: osf1 Submission from: (NULL) (129.240.28.227) Hello again! This is a follow-up to my message on R-help about a problem with match.arg() I have a little more on the topic, but not much really. First, it was not entirely true what I wrote in r-help that I call match.arg() in my ramp(), because ramp() just calls qamp() with runif() as

I am stuck in the installation of "R" on ALPHA runing OSF1/V5.1 for individual use. When I ran "./configure CC=cc F77=f77 Make=gmake ", the following message came out, 506426:/usr/users/1/mwang2/R/R-2.1.1/bin/exec/R: /sbin/loader: Error: libreadline.so.4: symbol "tgetflag" unresolved 506426:/usr/users/1/mwang2/R/R-2.1.1/bin/exec/R: /sbin/loader: Fatal Error: Load

I tried configuring Samba 2.0.7pre4 on a OSF1 machine (actually a DEC Alpha running Digital Unix 4.0d) with --with-utmp. The autoconf system sets the variable HAVE_UTMPX_H The linking of smbd aborts with the message ---------------------------------------------------------- ld: Unresolved: getutmpx utmpxname updwtmpx *** Exit 1 ---------------------------------------------------------- If I

Dear R-users, I currently have trouble in trying to compile R-1.3.0-patched on Compaq OSF1. -------- >uname -a OSF1 adenine.fysik.dtu.dk V4.0 1229 alpha -------- The 'configure' step ended seemingly corretly: ----------------------- R is now configured for alphaev6-dec-osf4.0f Source directory: . Installation directory: /home/adenine/sysman/laurent/share/ C