similar to: R-1.8.0 + IBM VisualAge/C for AIX compiler

I am trying to build R with 64bit support so I can access more than 2GB of memory on an IBM running AIX. (IBM NightHawk II RS/6000 node with 16 64-bit, 375-MHz POWER3 CPUs and 32 GB of memory, if you want specifics) The 32bit install required little tweaking, but the 64 bit is sufficiently complicated that I thought I would report my findings here and ask for help with the latest (and hopefully

Hi all, today I tried to compile R in 64-bit mode on Linux on Power4. I used the following parameter with configure. ./configure -without-x CC='xlC' F77='xlf' CXX='xlC' CFLAGS='-q64 -g -qfullpath' FFLAGS='-q64 -g -qfullpath' CXXFLAGS='-q64 -g -qfullpath' MAIN_LDFLAGS='-q64 -g -qfullpath' LDFLAGS='-q64' SHLIB_CXXLDFLAGS='-q64

The bulk is on my forums - the final post for today is: Results to date: A. It looks like I am going to need a newer compiler for C - xlc/xlC V11 apparently does not understand this code: "/data/prj/cran/R-3.2.3/src/main/memory.c", line 2149.31: 1506-046 (S) Syntax error. I will have to check if R-devel has different code before asking for assistence. +2139 #ifdef

Hello, I'm trying to compile R (versions 1.6.0, 1.6.1, 1.6.2 and 1.7.0) on our IBM Power3 Machine for an external user. I always used to configure with ./configure --prefix=/scratch_tmp/harald/instala I've never achieved to compile 1.7.0 because it seems that a file called R.exp is missing (or maybe it's not well referenced on the makefile). Output of make: .... xlc_r

Hi all, With the bug in tre identified I am trying to move forward - one step at a time. As I am getting some errors that prevent make completing with version 3.2.3, and R-devel introduces new issues (that I will face when I get to them) I would appreciate some guidance with output of "make check" (of 3.1.3) and the final message I run into when trying to build 3.2.3. Maybe they

I am having a problem building OpenSSH on my AIX 4.3.3 box. It fails during the make with the following error: xlc -o ssh ssh.o sshconnect.o sshconnect1.o sshconnect2.o sshtty.o readconf.o clientloop.o -L. -Lopenbsd-compat/ -L/usr/local/ssl/lib -L/usr/local/lib -L/usr/local/lib -L/usr/athena/lib -L/usr/afsws/lib -blibpath:/usr/lib:/lib:/usr/local/lib:/usr/athena/lib -lssh

We can't run VisualAge Generator (2.X) retriving files from the samba server (AIX). (we receive smberror: ErrDos 282 ) It seems to require to read the extended attrib to find out the version of the file (and until now I can't realize what else). Is there any workaround or patch to get rid of it? Can Samba works fine with this kind of application? Thanks in advance, Andrea Capanema

My apologies if this is not the appropriate forum for this but I have posted twice to the ssh security list and have not received any replies. I would appreciated any help that anyone can offer. TIA ------- Ok, this is a repost from awhile back to which I received no replies. Originally, I was dealing with 3.4p1 but I am running into the same problem now with 3.5p1. I would greatly

https://bugzilla.mindrot.org/show_bug.cgi?id=2371 Bug ID: 2371 Summary: make check fails when using --without-openssl on AIX Product: Portable OpenSSH Version: 6.9p1 Hardware: Other OS: All Status: NEW Severity: normal Priority: P5 Component: Build system Assignee:

https://bugzilla.mindrot.org/show_bug.cgi?id=2371 Bug ID: 2371 Summary: make check fails when using --without-openssl on AIX Product: Portable OpenSSH Version: 6.9p1 Hardware: Other OS: All Status: NEW Severity: normal Priority: P5 Component: Build system Assignee:

While trying to switch a domain from an WinNT 4.0 SP ? to an AIX 4.3 with samba 2.2.8 with OS2/warp 4 clients we receive some unexpected errors. - we can log on to the new domain , run logon scripts, map network drives , store and retrive files , print to a Remote server using the printers shared by samba. - we can't run VisualAge Generator (2.X) retriving files from the samba server. (we

On Tue, Nov 24, 2015 at 12:10:12AM +0100, Jeroen Ooms wrote: > Currently it is all to easy for package authors to introduce a memory > leak or stack imbalance by calling Rf_error() or > R_CheckUserInterrupt() in a way that skips over the usual cleanup > steps. I have a more modest request: Please improve the documentation of exactly what Rf_error() does and how it should be used!

I encountered several strange issues when linking to R.dll on Windows and I wonder if anyone of the Windows savvy-folks here had seen some of the issues before and have some explanation. My Rserve links to R dynamic library. That works perfectly on unix boxes and worked fairly well with older MinGW and older R (<=1.7.1). What I do in fact is that I specify -L$(R_HOME)/bin -lR when linking.

Dear all, after trying to compile R on our IBM Power3/AIX 5.1 machine I've been able to run it correctly. First of all I would thank all who responded my mails. I explain here how I've done it: First of all, it seems that configure and some shared libraries of AIX does not work at the same time. I tried to configure & make with the following environment vars CC=xlc F77=xlf CCC=xlC

Hi. Just wanted to let you know I am getting close to packaging R for AIX in 64.bit mode. One comment - the libtool.m4 I see used is quite old. The one I have on my system is 2.4.6, and what I see in R says: I am hoping a new libtool will clean up most of the manual work now needed. # Which release of libtool.m4 was used? macro_version=2.2.6 macro_revision=1.3012 This may be all that is

After the recent discussion about future direction of the Mac OS X port, I was toying with the idea to make R a proper Mac OS X framework. There are several advantages: OS X locates frameworks automatically, therefore any program wishing to link against R has only to specify "-framework R" at link time. Furthermore versioning is supported, i.e. if a program is linked against R 1.7.1

Some issues with the recent R-devel (rsync today) on Darwin: 1) Recent R-devel is a bit misleading concerning the R-framework installation: A new option --enable-R-framework was introduced, but install-Rframework ignores its absence (or --disable-R-framework for that matter) and tries to install the framework anyway in / which fails just after the R itself was copied into /Versions/.... I

On 04-Jan-16 23:24, Michael Felt wrote: > The bulk is on my forums - the final post for today is: > > Results to date: > > A. It looks like I am going to need a newer compiler for C - xlc/xlC > V11 apparently does not understand this code: > > "/data/prj/cran/R-3.2.3/src/main/memory.c", line 2149.31: 1506-046 (S) > Syntax error. > > I will have to check

This email isn't asking for assistance, but I thought R-help readers would find it interesting. This week we offered a half-day introduction to R for researchers at Augsburg University. The response was astonishing. Although Augsburg has no medical faculty and no engineers, there was far too much demand, with interest from every faculty (barring theology, "for one small

To anyone following the Windows toolchain saga: The gcc 4.9.2 toolchain that is currently in Rtools33 has too many incompatibilities with existing code, so we won't be using it in the R 3.2.0 build. I will soon be uploading to CRAN a new version of Rtools33 that is very similar to Rtools32, containing gcc 4.6.3. We are continuing to work on the new toolchain, and hope to have it ready