search for: __builtin_isnan

...e This is my first post to the list. I had experience installing and using Bioconductor on Linux and Windows systems but I am encountering problems installing Biobase on Solaris running on Sparc. The package compilation works fine, with only a warning warning: implicit declaration of function `__builtin_isnan' the help files are generated but in the end it fails with an error also related __builtin_isnan ** building package indices ... Error in dyn.load(file, DLLpath = DLLpath, ...) : unable to load shared library '/usr/local/lib/R/library/Biobase/libs/Biobase.so': ld.so.1: R: fatal: r...

...alize.o In file included from ../../src/include/Rinternals.h:921, from ../../src/include/Defn.h:72, from serialize.c:29: ../../src/include/Rinlinedfuns.h: In function `fmin2_int': ../../src/include/Rinlinedfuns.h:602: warning: implicit declaration of function `__builtin_isnan' [... and ...] gcc -std=gnu99 -L/usr/local/lib -o R.bin Rmain.o CConverters.o CommandLineArgs.o Rdynload.o Renviron.o RNG.o apply.o arithmetic.o apse.o array.o attrib.o base.o bind.o builtin.o character.o coerce.o colors.o complex.o connections.o context.o cov.o cum.o dcf.o datetime...

Hi, I've been trying to install the statnet package on my Solaris 10/Intel system. I've been having problems with one of the dependencies, sna. During the compile, it always fails and complains about __builtin_isnan (please see below for output). I have tried installing this using Sun Studio 12, as well as gcc4 from opencsw.org. I am thinking it may have to do with what R thinks is the default paths to libraries and include files, but I have no idea how those are controlled from within R (should I be setting e...

Hello, =20 I get this error when I try to install R-2.4.0 on Solaris 10 =20 Any Assistance would be greatly appreciated =20 The ./configure thing passed but then on gmake I get : =20 Undefined first referenced symbol in file __builtin_isnan arithmetic.o ld: fatal: Symbol referencing errors. No output written to R.bin collect2: ld returned 1 exit status gmake[3]: *** [R.bin] Error 1 gmake[3]: Leaving directory `/usr/local/R_HOME/R-2.4.0/src/main' gmake[2]: *** [R] Error 2 gmake[2]: Leaving directory `/us...

...to build under 64 bit (and I'm wondering if this might be part of our problem). Here is the output from the make... ld: warning: file /usr/local/lib/libiconv.so: attempted multiple inclusion of file Undefined first referenced symbol in file __builtin_isnan libR.a(plot.o) ld: fatal: Symbol referencing errors. No output written to R.bin collect2: ld returned 1 exit status make[3]: *** [R.bin] Error 1 make[3]: Leaving directory `/usr/local/src/R-2.9.2/src/main' make[2]: *** [R] Error 2 make[2]: Leaving directory `/usr/local/src/R...

...cap/gf7764-3.4.3+2/lib -lg2c -lm -lgcc_s > ../extra/zlib/libz.a ../extra/bzip2/libbz2.a ../extra/pcre/libpcre.a > ../extra/intl/libintl.a -lreadline -ltermcap -lnsl -lsocket -ldl -lm > Undefined first referenced > symbol in file > __builtin_isnan arithmetic.o > ld: fatal: Symbol referencing errors. No output written to R.bin > collect2: ld returned 1 exit status I've tried to look at the difference in outcomes in the old R-devel version -- if I touch arithmetic.c there and then type make I get a something...

...y_at_stats.ox.ac.uk> Date: Tue 10 Oct 2006 - 10:49:01 GMT Which Solaris is this? I am not seeing any problems with our Solaris 8 systems. Was the compiler built on that exact system? What gcc options were used (-std=gnu99, as recommended, for instance)? It looks like a system header problem: __builtin_isnan ought to be built in, not an external entry point. Since R does not use it, you need to trace through the headers to see why isnan is expanding to it. On Thu, 5 Oct 2006, roger koenker wrote: > We have a solaris/sparc machine that has been running an old version > of R-devel: Version 2.2....

...nix/libunix.a ./appl/libappl.a ../nmath/libnmath.a -L../../lib -lRblas -lg2c -lm -lgcc_s ./extra/zlib/libz.a ../extra/bzip2/libbz2.a ../extra/pcre/libpcre.a ./extra/intl/libintl.a -lnsl -lsocket -ldl -lm Undefined first referenced symbol in file __builtin_isnan arithmetic.o ld: fatal: Symbol referencing errors. No output written to R.bin collect2: ld returned 1 exit status make[3]: *** [R.bin] Error 1 make[3]: Leaving directory `/datos/java/temp/R-2.4.0/src/main' make[2]: *** [R] Error 2 make[2]: Leaving directory `/datos/java/temp...

...olaris2.10/3.4.2 -L/usr/ccs/bin -L/opt/sfw/lib -lg2c -lm -lgcc_s ./extra/zlib/libz.a ../extra/bzip2/libbz2.a ./extra/pcre/libpcre.a ../extra/intl/libintl.a -lreadline -lncurses -lnsl -lsocket -ldl -lm Undefined first referenced symbol in file __builtin_isnan arithmetic.o ld: fatal: Symbol referencing errors. No output written to R.bin collect2: ld returned 1 exit status gmake[3]: *** [R.bin] Error 1 gmake[3]: Leaving directory `/usr/local/R_HOME/R-2.4.0/src/main' gmake[2]: *** [R] Error 2 gmake[2]: Leaving directory `/us...

...e distinction between QNaN and SNaN. The default LLVM IR definition does not support this distinction. We seem to have an issue with isnan() in clang though. If you call isnan() you get a call to __isnan() which should be fine (assuming the library does the right thing), but we're translating __builtin_isnan() to x!=x. That's not what we should be doing if except_behavior isn't "ignore". > excess precision handling is missing from this list which matters for x87 and m68k fpu support and may matter for _Float16 implementations that fall back to _Float32 arithmetic. Yeah, we don...

...tand the error after trying to make: ######################################################## Undefined first referenced symbol in file libiconv_close libR.a(sysutils.o) libiconv_open libR.a(sysutils.o) __builtin_isnan libR.a(plot.o) libiconv libR.a(sysutils.o) ld: fatal: Symbol referencing errors. No output written to R.bin collect2: ld returned 1 exit status *** Error code 1 make: Fatal error: Command failed for target `R.bin' Current working directory /u/fox/b...

Hi all, I'm trying to put together a set of rules for how the various floating point semantic modes should be handled in clang. A lot of this information will be relevant to other front ends, but the details are necessarily bound to a front end implementation so I'm framing the discussion here in terms of clang. Other front ends can choose to follow clang or not. The existence of this set