ralf wrote: > I coult get rid of those by using the setarch tool and the > trivial patch below: > $ setarch i386 ../cln/configure -C 'CFLAGS=-m32 -g -O2' \ > 'CXXFLAGS=-m32 -g -O2' LDFLAGS=-m32 > $ setarch i386 make make failed with similar linker errors, the differences are: 1. additional undefined references to `_GLOBAL__I_cl_module__cl_ieee__firstglobalfun 2. the undefined references to mulu64_high and divu64_rest disappeared. btw, make without setarch i386 said exactly the same. installed cln on a pentium: no errors, make check passed, make install works. I couldn't use it to build GiNaC because I don't know how to tell GiNaC to find cln in my customized install dir, any hints? So I wrote a small sample program using cln: #include <iostream> #include <cln/real_io.h> #include <cln/random.h> #include <cln/real.h> using namespace std; using namespace cln; int main() { cl_R r=random_R(1.); cl_R s=exp(r); cout <<s <<endl; return 0; } and that worked on the x86. Then I copied libs and include to the xeon and compiled the program. With and without setarch i386, it complaint: .../cln/object.h:29: warning: "cl_word_alignment" redefined .../cln/number.h:187: error: `cl_FN_tag' undeclared .../cln/float_class.h:43: error: `cl_SF_tag' undeclared is this of any help? cheers werner
* werner wrote on Sun, Oct 31, 2004 at 06:27:23PM CET:
installed cln on a pentium: no errors, make check passed, make install works. I couldn't use it to build GiNaC because I don't know how to tell GiNaC to find cln in my customized install dir, any hints?
Yes. Read the documentation. It'll be something like $ ../path/to/ginac/configure CPPFLAGS=-I${prefix}/include \ LDFLAGS=-L${prefix}/lib where ${prefix} is whatever you pass to --prefix and you'll probably have to do an $ LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}${prefix}/lib $ export LD_LIBRARY_PATH before that. (The weird LD_LIBRARY_PATH setting is so that you don't end up with a solitary colon at the beginning of the path, making the current directory eligible for library loading, and at the same time prevent overwriting of a previous setting). Can you build and use GiNaC then? Note: I have never used GiNaC myself and thus this is all a bit speculative. Furthermore, you'll also have to do the `-m32' and setarch thing for builing GiNaC as well (or better: build it on the x86 right away, like you did with cln). Regards, Ralf
participants (2)
-
Ralf Wildenhues
-
werner