similar to: bzip2 directory won't build on OSF1 due to C99 code and -std1 option (PR#7257)

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,

http://bugzilla.mindrot.org/show_bug.cgi?id=371 Summary: OpenSSH fails to build on Alpha True64 in cipher.c Product: Portable OpenSSH Version: -current Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org

<<insert bug report here>> ------------------------------------------------------ Error: R : Copyright 2002, The R Development Core Team Version 1.5.1 (2002-06-17) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type `license()' or `licence()' for distribution details. R is a collaborative project with

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)

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:

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.

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

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.

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

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:

PArdon the "newbie" nature of this question, but I *am* a samba newbie I'm trying to compile samba-1.9.18p6 on a DEC Alpha running OSF/1 V3.0 (I know it's old, but I'm stuck with it). I've modified the Makefile as follows... ># Add any optimisation or debugging flags here ># add -DSYSLOG for syslog support >FLAGS1 = -O -std1 -w >LIBS1 = and ># This

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

http://bugzilla.mindrot.org/show_bug.cgi?id=940 anenni at isisw.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|xmmap.c noequality compile |xmmap.c noequality compile |error on DigitalUNIX 4.0F |error on Digital UNIX 4.0F |PK7

Hello, I'm facing a rights issue on with Asterisk 11.3.0 running on CentOS release 5.8. Asterisk process is running with asterisk since it is define in asterisk.conf as following: runuser = asterisk rungroup = asterisk You can see asterisk proccess here: ps aux |egrep 'python|asterisk' root 11581 0.0 0.1 65940 600 ? S Apr17 0:00 /bin/sh /usr/sbin/safe_asterisk

Hi, I am going to be attempting a build of R for the alphas (our main need is to collate and present graphically, performance metrics we gather on our applications). We have: CC=cc, CXX=cxx, Fortran V5.51 (f77, f95), GNU make 3.80, Perl 5.8.4 I am hesitant to rebuild GCC on this platform, and would like to know if others have success in building R with native C, C++ and Fortran. I plan on

Hello, I am trying to build the R-2.11.1 software for university faculty to use in research projects on a DEC/Compaq/HP AlphaServer model GS160 16CPU/64GB memory running Tru64Unix aka OSF1 version 5.1B-5. Is it known whether it is possible to build the R-2.11.1 software on the platform I am using? In my attempts to build the R-2.11.1 software, I first used the native C and Fortran 77/90/95

I am building from source on RHEL 4 and have run into a problem while running "make check": running code in 'lapack.R' ...make[3]: *** [lapack.Rout] Error 1 make[3]: Leaving directory `/opt/R/R-2.9.1/tests' make[2]: *** [test-Specific] Error 2 make[2]: Leaving directory `/opt/R/R-2.9.1/tests' make[1]: *** [test-all-basics] Error 1 make[1]: Leaving

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