Displaying 6 results from an estimated 6 matches for "lufor".
Did you mean:
lfor
1999 Dec 23
1
rpart on Alpha under OSF
...novapred.o branch.o bsplit.o choose_surg.o fix_cp.o free_tree.o gini.o graycode.o insert_split.o make_cp_list.o make_cp_table.o mysort.o nodesplit.o partition.o poisson.o poissonpred.o pred_rpart.o rpart.o rpcountup.o rplabel.o rpmatrix.o rundown.o rundown2.o s_to_rp.o s_xpred.o surrogate.o xval.o -lUfor -lfor -lFutil -lm -lots -lm
ld:
Warning: Unresolved:
S_alloc
What is S_alloc? Do I have to install the full source for R in order
to compile a package? I do not have root rights on this machine, which
is why I went for the compiled distribution. Compiling the same package
on my Linux Intel mach...
2000 Feb 08
0
0.99.0 --with-f77 configure problem
Installing 0.99.0 with Dec UNIX 4.0f, if I use the native fortran compiler
(--with-f77) configure fails with:
checking for Fortran libraries... -lUfor -lfor -lFutil -lm -lots -lm
checking whether Fortran libraries work correctly... no
In case anyone else runs into this, the quick fix is to change line 2071
of configure from
${CC} ${LDFLAGS} -o conftest conftest.o ${FLIBS} \
to
${FC} ${LDFLAGS} -o conftest conftest.o ${FLIBS} \
(Or just ch...
2000 Mar 03
1
compiling R-1.0.0 on dec alpha (digital Unix 4.0)
I have tried compiling R on a dec alpha running digital unix 4.0 and
got the following:
f77 -shared -o ts.so PPsum.o burg.o eureka.o filter.o pacf.o starma.o stl.o carray.o mburg.o myw.o qr.o -lUfor -lfor -lFutil -lm -lots -lm
ld:
Warning: Unresolved:
R_alloc
R_NaReal
R_IsNA
R_IsNaNorNA
R_chk_calloc
R_chk_free
Rf_error
vmaxget
vmaxset
dqrdc2_
dqrcf_
mkdir ../../../../library/ts/libs
gmake[4]: Leaving directory `/home/ming/R-1.0.0/src/library/ts/src'
gmake[3]: Leaving directory `/home/ming/...
2000 Jun 23
1
MAINLD and 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
2000 Mar 21
0
Summing up histograms and misc.
...eem to mean anything, but I figured I might as well
ask since I (finally) have upgraded to R-1.0.0. It goes:
rukbat:~/hfag/src/c> R CMD SHLIB readraw.c
cc -I/local/R/lib/R/include -ieee_with_inexact -std1 -O3 -tune ev56 -c
readraw.c -o readraw.o
f77 -shared -o readraw.so readraw.o -ldxml -lUfor -lfor -lFutil -lm
-lots -lmld:
Warning: Unresolved:
Rf_error
Is it anything to worry about?
Best,
Kjetil
--
Kjetil Kjernsmo
Graduate astronomy-student Problems worthy of attack
University of Oslo, Norway Prove their worth by hitting back
E-mail: kjetikj at astro.ui...
2002 Jul 11
1
dyn.load tcl/tk (PR#1774)
..... 16
checking whether /usr/bin/cc accepts -M for generating dependencies... yes
checking whether /usr/bin/cc supports -c -o FILE.lo... yes
checking how to get verbose linking output from /usr/bin/f77... -v
checking for Fortran 77 libraries... -L/soft/readline/v4.2.1/lib -lreadline
-ltermcap -lm -lUfor -lfor -lFutil -lots -lm_c32 -lmld -lexc
checking for dummy main to link with Fortran 77 libraries... none
checking for Fortran 77 name-mangling scheme... lower case, underscore, no
extra underscore
checking whether /usr/bin/f77 and /usr/bin/cc agree on int and double... yes
checking whether /usr/b...