similar to: Compiling R (1.3.0) on AIX (4.3) fails (PR#1034)

The configure script failed on tk on several platforms. One is given below. This did not happen on versions of R older than 1.5.0. Message from configure: configure: WARNING: /opt_local/opt/tk-8.0/include/tk.h: accepted by the compiler, rejected by the preprocessor! configure: WARNING: /opt_local/opt/tk-8.0/include/tk.h: proceeding with the preprocessor's result This was in config.log, the

The OS X configure in R-devel has been changed to use two-level namespaces. There are still some problems. 1. Trunmed.c in the modreg packages defines a function heapsort(), while heapsort is also defined (differently) in /usr/lib/stdlib.h. I (temporarily) disabled the definition in stdlib.h. 2. If R is configured with the --without-x flag, then CPPFLAGS does not include /usr/X11R6/include,

Hi, I believe configure was not finding tk.h, because tk-devel rpm was not available on the given host. Thanks Erik and Peter for the suggestions on checking tk.h and stdout of ./configure. Just one further question for Peter> "Well, the package is there, as a stub to tell you that it doesn't work...." So then how can you confirm from the library() output (or elsewhere) if

Hi, Having trouble loading tcltk in R 2.2.1 built from source. ./configure, make, make check, and make install run ok. > library(tcltk) Error in firstlib(which.lib.loc, package) : Tcl/Tk support is not available on this system Error in library(tcltk) : .First.lib failed for 'tcltk' even though it is listed in library() output. I have the same problem even if i compile

Hi, When installing "nlme" from CRAN on Solaris 5.3.1 by doing install.packages("nlme") I get: [clip] gcc -G -o nlme.so corStruct.o gnls.o matrix.o nlOptimizer.o nlme.o nlmefit.o nls.o pdMat.o -L/usr/local/lib R data inst /usr/local/lib/R/bin/INSTALL: /bin/perl: not found help /usr/local/lib/R/bin/INSTALL: /usr/local/lib/R/bin/build-help: not found

Hi. I am trying to modify kmeans function. It seems that is failing something obvious with the workspace. I am a newbie and here is my code: myk = function (x, centers, iter.max = 10, nstart = 1, algorithm = c("Hartigan-Wong", + "Lloyd", "Forgy", "MacQueen")) + { + do_one <- function(nmeth) { + Z <- switch(nmeth, { + Z

Dear R-helpers, I'm learning how to compile R packages with fortran routines and use the acepack source as an example. After some hiccups (Guido told me about the need to set make_mode=UNIX) I got to the following: `make pkg-acepack' runs without error (see below), but it does not * compile any .f file in acepack/src * (hence) try to create any dll file or libs (I'm

Hi everyone Following are a number of build-system cleanup patches. Some of them are prep-work for a possible upcoming automake/gnulib introduction. Best regards, Tiziano

On Sat, May 19, 2001 at 12:19:39PM +0000, Christian Weisgerber wrote: > Christian Weisgerber <naddy@mips.inka.de> wrote: > > > Problems in FLAC 0.9: > > Also: > > ===> Building for flac-0.9 > cd . && aclocal > aclocal: configure.in: 7: macro `AM_PROG_LIBTOOL' not found in library > aclocal: configure.in: 22: macro `AM_PATH_XMMS' not

> > > $ aclocal && autoconf && automake -c -a -i > > > aclocal: configure.in: 45: macro `AM_PATH_XMMS' not found in > library > > > > my hunch is that your version of either automake or possibly > > autoconf is not recent enough. > > No. He simply doesn't have xmms installed. That's what I mentioned > a while ago:

I re-generated configure of the latest R-devel with autoconf 2.57 and got the following problem: configure: error: conditional "HAVE_ORBIT" was never defined. Usually this means the macro was only invoked conditionally. (resolving HAVE_ORBIT leaves us with HAVE_GNORBA causing the same problem. You should be able to reproduce it by running autoreconf (or aclocal; autoconf - not just

> > > AM_INIT_AUTOMAKE(flac, 0.9) > > > > > > I've never had to run autoconf manually before so I'm not really > sure > > what > > > I'm doing. > > > > > hmm... not sure what the syntax error is; did you run aclocal > first? > > No. Had no idea I had to. I've gleaned from someone else's message > that I

1. Add support for files >2GB via Paul Eggert's AC_SYS_LARGEFILE macro. This macro is now part of autoconf 2.50. Because of this, "config.h" needs to be included before system headers to get the appropriate defines for LFS support. openbsd-compat/sigact.c configure.in acinclude.m4 2. AIX defines TILDE in <sys/ioctl.h>. Rename to TILDE_CHAR. Feel

> > Now I have done some more reading, and I don't think simply > > putting the call to AM_PATH_XMMS an acinclude.m4 will help him. > > No, of course not. You need to put the macro _definition_, i.e. ... > > > This macro is defined in /usr/local/share/aclocal/xmms.m4 > > ... xmms.m4 into acinclude.m4. (Putting it into aclocal.m4 may or > may > not

Is fPIC broken on x86_64 in LLVM 2.6? I looked through the release notes but did not see anything mentioned. When I try: ------------------- > llvm-gcc -Iinclude -emit-llvm -fPIC -O3 -c -o file.opt.bc file.c > llvm-ld -native -Xlinker=-shared -Xlinker=-Wl,-soname,libtest.so -o file.so file.opt.bc ------------------- on an x86 machine it works fine. When I try it on x86_64, the

Hi all, I've been running into what appears to be an optimization bug in llvm, while compiling the latest ruby 1.9.3 with the latest llvm/clang 2.9 version. From hands on experimentation I do know that the gvn pass for the "vm.c" compilation is the culprit of the miscompilation (clang -O2/-O3 options produce the miscompilation, however -O1 is fine!). I've also tried to

Hi I use RH 9 + asterisk v1.0 stable + 2 PCI fritz cards + chan_capi 3.5 and it works fine, Since my users want fax fonctionnality and customers know 1 of the msm as fax number I wanted to try the chan_capi-0.3.5 patch if I patch chan_capi and run make, I get an error message , as you can read below, orginal chan_capi compile works, when patched I get an error, no CID ? Any idea ? anybody

> Due to the lack of bugpoint examples in the documentation, I have no > idea how to use bugpoint > in this complex case, where vm.o firstly needs to be linked with lots > of other compiled modules > and libraries, then the resulting program needs to be executed with > some parameters! It should be possible. I did something like that for debugging a clang bootstrap. What I did

> Is fPIC broken on x86_64 in LLVM 2.6? No, it works w/o any problems > ------------------- >  > llvm-gcc -Iinclude -emit-llvm -fPIC -O3 -c -o file.opt.bc  file.c >  > llvm-ld -native -Xlinker=-shared -Xlinker=-Wl,-soname,libtest.so -o > file.so file.opt.bc > ------------------- PIC-ness is a backend option. So, passing -fPIC to llvm-gcc does not make any sense, it is not

The reason I was linking via llvm-ld is because I didn't know how to pass bitcode files to llvm-gcc. How can I do that? Anton Korobeynikov wrote: >> Is fPIC broken on x86_64 in LLVM 2.6? > No, it works w/o any problems > >> ------------------- >> > llvm-gcc -Iinclude -emit-llvm -fPIC -O3 -c -o file.opt.bc file.c >> > llvm-ld -native -Xlinker=-shared