similar to: R-beta: Compiling on HPUX 9.05 and DEC alpha OSF1

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 had some trouble compiling the new R version on my Alpha: make[2]: Entering directory `/usr2/local/R/src/graphics' cc -ieee_with_inexact -O -Olimit 2000 -I/usr/local/include -I../include -c gdevice.c cc -ieee_with_inexact -O -Olimit 2000 -I/usr/local/include -I../include -c graphics.c cc: Error: graphics.c, line 808: An unexpected newline character is present in a string literal.

Hi, I had some trouble compiling the new R version on my Alpha: make[2]: Entering directory `/usr2/local/R/src/graphics' cc -ieee_with_inexact -O -Olimit 2000 -I/usr/local/include -I../include -c gdevice.c cc -ieee_with_inexact -O -Olimit 2000 -I/usr/local/include -I../include -c graphics.c cc: Error: graphics.c, line 808: An unexpected newline character is present in a string literal.

HP_UX 10.20 / SAMBA2.0.6 / gcc Compiles just fine. Run the "testparm /opt/samba/lib/smb.conf" command and get the following error . . . "/usr/lib/dld.sl: Unresolved symbol: vsnprintf (code) from testparm Abort (coredump)" What are the pre-requisite(s) for libraries for Samba to function or is this a known error / fix. Please, could someone respond with a push in the right

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?

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.

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:

> I had some trouble compiling the new R version on my Alpha: > > make[2]: Entering directory `/usr2/local/R/src/graphics' > cc -ieee_with_inexact -O -Olimit 2000 -I/usr/local/include -I../include -c > gdevice.c > cc -ieee_with_inexact -O -Olimit 2000 -I/usr/local/include -I../include -c > graphics.c > cc: Error: graphics.c, line 808: An unexpected newline

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

I'm having trouble compiling and installing R as a shared library on Alpha/OSF1. I used ./configure --enable-R-shlib SHLIB_CXXLDFLAGS=-L/lib/cmplrs/cxx (Using configure with --enable-R-shlib alone generated "Could not determine SHLIB_CXXLDFLAGS" errors.) make and everything else were done as specified in the documentation. It compiled everything without visible problems, but on

Hi, I have a problem with Samba on an OSF1 v4.0d machine. I get an "INTERNAL ERROR" and a core dump when trying to connect to a share from an NT 4.0 SP3 or W95 machine. I configured Samba to use encrypted password and I set the parameter "security=user". My Samba server is in a workgroup on its own, no PDC and BDCs around. I can see it in my Computer Neighborhood from the NT

>Date: Tue, 8 Dec 1998 11:00:42 -0500 (EST) >From: Rob Naccarato <rob@sheridanc.on.ca> >To: samba@samba.org >Subject: Can't connect to shares w/2.0beta3 on OSF1 > > >I was running 1.9.18p10 on a test DEC Unix 4.0d box here and I decided to >give 2.0beta3 a try. For some reason, I cannot connect to any of the >server's >shares or even get a list of

Hi, I have managed to test this same transfer reliably with the Linux boxes and open-ssh, but I am in trouble with the OSF1 4.0 (Digital Unix) being the server sending files from a single directory to the HP/UX 11 - being the client The 'sshd2' (and ssh2) in both ends is installed as root (and starts probably from 'rc') The 'rsync' (2.4.6) in both end is just

Is the following (from configure.in) intended: *-dec-osf*) if test ! -z "USE_SIA" ; then AC_MSG_CHECKING(for Digital Unix Security Integration Architecture) should that be "$USE_SIA" or similar or what is the point of testing a constant string for being zero length... The reason I ask is the for complex reasons we don't want SIA enabled on Tru64 since it breaks some

http://bugzilla.mindrot.org/show_bug.cgi?id=319 ------- Additional Comments From mouring at eviladmin.org 2002-06-29 02:59 ------- Created an attachment (id=120) Sounds like an SIA issue w/ privsep. Does this fix it? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

OS: Tru64 5.1 OpenSSH version: 3.2.2p1 and higher. Problem: after upgrading sshd my servers no longer forward X11 connections. I ran the server as 'sshd -d' and saw that the server was successfully creating and binding the IPV6 socket but failing to bind the IPV4 socket. The error message is: Bind to port 22 on 0.0.0.0 failed: Address already in use. Also, when channels.c tries to open

Digital Alpha (various), Digital UNIX V4.0[EF], R-1.0.0, gcc, f77 When using batch mode with the save option, an error message is issued. However [I have just discovered that] it appears that the operation does complete, i.e. the .RData file is saved successfully. The main problem is that the return code is non-zero (and so it is impossible to distinguish this "non-error" from some

Hi there ! I just solved the problem that produced following error in smb.log file: 'check_access_allowed_for_current_user: The process is no longer waiting!' Since nobody gave me any help I had to dig this out myself :-) This error happens if two programs hold more than 10 same files simultaneously open through Samba and check_access_allowed_for_current_user() gets called. And this