Thank you for the report.
/* */ is standard C. simpleaffy is not a CRAN package: we test those with
enough flags (-Wall -pedantic) that the use of // is flagged and would get
reported to the maintainer/submitter.
On Tue, 30 Aug 2005, Jennifer Lai wrote:
> Hi,
> After getting some help from
Hi,
After getting some help from Portland Group, I was able to pass the
initial stage of building R with Portland Group Compiler on AMD Opeteron.
For anyone who is interested in building R with PG compiler, here is a
list of set flags used in config.site,
CC=/usr/pgi/linux86-64/6.0/bin/pgcc
Let us be clear: some things in config.log are designed to fail, so only
unexpected errors are a cause to look there. The regex.c warnings are
it seems from an over-zealous compiler.
The problems here seem to be the unknown use of .lo (which it seems to
have coped with) and a problem in the PG
I downloaded R-devel and compiled it with pgcc. This time, instead of
breaking in src/main, compilation breaks in src/modules with the
following error messages.
Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved.
Copyright 2000-2005, STMicroelectronics, Inc. All Rights Reserved.
regex.c is not our code, but from glibc. Could you please try R-devel
instead, which has a later version of glibc. Since 2.1.1 is not longer
part of the developement, we cannot help with that, but we can help wih
R-devel.
I see the later regex.c does use prototypes. But bitset is an integer
Hi,
Can anyone advise me on how to compile R with Portland Group
compiler on a Opeteron machine with Red Hat Enterprise Linux WS release
4 installed?
I've edit config.site file to pick portland group compilers instead of
gcc. Here is the list of modified flags:
CC=/usr/pgi/linux86-64/6.0/bi
