"Richard" == Richard B Kreckel <kreckel@zino.physik.uni-mainz.de> writes:
Richard> On 1 Dec 1999 nbecker@fred.net wrote: >> It would be nice to add an option to tell configure where to find cln >> includes and lib. >> >> Lacking that, it should be documented that this will work: >> >> CPPFLAGS=/usr/local/include ./configure Richard> ^-- a -I is missing here Richard> Shouldn't your compiler check this directory anyways? Strange it doesn't. Richard> BTW, this *is* documented in the tutorial's section about configuration Richard> with the only difference in path: CPPFLAGS="${CPPFLAGS} -I${HOME}/include" No. Starting with gcc-2.95 (IIRC) it won't automatically look in /usr/local/include. On systems (such as linux) where gcc is the native compiler, installed with --prefix=/usr, /usr/local/include is no longer automatically checked. Richard> Exactly as I did, except that we use includedir=/usr/local/include/CLN Richard> here. I guess the uppercase spelling is depricated by some people out Richard> there. In acinclude.m4 the Macro GINAC_CHECK_CLN_H does attempt to do Richard> exactly this but the macro AC_CHECK_HEADERS puts it result in uppercase Richard> always so there is no nice Autoconf-way to distinguish between cln/cln.h Richard> and CLN/cln.h. Hope you can live with that. Maybe a future version of Richard> CLN does this. I didn't notice that GiNaC looks for CLN/ until after installing cln, so I just put a symlink from CLN->cln. - To UNSUBSCRIBE, email to ginac-list@ginac.de with a subject of "unsubscribe".
On 1 Dec 1999 nbecker@fred.net wrote:
No. Starting with gcc-2.95 (IIRC) it won't automatically look in /usr/local/include. On systems (such as linux) where gcc is the native compiler, installed with --prefix=/usr, /usr/local/include is no longer automatically checked.
I have version 2.95.1 19990816 sitting under /data/scratch/prefix/bin/ and it finds the headers under /usr/local/include/.
I didn't notice that GiNaC looks for CLN/ until after installing cln, so I just put a symlink from CLN->cln.
We had the suggestion to write a script cln-config and get this into CLN, that just does what gtk-config does for gtk. Maybe this would be a good idea. Regards -rbk. -- Richard B. Kreckel <Richard.Kreckel@Uni-Mainz.DE> <http://wwwthep.physik.uni-mainz.de/~kreckel/> - To UNSUBSCRIBE, email to ginac-list@ginac.de with a subject of "unsubscribe".
Hi, I've just run $ cvs checkout GiNaC and tried to run "make". Then there still has some error messages when making the document (see below). It's not a problem, but it makes users feel bad at the first glance! Have nice weekend, Son. ------------- Making all in doc make[2]: Entering directory `/home/dhson/project/GiNaC/doc' Making all in tutorial make[3]: Entering directory `/home/dhson/project/GiNaC/doc/tutorial' cd . \ && makeinfo --html `echo ginac.texi | sed 's,.*/,,'` /usr/local/teTeX/bin/ix86-linux-libc6/makeinfo: unrecognized option `--html' Try `makeinfo --help' for more information. make[3]: *** [ginac.html] Error 4 make[3]: Leaving directory `/home/dhson/project/GiNaC/doc/tutorial' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/dhson/project/GiNaC/doc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/dhson/project/GiNaC' make: *** [all-recursive-am] Error 2 - To UNSUBSCRIBE, email to ginac-list@ginac.de with a subject of "unsubscribe".
Hi! On Fri, 3 Dec 1999, Do Hoang Son wrote:
/usr/local/teTeX/bin/ix86-linux-libc6/makeinfo: unrecognized option `--html'
You will either need a newer version of texinfo (I recommend 4.0) or disable the generation of HTML docs specifying the '--disable-html-doc' flag to 'configure'. Bye, Christian -- / Coding on PowerPC and proud of it \/ http://www.uni-mainz.de/~bauec002/ - To UNSUBSCRIBE, email to ginac-list@ginac.de with a subject of "unsubscribe".
On Fri, 3 Dec 1999, Christian Bauer wrote:
Hi!
On Fri, 3 Dec 1999, Do Hoang Son wrote:
/usr/local/teTeX/bin/ix86-linux-libc6/makeinfo: unrecognized option `--html'
You will either need a newer version of texinfo (I recommend 4.0) or disable the generation of HTML docs specifying the '--disable-html-doc' flag to 'configure'.
Bye, Christian
Hi Christian, So in such case could we put a check point for configure file, e.g if ( version texinfo < 4.0) flag=--disable-html-doc else go ahead! :-))) Ok, just a joke, thanks for your guide. Son. PS. But anyways I wonder if we could check the version for any involved packages and give a more frinedly mesg. like:" you should have bla bla..." instead of throwing out the errors mesg and stop ? If it can be done, GiNac will be as friendly as any application in MS Windows env. :-)) - To UNSUBSCRIBE, email to ginac-list@ginac.de with a subject of "unsubscribe".
On Fri, 3 Dec 1999, Do Hoang Son wrote: [...]
Hi Christian, So in such case could we put a check point for configure file, e.g if ( version texinfo < 4.0) flag=--disable-html-doc else go ahead! :-)))
We could just delete it from /usr/local/bin/, in which case AM_MISSING_PROG will take proper action. ;-) Changing the macro will require to write our own macro, since: if (makeinfo --version) < /dev/null > /dev/null 2>&1; then MAKEINFO=makeinfo echo "$ac_t""found" 1>&6 else MAKEINFO="$missing_dir/missing makeinfo" echo "$ac_t""missing" 1>&6 fi
Ok, just a joke, thanks for your guide.
Aren't you supposed to be on vacation? Are you coding there (in France)?!?
PS. But anyways I wonder if we could check the version for any involved packages and give a more frinedly mesg. like:" you should have bla bla..." instead of throwing out the errors mesg and stop ? If it can be done, GiNac will be as friendly as any application in MS Windows env. :-))
Boy, that *was* rude! ;-) PS: BTW, you guys have noticed that we are on ginac-list, haven't you? These are two lists: ginac-devel and ginac-list. Maybe I should open ginac-flame soon... -- Richard Kreckel <Richard.Kreckel@Uni-Mainz.DE> <http://wwwthep.physik.uni-mainz.de/~kreckel/> - To UNSUBSCRIBE, email to ginac-list@ginac.de with a subject of "unsubscribe".
Hi! On Fri, 3 Dec 1999, Richard B. Kreckel wrote:
So in such case could we put a check point for configure file, e.g if ( version texinfo < 4.0) flag=--disable-html-doc
We could just delete it from /usr/local/bin/, in which case AM_MISSING_PROG will take proper action. ;-) Changing the macro will require to write our own macro
Something like "checking whether makeinfo accepts the --html flag..." might be appropriate. Richy, you have written the CLN checks, so you know how to do this. :-) Bye, Christian -- / Coding on PowerPC and proud of it \/ http://www.uni-mainz.de/~bauec002/ - To UNSUBSCRIBE, email to ginac-list@ginac.de with a subject of "unsubscribe".
On Fri, 3 Dec 1999, Christian Bauer wrote: [...]
Something like "checking whether makeinfo accepts the --html flag..." might be appropriate. Richy, you have written the CLN checks, so you know how to do this. :-)
Oh, no, I have forgotten! Who ordered this??? Happy hacking -richy. -- Richard Kreckel <Richard.Kreckel@Uni-Mainz.DE> <http://wwwthep.physik.uni-mainz.de/~kreckel/> - To UNSUBSCRIBE, email to ginac-list@ginac.de with a subject of "unsubscribe".
On Fri, 3 Dec 1999, Christian Bauer wrote:
You will either need a newer version of texinfo (I recommend 4.0) or disable the generation of HTML docs specifying the '--disable-html-doc' flag to 'configure'.
Or we have to update the configure script. I always though that checking the installed software base and then deciding what to build and what not is the main task of configure... -- Alexander Frink E-Mail: Alexander.Frink@Uni-Mainz.DE Institut fuer Physik Phone: +49-6131-393391 Johannes-Gutenberg-Universitaet D-55099 Mainz, Germany - To UNSUBSCRIBE, email to ginac-list@ginac.de with a subject of "unsubscribe".
participants (5)
-
Alexander Frink
-
Christian Bauer
-
Do Hoang Son
-
nbecker＠fred.net
-
Richard B. Kreckel