search for: dylib_ldflag

There is a linker argument that only Apple's GCC recognizes in the latest build. In libs/wine/Makefile.in, there is a variable that reads: Code: DYLIB_LDFLAGS = -compatibility_version $(SOVERSION) -current_version $(VERSION) -headerpad_max_install_names in order for non-Apple GCC to successfully build, it needs to pass-through the argument to the linker. The line should read: Code: DYLIB_LDFLAGS = -compatibility_version $(SOVERSION) -current_versi...

I am building from source on RHEL 4 and have run into a problem while running "make check": running code in 'lapack.R' ...make[3]: *** [lapack.Rout] Error 1 make[3]: Leaving directory `/opt/R/R-2.9.1/tests' make[2]: *** [test-Specific] Error 2 make[2]: Leaving directory `/opt/R/R-2.9.1/tests' make[1]: *** [test-all-basics] Error 1 make[1]: Leaving

Full_Name: Karsten Tabelow Version: R-2.3.1 OS: AIX5.3 Submission from: (NULL) (62.141.176.2) Specification in config.site: CC=xlc_r CFLAGS='-O -qstrict' F77=xlf_r FFLAGS='-O -qstrict' SHLIB_LDFLAGS='-G' DYLIB_LDFLAGS='-G' LDFLAGS='-brtl' CXX=xlc++_r CXXFLAGS='-O -qstrict' Complilation error in src/main/printutils.c: "printutils.c", line 582.7: 1506-1352 (S) "va_start" may not appear in a function without a variable argument list. "printutils.c", line 591.5...

Dear list, When compiling the R-2.3.0 on FC4 x86_64, I got the following errors: make[3]: Entering directory `/project/scratch3/ligroup/wuming/src/R-2.3.0/src/main' gcc -Wl,--export-dynamic -L/usr/local/lib64 -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

A while ago I compiled R 1.7.0 for AIX (with the above compiler - I'll call it xlc) and I was surprised that it went quite smoothly. Unfortunately with R 1.8.0 it's not as easy, but I succeeded at least partially. Static R works fine (after some tweaking), but --enable-R-shlib fails resp. produces a buggy R. Following are the problems I encountered (in a warning-to-fatal-error

...e' runs fine and the compilation (make) runs fine until the very last part (see below). I have libiconv in /usr/local/lib (no sure why I am getting the referencing error). The config.site file is attached. ANY HELP YOU CAN GIVE WOULD BE GREATLY APPRECIATED! :) ./configure --without-readline DYLIB_LDFLAGS=-xarch=v9 MAIN_LDFLAGS=-xarch=v9 Then I run /usr/ccs/bin/make cc -xc99=all -xarch=v9 -xopenmp -L/usr/local/bin -o R.bin Rmain.o libR.a -L../../lib -lRblas -R/usr/local/opt/SUNWspro/lib/v9:/opt/SUNWspro/lib/v9 -L/usr/local/opt/SUNWspro/lib/v9 -L/usr/local/opt/SUNWspro/prod/lib/v9 -L/usr/ccs/lib...

...are required by the linker when creating ## shared objects containing object files from a C or FORTRAN 77 ## compiler only. This is usually automatically detected by configure, ## and anything set here will be in addition unless SHLIB_LD is given. ## SHLIB_LDFLAGS= ## ditto for a dynamic library: DYLIB_LDFLAGS defaults to SHLIB_LDFLAGS ## DYLIB_LD= ## DYLIB_LDFLAGS= ## The appropriate 'lib' dir, normally 'lib', but 'lib64' on Linux on ## x86_64, mips64, ppc64, sparc64, s390x but not ia64. ## LIBnn= ## Stripping ('-s'), path ('-L'), and any other miscellaneous op...

...n, Thanks for your insight, that seems pretty direct. Unfortunately, I did not compile this version of R (it's on a large supercomputer system and this version of R was installed by the admins). Using "R CMD config", I see the following relevant settings: DYLIB_LD = icc -std=gnu99 DYLIB_LDFLAGS = -shared -openmp LDFLAGS = -L/opt/compilers/intel/cce/9.1.039/lib -L/opt/compilers/intel/fce/9.1.033/lib -L/usr/local/lib64 SHLIB_CXXLD = icpc SHLIB_CXXLDFLAGS = SHLIB_LD = icc -std=gnu99 SHLIB_LDFLAGS = -shared It looks like the SHLIB_CXXLDFLAGS is missing the "-shared -lR -L<loc-of-li...

(I asked an earlier question on the rpy2 installation to the rpy2 list, the solution there was to edit the setup.py script, but this looks beyond what I can do unless someone tells me exactly what to modify). I have R 2.8.1 on 2 machines running ubuntu 8.04 (packages R-base and R-base-dev, among others, installed using Synaptic) and while the installation of rpy2 went fine on machine1, failed on

Hi, I'm encountering trouble compiling caTools_1.17.1.tar.gz and e1071_1.6-4.tar.gz on a Linux system using the Intel compiler suite. 14 other packages I generally use installed without any trouble. I notice both of these trouble packages have a C++ component, so I wonder if that might be the issue. Below, there's information on my platform, compiler, and some diagnostic output showing

...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_CXXPICFLAGS_set= ac_cv_env_CXXPICFLAGS_value= ac_cv_env_CXX_set= ac_cv_env_CXX_value= ac_cv_env_DEFS_set= ac_cv_env_DEFS_value= ac_cv_env_DYLIB_LDFLAGS_set= ac_cv_env_DYLIB_LDFLAGS_value= ac_cv_env_DYLIB_LD_set= ac_cv_env_DYLIB_LD_value= ac_cv_env_F77_set= ac_cv_env_F77_value= ac_cv_env_FCFLAGS_set= ac_cv_env_FCFLAGS_value= ac_cv_env_FCPICFLAGS_set= ac_cv_env_FCPICFLAGS_value= ac_cv_env_FC_set= ac_cv_env_FC_value= ac_cv_env_FFLAGS_set= ac_cv_env_...

..._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_CXXPICFLAGS_set= ac_cv_env_CXXPICFLAGS_value= ac_cv_env_CXX_set= ac_cv_env_CXX_value= ac_cv_env_DYLIB_LDFLAGS_set= ac_cv_env_DYLIB_LDFLAGS_value= ac_cv_env_DYLIB_LD_set= ac_cv_env_DYLIB_LD_value= ac_cv_env_F2C_set= ac_cv_env_F2C_value= ac_cv_env_F77_set= ac_cv_env_F77_value= ac_cv_env_FFLAGS_set= ac_cv_env_FFLAGS_value= ac_cv_env_FPICFLAGS_set= ac_cv_env_FPICFLAGS_value= ac_cv_env_LAPACK_LIBS_set= ac_cv_e...