search for: shlibld

I would like to always use ${CC} for linking the main binary and the shlibs. Inspection of configure.in reveals that we currently deviate in the following cases: mainld shlibld aix[2-9]* ld ld alpha*osf* ${FC} -g -nofor_main -fpe3 ${FC} hpux* ${CC} ld Does anyone recall why we do not use ${CC} in these cases? Did anyone successfully build R on these platforms with ${CC} for mainld/shlibld? (Inspection of ltconfig from libtool seems to indicate that ${CC} shoul...

...t; > > _if_ f77 is used. How viable is `use FC to link' on other platforms? > > > > I'm not sure if it does matter here, but the only way to build R on my > Alphas currently is using Fortran as LDCMD: > > in config.site: > LDCMD="f77 " > > SHLIBLD is "ld -shared -expect_unresolved '*'". I would have expected LDCMD=f77 LDFLAGS="-g -nofor_main -fpe3" SHLIBLD=ld SHLIBLDFLAGS="-shared -expect_unresolved '*'" as the way to encode that. Now my question amounts to Does SHLIBLD=f77 work with those S...

...PIC flag for DEC cc (with DU 4.0E) --- ./configure.in.alpha-patch Mon Aug 23 06:36:28 1999 +++ ./configure.in Sun Sep 12 17:38:27 1999 @@ -541,7 +541,9 @@ -bI:\$(R_HOME)/etc/R.exp -lc -lm" ;; alpha*osf*) + ldcmd="f77 -g -nofor_main -fpe3 " cpicflags= + shlibld=f77 shlibldflags=-shared ;; alpha*linux) @@ -612,7 +614,7 @@ : ${CPICFLAGS=${cpicflags}} if test -z "${CPICFLAGS}"; then AC_MSG_WARN([Could not determine CPICFLAGS.]) - AC_MSG_ERROR([See the file INSTALL for more information.]) +# AC_MSG_ERROR([See the file INSTALL for...

...f77 LDFLAGS = LIBS = -ldl -ltermcap -lm LN_S = ln -s MAKEINDEX = /usr/local/bin/makeindex MKINSTALLDIRS = $(top_srcdir)/tools/mkinstalldirs R_XTRA_CFLAGS = R_XTRA_CPPFLAGS = -I. -I../include -I$(top_srcdir)/src/include R_XTRA_FFLAGS = R_XTRA_LIBS = RANLIB = ranlib SHELL = /bin/sh SHLIBEXT = so SHLIBLD = f77 SHLIBLDFLAGS = -bM:SRE -H512 -T512 -bnoentry -bexpall -bI:$(R_HOME)/etc/R. exp -lc -lm TAR = tar X_CFLAGS = X_LIBS = -lX11 X_PRE_LIBS = X_EXTRA_LIBS = YACC = bison -y -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://...

...nf.in by configure. # # ${R_HOME}/etc/Makeconf CC = gcc CFLAGS = -g -O2 CPICFLAGS = -fPIC CPPFLAGS = DEFS = -DHAVE_CONFIG_H FC = g77 FFLAGS = -g -O2 FLIBS = -L/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66 -L/usr/i386-redhat-linux/lib -lg2c -lm FPICFLAGS = -fPIC F2C = F2CFLAGS = SHLIBEXT = so SHLIBLD = gcc SHLIBLDFLAGS = -shared R_XTRA_CFLAGS = -mieee-fp R_XTRA_CPPFLAGS = -I$(R_HOME)/include R_XTRA_FFLAGS = ALL_CPPFLAGS = $(R_XTRA_CPPFLAGS) $(CPPFLAGS) $(DEFS) ALL_CFLAGS = $(R_XTRA_CFLAGS) $(CPICFLAGS) $(CFLAGS) ALL_FFLAGS = $(R_XTRA_FFLAGS) $(FPICFLAGS) $(FFLAGS) .SUFFIXES: .SUFFIXES: .c...

...= base ctest eda lqs modreg mva nls splines stepfun ts R_XTRA_CFLAGS = @R_XTRA_CFLAGS@ R_XTRA_CPPFLAGS = -I. -I../include -I$(top_srcdir)/src/include -I$(top_srcdir)/src/include/R_ext R_XTRA_FFLAGS = @R_XTRA_FFLAGS@ R_XTRA_LIBS = @R_XTRA_LIBS@ RANLIB = @RANLIB@ SHELL = /bin/sh SHLIBEXT = @SHLIBEXT@ SHLIBLD = @SHLIBLD@ SHLIBLDFLAGS = @SHLIBLDFLAGS@ TAR = @TAR@ X_CFLAGS = @X_CFLAGS@ X_LIBS = @X_LIBS@ X_PRE_LIBS = @X_PRE_LIBS@ X_EXTRA_LIBS = @X_EXTRA_LIBS@ YACC = @YACC@ ALL_CFLAGS = $(R_XTRA_CFLAGS) $(CFLAGS) ALL_CPPFLAGS = $(R_XTRA_CPPFLAGS) $(CPPFLAGS) $(DEFS) ALL_FFLAGS = $(R_XTRA_FFLAGS) $(FFLAGS)...

...t the package into CRAN's src/contrib/Devel for some time. If anyone knows about platform/compiler specific settings CXXPICFLAGS settings that configure needs to be taught, pls let me know. Building shared libs would be based on the following idea: if C++ code was found, then try using CXX as SHLIBLD (i.e. the C++ compiler for building the shared library). Alternatively, one would need to find out what C++ is linked against, which may be a pain. Anyway, I thought I'd collect some feedback and then maybe come up with something refined. -k -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-....

...hz.ch > Subject: [Rd] Missing -lm for tcltk (R 1.1.0, AIX 4.3) (PR#573) > CC: R-bugs@biostat.ku.dk > X-Loop: R-bugs@biostat.ku.dk > > Hi, > > ok, AIX 4.3 insists on being different. I can't compile --with-tcltk > out of the box. I have to add '-lm' to the SHLIBLDFLAGS manually > after configure. Yes, I guess that's because it insists on resolving libm at the shared libs build stage. > Which brings up the question: Can you use TK_LIBS instead of TK_XLIBSW > during configure? Excerpt from tkConfig.sh on my machine: > > # Linker sw...

...KINSTALLDIRS = $(top_srcdir)/tools/mkinstalldirs R_PKGS = base ctest eda lqs modreg mva nls splines stepfun ts R_XTRA_CFLAGS = R_XTRA_CPPFLAGS = -I. -I../include -I$(top_srcdir)/src/include -I$(top_srcdir)/src/include/R_ext R_XTRA_FFLAGS = R_XTRA_LIBS = RANLIB = ranlib SHELL = /bin/sh SHLIBEXT = so SHLIBLD = gcc SHLIBLDFLAGS = -G TAR = tar X_CFLAGS = -I/usr/openwin/include X_LIBS = -L/usr/openwin/lib -R/usr/openwin/lib -lX11 X_PRE_LIBS = -lSM -lICE X_EXTRA_LIBS = -lsocket -lnsl YACC = bison -y ALL_CFLAGS = $(R_XTRA_CFLAGS) $(CFLAGS) ALL_CPPFLAGS = $(R_XTRA_CPPFLAGS) $(CPPFLAGS) $(DEFS) ALL_FFLAG...

Full_Name: Frank Beimfohr Version: 0.64.1, devel. OS: Solaris 2.5.1 Submission from: (NULL) (129.217.131.31) I try to compile R on my Sparc 4 (Solaris 2.5.1) but the compilation fails. I tried the developer-version and the contributed 0.64.1-Version. I start configure with the --g77-Option. During the compilation it stops with an error, which says that the R/src/library/modreg/src/bsplvd.f

...and spectrum (spec.pgram, plot.spec). tseries ======= This has S-like function names, but does not, for example, accept multiple time series in acf. It has nice plots and nice examples. (It would be better if the LIBNAME were tseries, when no Makefile would be needed: as it is $(LD) should be $(SHLIBLD) and CFLAGS += -Wall is not a good idea being make and CC-specific.) It would give us acf/ccf/pacf (for acf in S) spectrum/cross spectra/cumulative.periodogram dse === As far as I can see (it is very complex) this handles state-space models, and can handle ARMA models by converting them (appro...

Recent sensible changes to the dynload mechanism have made an old problem resurface: how should we deal with packages which contain Fortran code and may need to be linked against additional libraries such as -lf2c? The current consensus is that extra Fortran libraries maybe needed are handled via the make variable FLIBS, and that `-lf2c' or `-lg2c' are added by default if g77 is used.

...r)/aux/install-sh -c INSTALL_DATA= ${INSTALL} -m 644 INSTALL_PROGRAM= ${INSTALL} INSTALL_DIR= ${INSTALL} -d LATEX= /apps/res/bin/latex LDCMD= g77 LDFLAGS = LIBS= -ldl -ltermcap -lm LN_S= ln -s MAKEINDEX= false MKINSTALLDIRS= $(top_srcdir)/aux/mkinstalldirs RANLIB= ranlib SHELL= /bin/sh SHLIBEXT= so SHLIBLD= ld SHLIBLDFLAGS= -G TAR= tar X_CFLAGS= -I/usr/openwin/include X_LIBS= -L/usr/openwin/lib -R/usr/openwin/lib -lX11 X_PRE_LIBS= -lSM -lICE X_EXTRA_LIBS= -lsocket -lnsl YACC= yacc prefix= /usr/local exec_prefix= ${prefix} bindir= ${exec_prefix}/bin datadir= ${prefix}/share libdir= ${exec_prefix}/lib...