search for: cxxcpp

....4 in an insulated directory for use with my llvm installation. However, I am not sure I am configuring properly. The gcc-4.2.4 installation is in /pkg/bin/gcc-4.2.4. Here is my config line: ../llvm-2.5/configure --prefix=/pkg/bin/llvm/ CC=/pkg/bin/gcc-4.2.4/bin/gcc CXX=/pkg/bin/gcc-4.2.4/bin/g++ CXXCPP=/pkg/bin/gcc-4.2.4/bin/cpp LDFLAGS=-L /pkg/bin/gcc-4.2.4/lib64/ CXXFLAGS=-I/pkg/bin/gcc-4.2.4/include/c++/4.2.4/ CPPFLAGS=-I/pkg/bin/gcc-4.2.4/include/ I am trying to specify all the appropriate environment variables for using the non-default gcc. However, it is likely that I have made an error o...

...ang version 3.7.0 (git 718825a8666acd9ceaab70fc7868332f20e2758f) Target: x86_64-unknown-linux-gnu Thread model: posix Compiled: ../configure --prefix=<..> --enable-optimized --with-binutils-include=<..> --disable-terminfo --enable-bindings=none CC=gcc CXX=g++ 'CPP=gcc -E' 'CXXCPP=g++ -E' Cheers, david - - - [1] http://davidlt.web.cern.ch/davidlt/vault/vpp_generated.ii.xz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: Message signed with OpenPGP using GPGMail URL: &l...

...n of gcc-4.2.4, which is located in /pkg/bin/gcc-4.2.4. Perhaps someone has done something similar and can provide me a working example? Details: *** llvm-2.5 configured to use gcc-4.2.4: $ ../llvm-2.5/configure --prefix=/pkg/bin/llvm/ CC=/pkg/bin/gcc-4.2.4/bin/gcc CXX=/pkg/bin/gcc-4.2.4/bin/g++ CXXCPP=/pkg/bin/gcc-4.2.4/bin/cpp LDFLAGS=-L/pkg/bin/gcc-4.2.4/lib64/ CXXFLAGS=-I/pkg/bin/gcc-4.2.4/include/c++/4.2.4/ CPPFLAGS=-I/pkg/bin/gcc-4.2.4/include/ llvm-2.5 build: $ make tools-only error: make[1]: Entering directory `/pkg/build/llvm/llvm-obj/lib/VMCore' llvm[1]: Building Intrinsics.gen....

...use with my llvm > installation. > > However, I am not sure I am configuring properly. The gcc-4.2.4 > installation is in /pkg/bin/gcc-4.2.4. Here is my config line: > > ../llvm-2.5/configure --prefix=/pkg/bin/llvm/ CC=/pkg/bin/gcc-4.2.4/bin/gcc > CXX=/pkg/bin/gcc-4.2.4/bin/g++ CXXCPP=/pkg/bin/gcc-4.2.4/bin/cpp LDFLAGS=-L > /pkg/bin/gcc-4.2.4/lib64/ CXXFLAGS=-I/pkg/bin/gcc-4.2.4/include/c++/4.2.4/ > CPPFLAGS=-I/pkg/bin/gcc-4.2.4/include/ > > I am trying to specify all the appropriate environment variables for using > the non-default gcc. However, it is likely tha...

...it has been on other platforms where available since R 3.6.0: the default toolchain on Windows was defaulting to C++98). DEPRECATED AND DEFUNCT: * Support for specifying C++98 in package installation is deprecated. * Support in R CMD config for F77, FCPIFCPLAGS, CPP, CXXCPP and CXX98 and similar is deprecated. (CPP is found from the system make and may well not be set.) Use $CC -E and $CXX -E instead of CPP and CXXCPP. BUG FIXES: * runmed(x, *) when x contains missing values now works consistently for both algorithm="Stuetzle&quo...

...it has been on other platforms where available since R 3.6.0: the default toolchain on Windows was defaulting to C++98). DEPRECATED AND DEFUNCT: * Support for specifying C++98 in package installation is deprecated. * Support in R CMD config for F77, FCPIFCPLAGS, CPP, CXXCPP and CXX98 and similar is deprecated. (CPP is found from the system make and may well not be set.) Use $CC -E and $CXX -E instead of CPP and CXXCPP. BUG FIXES: * runmed(x, *) when x contains missing values now works consistently for both algorithm="Stuetzle&quo...

...it has been on other platforms where available since R 3.6.0: the default toolchain on Windows was defaulting to C++98). DEPRECATED AND DEFUNCT: * Support for specifying C++98 in package installation is deprecated. * Support in R CMD config for F77, FCPIFCPLAGS, CPP, CXXCPP and CXX98 and similar is deprecated. (CPP is found from the system make and may well not be set.) Use $CC -E and $CXX -E instead of CPP and CXXCPP. BUG FIXES: * runmed(x, *) when x contains missing values now works consistently for both algorithm="Stuetzle&quo...

...ere available since R 3.6.0: the > default toolchain on Windows was defaulting to C++98). > > DEPRECATED AND DEFUNCT: > > * Support for specifying C++98 in package installation is > deprecated. > > * Support in R CMD config for F77, FCPIFCPLAGS, CPP, CXXCPP and > CXX98 and similar is deprecated. (CPP is found from the system > make and may well not be set.) > > Use $CC -E and $CXX -E instead of CPP and CXXCPP. > > BUG FIXES: > > * runmed(x, *) when x contains missing values now works > consi...

...t supported by Apple's GCC (4.2.1). When the code runs on a linux cluster it compiles with openmp and runs no problem./ *makevars file* CC = gcc -arch x86_64 -std=gnu99 CFLAGS = -g -O2 $(LTO) /# with -O2 we compile fine / CPICFLAGS = -fPIC CPPFLAGS = -I/usr/local/include CXX = g++ -arch x86_64 CXXCPP = g++ -arch x86_64 -E CXXFLAGS = -g $(LTO) CXXPICFLAGS = -fPIC ... compiles and installs no problem. However, if I remove the -O (or use -O0, -O1) it fails with the following error ** preparing package for lazy loading ** help *** installing help indices ** building package indices ** testing if...

...where available since R 3.6.0: the > default toolchain on Windows was defaulting to C++98). > > DEPRECATED AND DEFUNCT: > > * Support for specifying C++98 in package installation is > deprecated. > > * Support in R CMD config for F77, FCPIFCPLAGS, CPP, CXXCPP and > CXX98 and similar is deprecated. (CPP is found from the system > make and may well not be set.) > > Use $CC -E and $CXX -E instead of CPP and CXXCPP. > > BUG FIXES: > > * runmed(x, *) when x contains missing values now works > consiste...

...> default toolchain on Windows was defaulting to C++98). > > > > DEPRECATED AND DEFUNCT: > > > > * Support for specifying C++98 in package installation is > > deprecated. > > > > * Support in R CMD config for F77, FCPIFCPLAGS, CPP, CXXCPP and > > CXX98 and similar is deprecated. (CPP is found from the system > > make and may well not be set.) > > > > Use $CC -E and $CXX -E instead of CPP and CXXCPP. > > > > BUG FIXES: > > > > * runmed(x, *) when x contains miss...

...3 | R Under development (unstable) (2017-04-18 r72542) | Platform: x86_64-pc-linux-gnu (64-bit) | Running under: Arch Linux Maybe you can share with us how you configure the build of R-devel? I tend to locally build every week or so and I have the following on Ubuntu 16.10: CXX = ccache g++ CXXCPP = $(CXX) -E CXXFLAGS = -ggdb -pipe -Wall -pedantic $(LTO) CXXPICFLAGS = -fpic CXX98 = ccache g++ CXX98FLAGS = -ggdb -pipe -Wall -pedantic CXX98PICFLAGS = -fpic CXX98STD = -std=gnu++98 CXX11 = ccache g++ CXX11FLAGS = -ggdb -pipe -Wall -pedantic CXX11PICFLAGS = -fpic CXX11STD = -s...

Hi, > $ ../llvm-2.5/configure --prefix=/pkg/bin/llvm/ > CC=/pkg/bin/gcc-4.2.4/bin/gcc CXX=/pkg/bin/gcc-4.2.4/bin/g++ > CXXCPP=/pkg/bin/gcc-4.2.4/bin/cpp LDFLAGS=-L/pkg/bin/gcc-4.2.4/lib64/ > CXXFLAGS=-I/pkg/bin/gcc-4.2.4/include/c++/4.2.4/ > CPPFLAGS=-I/pkg/bin/gcc-4.2.4/include/ how about: export PATH=/pkg/bin/:$PATH ../llvm-2.5/configure --prefix=/pkg/bin/llvm/ instead? Ciao, Duncan.

...ariables. ## ## ---------------- ## ac_cv_build=powerpc-apple-darwin8.11.0 ac_cv_env_CCC_set= ac_cv_env_CCC_value= ac_cv_env_CC_set= ac_cv_env_CC_value= ac_cv_env_CFLAGS_set= ac_cv_env_CFLAGS_value= ac_cv_env_CPPFLAGS_set= ac_cv_env_CPPFLAGS_value= ac_cv_env_CPP_set= ac_cv_env_CPP_value= ac_cv_env_CXXCPP_set= ac_cv_env_CXXCPP_value= ac_cv_env_CXXFLAGS_set= ac_cv_env_CXXFLAGS_value= ac_cv_env_CXX_set= ac_cv_env_CXX_value= ac_cv_env_F77_set= ac_cv_env_F77_value= ac_cv_env_FFLAGS_set= ac_cv_env_FFLAGS_value= ac_cv_env_LDFLAGS_set=set ac_cv_env_LDFLAGS_value=-flat-namespace ac_cv_env_YACC_set= ac_cv_en...

Morten Ofstad wrote: >> Hi, >> >> There's no HAVE_RAND48 symbol provided by autoconf. You'll have to >> add the appropriate check to autoconf/configure.ac before we can take >> this patch. I installed autoconf with cygwin now and I think I've managed to do this right now -- there are some strange problems with running the AutoRegen.sh script, so I

...ables See `config.log' for more details. ## ---------------- ## ## Cache variables. ## ## ---------------- ## ac_cv_env_CC_set= ac_cv_env_CC_value= ac_cv_env_CFLAGS_set= ac_cv_env_CFLAGS_value= ac_cv_env_CPPFLAGS_set= ac_cv_env_CPPFLAGS_value= ac_cv_env_CPP_set= ac_cv_env_CPP_value= ac_cv_env_CXXCPP_set= ac_cv_env_CXXCPP_value= ac_cv_env_CXXFLAGS_set= ac_cv_env_CXXFLAGS_value= ac_cv_env_CXX_set= ac_cv_env_CXX_value= ac_cv_env_F77_set= ac_cv_env_F77_value= ac_cv_env_FFLAGS_set= ac_cv_env_FFLAGS_value= ac_cv_env_LDFLAGS_set= ac_cv_env_LDFLAGS_value= ac_cv_env_OGG_PREFIX_set= ac_cv_env_OGG_PREFIX...

> Hi, > > There's no HAVE_RAND48 symbol provided by autoconf. You'll have to add > the appropriate check to autoconf/configure.ac before we can take this > patch. Sorry I forgot to mention I didn't make any changes to the configure script. The problem is that I can't test these things since I'm not on a Unix platform, and I'm not even using the

...tion, R CMD check and R CMD build all ran without running "make". Is this the way it is supposed to be? (no error messages encountered). Where is the problem? Thanks in advance! BLAS_LIBS = -L. -lblas CC = gcc CFLAGS = -g -O2 CPICFLAGS = -fPIC CPPFLAGS = -I/usr/local/include CXX = c++ CXXCPP = c++ -E CXXFLAGS = -g -O2 CXXPICFLAGS = -fPIC ECHO_C = ECHO_N = -n ECHO_T = FC = g77 FFLAGS = -g -O2 FLIBS = -lg2c -lm -L/usr/lib/gcc-lib/i386-linux/2.95.4 -lm FPICFLAGS = -fPIC F2C = F2CFLAGS = LIBM = -lm LIBR = -L$(R_HOME)/bin -lR LIBS = -L/usr/local/lib -lz -lreadline -ldl -lncurses -lm...

...tion, R CMD check and R CMD build all ran without running "make". Is this the way it is supposed to be? (no error messages encountered). Where is the problem? Thanks in advance! BLAS_LIBS = -L. -lblas CC = gcc CFLAGS = -g -O2 CPICFLAGS = -fPIC CPPFLAGS = -I/usr/local/include CXX = c++ CXXCPP = c++ -E CXXFLAGS = -g -O2 CXXPICFLAGS = -fPIC ECHO_C = ECHO_N = -n ECHO_T = FC = g77 FFLAGS = -g -O2 FLIBS = -lg2c -lm -L/usr/lib/gcc-lib/i386-linux/2.95.4 -lm FPICFLAGS = -fPIC F2C = F2CFLAGS = LIBM = -lm LIBR = -L$(R_HOME)/bin -lR LIBS = -L/usr/local/lib -lz -lreadline -ldl -lncurses -lm...

>>> >>> Those are valid instructions in every x86-32 assembler I'm aware of. >>> Perhaps it needs a switch to put it in 32-bit mode? >> >> Yes, I have been able to confirm that's what's happening behind the >> scene. The switch would be --32, however after that, ld will try to >> link >> the 64-bit versions of libc and the C