similar to: Problems with gcc-3.1 -O2 on Solaris

Displaying 20 results from an estimated 10000 matches similar to: "Problems with gcc-3.1 -O2 on Solaris"

2005 Jan 12
2
?"=" (Windows) (PR#7504)
?"=", ?"==", ?"!=", ?">=", and ?"<=" sends me to the documentation for ?help on Windows, while returning the correct documentation on Linux. Robert > version _ platform i386-pc-mingw32 arch i386 os mingw32 system i386, mingw32 status major 2 minor
2005 Mar 09
3
R-2.0.1 Gentoo g77 problem
Hello, I use Gentoo and I can't get R 2.0.1 to compile. I used the portage system, Gentoo's source package sytem, and after it uncompresses the source to R, it says that I don't have a fortran compiler. It told me to use f77 flag and re-emerge gcc, which I did with the f77 and fortran flags, but it still won't compile. Does anyone have any ideas? I suspect that gcc has changed
2000 Dec 22
1
rw1020 Rcmd INSTALL path\ deletes rw1020\library\* (PR#789)
The trailing backslash seems to be the culprit. After looking at rw1020\bin\INSTALL, I noticed $pkg =~ s/\/$//; which I assume is to strip the trailing slash from a package name before obtaining the package name and cleaning out its directory I added $pkg =~ s/\\$//; immediately after this line. Rerunning Rcmd INSTALL C:\rw1011\src\library\bqtl\ with that change seemed to work OK
2002 Jul 17
2
Build on Solaris 8 gcc-3.1 fails make check
Dear R-help, I am trying to build R-1.5.1 on a Sun Blade 100 (sparc). It fails make check when var(1) returns NaN instead of NA. Using gcc-2.95.3 from sunfreeware.com, the build succeeds and passes make check I have: Solaris 8 gcc-3.1 (built on that machine from sources and installed in /usr/local/gcc-3.1 with binaries symlink'ed to /usr/local/bin) A synopsis is at the bottom of
2002 Jul 17
2
Build on Solaris 8 gcc-3.1 fails make check
Dear R-help, I am trying to build R-1.5.1 on a Sun Blade 100 (sparc). It fails make check when var(1) returns NaN instead of NA. Using gcc-2.95.3 from sunfreeware.com, the build succeeds and passes make check I have: Solaris 8 gcc-3.1 (built on that machine from sources and installed in /usr/local/gcc-3.1 with binaries symlink'ed to /usr/local/bin) A synopsis is at the bottom of
2005 Jan 11
1
Nested ifelse - is there a better way?
Dear r-help, I'm interested in finding a better way to add a column to a data frame when calculating the new column requires more than one conditional. For example, if I wanted to associate a character string in {"Pos","Neg","Zero"} with each number in the following data frame: > d <- data.frame(num = -2:2) > d num 1 -2 2 -1 3 0 4 1 5 2 I
2000 Jul 26
3
Correlation matrices
Hello, are there any good methods in R that will test if two correlation matrices (obtained in different ways) are equal? Something better than the Mantel test would be preferable. Regards, Patrik Waldmann -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info",
2004 Oct 06
3
possible help.start() bug
I have compiled R 2.0.0 for my gentoo desktop and have found this problem: help.start() will work correcly if mozilla is already started, will fail if mozilla is not. Error message: > help.start() Making links in per-session dir ... If /usr/bin/mozilla is already running, it is *not* restarted, and you must switch to its window. Otherwise, be patient ... > No running windows found
2000 Mar 07
2
lm(rnorm(1000)~rnorm(1000)) kills rw1000 (PR#476)
First: R core: (Thank You!)^HUGE_VAL Now, down to business: In a loop or in repeated command lines: system.time(lm(rnorm(1000)~rnorm(1000))) ( or lm(rnorm(1000)~rnorm(1000))$coef ) fails after several iterations with the Windows message 'This program has performed an illegal operation and will be shut down. If the problem persists, please contact the vendor'. clicking on DETAILS
2000 Mar 26
1
matlines, matpoints don't follow prototype (PR#506)
The Blue Book allows the 'type' argument to be used in matpoints and matlines. matlines(x, y, type="l", lty=1:5, pch=, col=1:4) R-1.0.0 does not. Thus, type="h", "b", must be invoked thru matplot( x, y, type = "h", add=TRUE) For the sake of consistency with S, it would be nice to have matlines defined as: "matlines" <-
1999 Nov 11
2
dimname'less array breaks apply (PR#318)
<<insert bug report here>> > apply(array(1:20,c(2,2,5)),2:3,function(x) x) Error: length of dimnames must match that of dims > Changing: dimnames = if (is.null(dn.ans)) list(ans.names, NULL) else c(list(ans.names), dn.ans) To: dimnames = if (length(dn)==0) NULL else if (is.null(dn.ans)) list(ans.names, NULL) else c(list(ans.names), dn.ans) seems to fix this. Chuck
2001 Nov 29
1
rug(x) clip warning incorrect if par("xlog")==TRUE (PR#1188)
To wit: > plot(1:2,1:2,log="x") > rug(1:2) # should not warn Warning message: some values will be clipped in: rug(1:2) > plot(1:2,1:2,log="x") > rug(c(0,.1,.2)) # should warn, but does not > I believe this fixes the problem: % diff -c /tmp/orig.rug.R /tmp/cberry.rug.R *** /tmp/orig.rug.R Thu Nov 29 12:59:00 2001 --- /tmp/cberry.rug.R Thu Nov 29
2000 Mar 13
1
plot(1:10,c(1)$nothing) yields index plot (PR#482)
<<insert bug report here>> IMHO, plot(x,c(1)$nothing) should fail or at least issue a warning. Instead it produces an index plot of the first argument, i.e. plot(x) Chuck Berry --please do not edit the information below-- Version: platform = sparc-sun-solaris2.7 arch = sparc os = solaris2.7 system = sparc, solaris2.7 status = Patched major = 1 minor = 0.0 year = 2000
2000 Nov 08
1
substitute(x$y)) corrupts 'y' component (PR#731)
viz. > (function(x,y=a) substitute(x$y))(x) x$a > (function(x,y=a) substitute(x$y))(list(y=1:3)) list(y = 1:3)$a > (function(x,y) eval(substitute(substitute(y))))(x=list(y=1:3),y=x$y) list(y = 1:3)$x$y The behavior I expect and want is like that in Splus 3.4: > (function(x,y=a) substitute(x$y))(x) x$y > (function(x,y=a) substitute(x$y))(list(y=1:3)) list(y = 1:3)$y >
2009 Apr 30
1
How to know what device I am using
Some years ago I wrote a plotting routine that was run on both Linux & Windows computers. There were some differences in the way the plot looked from the windows device and the X11 device. To ensure consistency I used getOption("device")) and made some changes to the plotting if the windows device was being used. Using this routine again, years later, I now notice that
1998 Aug 14
1
R-beta: ld problem/SunOS/gcc/g77
In trying to compile R-0.62.2 on my SPARC SunOS: tajo% uname -a SunOS tajo 4.1.3_U1 1 sun4m with gcc/g77, I ran into gcc -o R.binary [deleted] ../lib/libmath.a -L/usr/openwin/lib -lX11 -ldl -ltermcap -lm -lf2c collect2: ld returned 2 exit status ld: /lib/libm.a(lgamma.o): _gamma: multiply defined ld: /lib/libm.a(lgamma.o): _lgamma: multiply defined *** Error code 1 make: Fatal error:
2001 Jun 18
1
"[.data.frame" allows un-named 3rd subscript (PR#989)
Since the Extract page has usage as: x[i, j, ... , drop=TRUE] I would expect that 'drop=' would need to be given to the third 'subscript' > diag(4)[ , 4 , 4 ] # Forgot 'drop=' or added extra ',' Error in diag(4)[, 4, 4] : incorrect number of dimensions > > as.data.frame( diag(4) )[ , 4 , 4 ] # should return error, right? [1] 0 0 0 1 Also note:
2001 Oct 08
1
NA as names of vector from subscripted matrix == bug ?
Is this a bug? > matrix(1:4,nc=2,dimnames=list(1:2,1:2))[c(1,3)] 1 NA 1 3 It has some annoying consequences, e.g. > median( matrix(1:9,nc=3,dimnames=list(1:3,1:3))[1,,drop=F] ) NA 4 > The above was for Version: platform = sparc-sun-solaris2.7 arch = sparc os = solaris2.7 system = sparc, solaris2.7 status = major = 1 minor = 3.0 year = 2001 month = 06 day = 22
2002 Apr 05
1
randomForest() segfaults under Solaris(SPARC) 2.7
Invocation of randomForest() using the iris example in the help file crashes R with a segmentation fault. This happens on all of our ultraSPARC machines running Solaris 2.7. We're using R-1.4.1, compiled using Sun cc and f77 and the flags: CC=cc CFLAGS="-xO5 -xlibmil -dalign" FC=f77 FFLAGS="-xO5 -xlibmil -dalign" "make check" runs withour errors, and R has been
2000 Sep 29
2
all.equal.list() sometimes fails with unnamed and named components (PR#674)
examples: 1) Fails to report that components 2 and 3 differ all.equal(list(1,2,3,zap=1),list(1,3,4,zap=2)) [1] "Component zap: Mean relative difference: 1 2) Incorrectly asserts all are equal when components 2 and 3 differ > all.equal(list(1,2,3,zap=1),list(1,3,4,zap=1)) [1] TRUE 3) Removing named component reveals differences: > all.equal(list(1,2,3,1),list(1,3,4,1)) [1]