- GiNaC-list - ginac.de

Version 0.4.1
by Richard B. Kreckel 14 Dec '99

14 Dec '99

Hello all, Apologies if you got this mail twice, but the set of people on ginac-list and ginac-devel is neither disjoint nor is one a subset of the other... This is to notify you that we've uploaded version 0.4.1 of GiNaC yesterday. The updated documentation is sitting on <http://www.ginac.de/> as well. Please read the News if you are curious on what has changed (it ain't anything dramatic). Check it out, test it, submit bug-reports and (if possible) fixes! Just to keep people informed about current development, let me mention that the next release will probably feature an interface to the CINT C++ interpreter <http://root.cern.ch/root/Cint.html> by Masaharu Goto. This will allow people to write C++ scripts interactively and to compile them later. We'll get another interactive interface to GiNaC besides ginsh this way---one with all loop constructs, conditionals and containers known from C++. Currently there are still some weirdnesses concerning automatic promotion of types which are hopefully fixed soon but we are already quite excited about the new possibilities. happy hacking -rbk. -- Richard Kreckel <Richard.Kreckel(a)Uni-Mainz.DE> <http://wwwthep.physik.uni-mainz.de/~kreckel/> - To UNSUBSCRIBE, email to ginac-list(a)ginac.de with a subject of "unsubscribe".

1 0

Can't compile ginsh
by Gunnar.Isaksson＠saab.se 13 Dec '99

13 Dec '99

I have compiled GiNaC on a Debian Linux Potato box. The library compiled OK and I have successfully tested a few examples from the tutorial with correct result. However I can't get ginsh to compile, it fails on ginsh_parser.cc. Any tips/patches? //Gunnar Isaksson - To UNSUBSCRIBE, email to ginac-list(a)ginac.de with a subject of "unsubscribe".

2 2

Re: configure suggestion
by nbecker＠fred.net 03 Dec '99

03 Dec '99

>>>>> "Richard" == Richard B Kreckel <kreckel(a)zino.physik.uni-mainz.de> writes: Richard> On 1 Dec 1999 nbecker(a)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(a)ginac.de with a subject of "unsubscribe".

5 8

configure suggestion
by nbecker＠fred.net 01 Dec '99

01 Dec '99

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 It also would be nice to fix cln so it be default installs headers in /usr/local/include/cln instead of /usr/local/include. I did this manually by saying: make install includedir=/usr/local/include/cln - To UNSUBSCRIBE, email to ginac-list(a)ginac.de with a subject of "unsubscribe".

2 1