- GiNaC-devel - ginac.de

Error while building GiNaC-1.2.1
by Kai Ludwig 08 Jun '04

08 Jun '04

Hi All, First of all: You're doing a great job with GiNaC! I've tried to compile the GiNaC-1.2.1 version with g++-3.3.3-41 under a SuSE9.1 Linux system. Got the following: g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -MT input_lexer.lo -MD -MP -MF .deps/input_lexer.Tpo -c input_lexer.cc -fPIC -DPIC -o .libs/input_lexer.oIn file included from /home/cbauer/projects/GiNaC-1.2/ginac/input_lexer.ll:35:input_lexer.h:43: error: conflicting types for `char ginac_yytext[]' input_lexer.cc:446: error: previous declaration as `char*ginac_yytext' input_lexer.h:43: error: storage size of `ginac_yytext' isn't known input_lexer.h:43: error: storage size of `ginac_yytext' isn't known make[2]: *** [input_lexer.lo] Error 1 make[2]: Leaving directory `/usr/local/src/ginac/GiNaC-1.2.1/ginac' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/ginac/GiNaC-1.2.1' make: *** [all] Error 2 Cheers, Kai -- http://echempp.sourceforge.net Kai Ludwig Institut für Organische Chemie Auf der Morgenstelle 18 72076 Tübingen Tel.: 07071/29-73049 Mail: kai.ludwig(a)uni-tuebingen.de

1 0

None
by Chris Dams 07 Jun '04

07 Jun '04

Dear GiNaCers, Here is a patch for series expansion. The reason for the patch is the same as for one I sent before. However, I did not get any answer on my pervious mail. What do you think when I say "Series expansion should never use expansion, unless there is no other means available to avoid it."? Best, Chris

1 0

Re: C++ module ordering (was: segmentation fault on GiNaC-1.2.0 using MinGW on Win XP)
by Richard B. Kreckel 10 May '04

10 May '04

On 6 May 2004, Ian Lance Taylor wrote: > > Please see <http://www.ginac.de/lists/ginac-devel/msg00623.html>. > > Those bits are the end of my message weren't actually written by me. > They were written by some of the C++ compiler hackers at Cygnus. So it remains a mystery what was meant by "full runtime dependency analysis [...] with no linker mods"? Sad. > Are you familiar with the init_priority attribute supported by g++? > It seems to me that it handles most of the problems associated with > static object initialization order. > http://gcc.gnu.org/onlinedocs/gcc-3.4.0/gcc/C---Attributes.html#C++%20Attri… Sure, but that is only pampering about the real problem: Who establishes the PRIORITY variables? The programmer would have to do it manually. Any programmer is likely to get it wrong if confronted with several hundreds or even thousands of modules. Working with an automated mechanism is much less prone to errors. Hence init_priority is not at all an acceptable solution, IMNSHO. A while ago, I've been debugging an industrial application where the linker line was basically rearranged automatically based on a self-made scheme: a script was extracting dependency ordering information scattered by the programmer. That solution is equivalant to GCC's init_priority. The lesson learned from that experience are: 1) Most professional C++ programmers are not aware of there being a problem. Really. :-( 2) Even if they are, they are unlikely to get it right. #-( 3) If they don't get it right, debugging code which hasn't even started running yet is intersting. :-/ Best wishes -richy. -- Richard B. Kreckel <http://www.ginac.de/~kreckel/>

3 4

CLN 1.1.7 released
by Richard B. Kreckel 02 May '04

02 May '04

Hi! This is to announce the availability of CLN version 1.1.7. It is source and binary compatible to version 1.1.6. Noticeable features are fixes for a couple of corner case bugs and the inclusion of a workaroud for a miscompilation issue with GCC 3.1.0 - 3.3.4-prerelease. Cebix: Is my handling of the spec file finally okay? Qalculate-hackers: Oh, yes, that miscompilation issue is responsible for crashes you may see when typing into the number base conversion dialog. It was reported via the Debian BTS. Enjoy -richy. -- Richard B. Kreckel <http://www.ginac.de/~kreckel/>

1 0

Link Failure with 1.2.1 and Mac OS X 10.3.3
by Gregory Wright 26 Apr '04

26 Apr '04

Hi, The latest still fails to link on Mac OS 10.3.3. Build log is below. Any suggestions? Best Wishes, Greg if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I./../ginac -I../ginac -DIN_GINAC -I/opt/local/include -I/opt/local/include -I/opt/local/include -g -O2 -MT ginsh_lexer.o -MD -MP -MF ".deps/ginsh_lexer.Tpo" \ -c -o ginsh_lexer.o `test -f 'ginsh_lexer.cc' || echo './'`ginsh_lexer.cc; \ then mv -f ".deps/ginsh_lexer.Tpo" ".deps/ginsh_lexer.Po"; \ else rm -f ".deps/ginsh_lexer.Tpo"; exit 1; \ fi /bin/sh ../libtool --mode=link g++ -g -O2 -L/opt/local/lib -o ginsh ginsh_parser.o ginsh_lexer.o ../ginac/libginac.la -lreadline -lncurses -L/opt/local/lib -lcln -lgmp mkdir .libs g++ -g -O2 -o .libs/ginsh ginsh_parser.o ginsh_lexer.o -Wl,-bind_at_load -L/opt/local/lib ../ginac/.libs/libginac.dylib -lreadline -lncurses /opt/local/lib/libcln.dylib -lstdc++ /opt/local/lib/libgmp.dylib ld: warning multiple definitions of symbol _PC /opt/local/lib/libreadline.dylib(terminal.so) definition of _PC /usr/lib/libncurses.dylib(lib_tputs.o) definition of _PC ld: warning multiple definitions of symbol _BC /opt/local/lib/libreadline.dylib(terminal.so) definition of _BC /usr/lib/libncurses.dylib(lib_termcap.o) definition of _BC ld: warning multiple definitions of symbol _UP /opt/local/lib/libreadline.dylib(terminal.so) definition of _UP /usr/lib/libncurses.dylib(lib_termcap.o) definition of _UP ld: Undefined symbols: __GLOBAL__I_cl_module__cl_C_ring__firstglobalfun __GLOBAL__I_cl_module__cl_DF_globals__firstglobalfun __GLOBAL__I_cl_module__cl_FF_globals__firstglobalfun __GLOBAL__I_cl_module__cl_GV_I__firstglobalfun __GLOBAL__I_cl_module__cl_GV_number__firstglobalfun __GLOBAL__I_cl_module__cl_I_ring__firstglobalfun __GLOBAL__I_cl_module__cl_LF_globals__firstglobalfun __GLOBAL__I_cl_module__cl_MI__firstglobalfun __GLOBAL__I_cl_module__cl_RA_ring__firstglobalfun __GLOBAL__I_cl_module__cl_R_ring__firstglobalfun __GLOBAL__I_cl_module__cl_SV_number__firstglobalfun __GLOBAL__I_cl_module__cl_SV_ringelt__firstglobalfun __GLOBAL__I_cl_module__cl_UP__firstglobalfun __GLOBAL__I_cl_module__cl_UP_no_ring__firstglobalfun __GLOBAL__I_cl_module__cl_ieee__firstglobalfun __GLOBAL__I_cl_module__cl_no_ring__firstglobalfun __GLOBAL__I_cl_module__cl_prin_globals__firstglobalfun __GLOBAL__I_cl_module__cl_random_def__firstglobalfun __GLOBAL__I_cl_module__cl_st_null__firstglobalfun __GLOBAL__I_cl_module__cl_symbol__firstglobalfun make[2]: *** [ginsh] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: Target com.apple.build returned: shell command "cd "/Users/gwright/src/darwinports/dports/math/GiNaC/work/GiNaC-1.2.1" && make all" returned error 2 Command output: ld: warning multiple definitions of symbol _BC /opt/local/lib/libreadline.dylib(terminal.so) definition of _BC /usr/lib/libncurses.dylib(lib_termcap.o) definition of _BC ld: warning multiple definitions of symbol _UP /opt/local/lib/libreadline.dylib(terminal.so) definition of _UP /usr/lib/libncurses.dylib(lib_termcap.o) definition of _UP ld: Undefined symbols: __GLOBAL__I_cl_module__cl_C_ring__firstglobalfun __GLOBAL__I_cl_module__cl_DF_globals__firstglobalfun __GLOBAL__I_cl_module__cl_FF_globals__firstglobalfun __GLOBAL__I_cl_module__cl_GV_I__firstglobalfun __GLOBAL__I_cl_module__cl_GV_number__firstglobalfun __GLOBAL__I_cl_module__cl_I_ring__firstglobalfun __GLOBAL__I_cl_module__cl_LF_globals__firstglobalfun __GLOBAL__I_cl_module__cl_MI__firstglobalfun __GLOBAL__I_cl_module__cl_RA_ring__firstglobalfun __GLOBAL__I_cl_module__cl_R_ring__firstglobalfun __GLOBAL__I_cl_module__cl_SV_number__firstglobalfun __GLOBAL__I_cl_module__cl_SV_ringelt__firstglobalfun __GLOBAL__I_cl_module__cl_UP__firstglobalfun __GLOBAL__I_cl_module__cl_UP_no_ring__firstglobalfun __GLOBAL__I_cl_module__cl_ieee__firstglobalfun __GLOBAL__I_cl_module__cl_no_ring__firstglobalfun __GLOBAL__I_cl_module__cl_prin_globals__firstglobalfun __GLOBAL__I_cl_module__cl_random_def__firstglobalfun __GLOBAL__I_cl_module__cl_st_null__firstglobalfun __GLOBAL__I_cl_module__cl_symbol__firstglobalfun make[2]: *** [ginsh] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Warning: the following items did not execute (for GiNaC): com.apple.build ranger>

2 1

GiNaC 1.2.1 now available
by Christian Bauer 23 Apr '04

23 Apr '04

Hello! GiNaC 1.2.1 is now available! The changes are: - Fixed infinite recursion in atan2_evalf() and improved atan2_eval(). - Added automatic evaluations for trigonometric functions with negative arguments (e.g. sin(-2) -> -sin(2)). - Fixed a static initialization order goof-up. - Fixed various bugs in series expansion. If you had problems using GiNaC 1.2 on certain platforms because you were getting segmentation faults all the way, this release should solve the issue. You can download GiNaC 1.2.1 as always from ftp://ftpthep.physik.uni-mainz.de/pub/GiNaC Bye, Jens and Christian -- / Physics is an algorithm \/ http://www.uni-mainz.de/~bauec002/

1 0

Link failure on OS X 10.3.3
by Gregory Wright 23 Apr '04

23 Apr '04

Hi, While building 1.2.0 on Mac OS X 10.3.3 (Panther) I had a link error. The underlying CLN is version 1.1.6 built with gmp 4.1.2. The compiler is ranger> gcc --version gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1495) Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. The error is below. The multiply defined symbols are harmless, but the undefined symbols are the problem. Is this perhaps some link-ordering issue? Does anyone have any ideas? Please cc: to me directly as I am not subscribed to the list yet. Thanks. Best Wishes, Greg Wright if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I./../ginac -I../ginac -DIN_GINAC -I/opt/local/include -I/opt/local/include -I/opt/local/include -g -O2 -MT ginsh_lexer.o -MD -MP -MF ".deps/ginsh_lexer.Tpo" \ -c -o ginsh_lexer.o `test -f 'ginsh_lexer.cc' || echo './'`ginsh_lexer.cc; \ then mv -f ".deps/ginsh_lexer.Tpo" ".deps/ginsh_lexer.Po"; \ else rm -f ".deps/ginsh_lexer.Tpo"; exit 1; \ fi /bin/sh ../libtool --mode=link g++ -g -O2 -L/opt/local/lib -o ginsh ginsh_parser.o ginsh_lexer.o ../ginac/libginac.la -lreadline -lncurses -L/opt/local/lib -lcln -lgmp mkdir .libs g++ -g -O2 -o .libs/ginsh ginsh_parser.o ginsh_lexer.o -Wl,-bind_at_load -L/opt/local/lib ../ginac/.libs/libginac.dylib -lreadline -lncurses /opt/local/lib/libcln.dylib -lstdc++ /opt/local/lib/libgmp.dylib ld: warning multiple definitions of symbol _PC /opt/local/lib/libreadline.dylib(terminal.so) definition of _PC /usr/lib/libncurses.dylib(lib_tputs.o) definition of _PC ld: warning multiple definitions of symbol _BC /opt/local/lib/libreadline.dylib(terminal.so) definition of _BC /usr/lib/libncurses.dylib(lib_termcap.o) definition of _BC ld: warning multiple definitions of symbol _UP /opt/local/lib/libreadline.dylib(terminal.so) definition of _UP /usr/lib/libncurses.dylib(lib_termcap.o) definition of _UP ld: Undefined symbols: __GLOBAL__I_cl_module__cl_C_ring__firstglobalfun __GLOBAL__I_cl_module__cl_DF_globals__firstglobalfun __GLOBAL__I_cl_module__cl_FF_globals__firstglobalfun __GLOBAL__I_cl_module__cl_GV_I__firstglobalfun __GLOBAL__I_cl_module__cl_GV_number__firstglobalfun __GLOBAL__I_cl_module__cl_I_ring__firstglobalfun __GLOBAL__I_cl_module__cl_LF_globals__firstglobalfun __GLOBAL__I_cl_module__cl_MI__firstglobalfun __GLOBAL__I_cl_module__cl_RA_ring__firstglobalfun __GLOBAL__I_cl_module__cl_R_ring__firstglobalfun __GLOBAL__I_cl_module__cl_SV_number__firstglobalfun __GLOBAL__I_cl_module__cl_SV_ringelt__firstglobalfun __GLOBAL__I_cl_module__cl_UP__firstglobalfun __GLOBAL__I_cl_module__cl_UP_no_ring__firstglobalfun __GLOBAL__I_cl_module__cl_ieee__firstglobalfun __GLOBAL__I_cl_module__cl_no_ring__firstglobalfun __GLOBAL__I_cl_module__cl_prin_globals__firstglobalfun __GLOBAL__I_cl_module__cl_random_def__firstglobalfun __GLOBAL__I_cl_module__cl_st_null__firstglobalfun __GLOBAL__I_cl_module__cl_symbol__firstglobalfun make[2]: *** [ginsh] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: Target com.apple.build returned: shell command "cd "/Users/gwright/src/darwinports/dports/math/GiNaC/work/GiNaC-1.2.0" && make all" returned error 2 Command output: ld: warning multiple definitions of symbol _BC /opt/local/lib/libreadline.dylib(terminal.so) definition of _BC /usr/lib/libncurses.dylib(lib_termcap.o) definition of _BC ld: warning multiple definitions of symbol _UP /opt/local/lib/libreadline.dylib(terminal.so) definition of _UP /usr/lib/libncurses.dylib(lib_termcap.o) definition of _UP ld: Undefined symbols: __GLOBAL__I_cl_module__cl_C_ring__firstglobalfun __GLOBAL__I_cl_module__cl_DF_globals__firstglobalfun __GLOBAL__I_cl_module__cl_FF_globals__firstglobalfun __GLOBAL__I_cl_module__cl_GV_I__firstglobalfun __GLOBAL__I_cl_module__cl_GV_number__firstglobalfun __GLOBAL__I_cl_module__cl_I_ring__firstglobalfun __GLOBAL__I_cl_module__cl_LF_globals__firstglobalfun __GLOBAL__I_cl_module__cl_MI__firstglobalfun __GLOBAL__I_cl_module__cl_RA_ring__firstglobalfun __GLOBAL__I_cl_module__cl_R_ring__firstglobalfun __GLOBAL__I_cl_module__cl_SV_number__firstglobalfun __GLOBAL__I_cl_module__cl_SV_ringelt__firstglobalfun __GLOBAL__I_cl_module__cl_UP__firstglobalfun __GLOBAL__I_cl_module__cl_UP_no_ring__firstglobalfun __GLOBAL__I_cl_module__cl_ieee__firstglobalfun __GLOBAL__I_cl_module__cl_no_ring__firstglobalfun __GLOBAL__I_cl_module__cl_prin_globals__firstglobalfun __GLOBAL__I_cl_module__cl_random_def__firstglobalfun __GLOBAL__I_cl_module__cl_st_null__firstglobalfun __GLOBAL__I_cl_module__cl_symbol__firstglobalfun make[2]: *** [ginsh] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2

1 0

series expansion of powers.
by Chris Dams 21 Apr '04

21 Apr '04

Hello, Recently I had to find the power series to 11th order of the fifth power of a polynomial of degree 11 containing all kinds of symbols. The thing that was raised to the fifth power had 139 terms. The point of course is that in this case you do not want to have the full expansion of this power because it is way too large, takes too much time, and not necesary to find the answer. However, using the series method falls back on basic::series and this uses expand() internally. The conclusion would be that power::series is a bit to eager to use basic::series. Changing the line if (!must_expand_basis && !exponent.info(info_flags::negint)) that occurs in power::series into if (!must_expand_basis && !exponent.info(info_flags::negint) && !is_a<add>(basis)) makes this calculation finish within the second. Bye, Chris Dams

2 1

series taking too looooooong.
by Chris Dams 19 Apr '04

19 Apr '04

Hello, I found out that if I make the series expansion of a multiplication that has somewhere in it a factor to a rather large power (say 8), determining the lowest order of that takes very long. For instance, determinging the lowest order of b0^(-10)*(-2*b0^(-7)*log(-b0^(-2)*b1*recs)*b1^3*recs^4-b0^(-5)*log(-b0^(-2)*b1*recs)^2*b1^2*recs^3+b0^(-5)*b1^2*recs^3+b0^(-7)*log(-b0^(-2)*b1*recs)^3*b1^3*recs^4+b0^(-3)*log(-b0^(-2)*b1*recs)*b1*recs^2+3*b0^(-6)*b2*log(-b0^(-2)*b1*recs)*b1*recs^4-1/2*b0^(-7)*b1^3*recs^4-b0^(-4)*b2*recs^3+1/2*b0^(-5)*recs^4*b3-b0^(-1)*recs-b0^(-5)*log(-b0^(-2)*b1*recs)*b1^2*recs^3+5/2*b0^(-7)*log(-b0^(-2)*b1*recs)^2*b1^3*recs^4)^8*b1^9 with respect to the variable recs takes a few seconds on my pentium 1.8 GHz. The attached patch should make this much faster by determining the lowest order of the base and simply multiplying it with the exponent. Bye, Chris

2 1

expansion of log
by Chris Dams 19 Apr '04

19 Apr '04

Hello all, The patch I sent last friday turned up in the source. That's the good part, but unfortunately at the wrong spot. The line const ex newarg = ex_to<pseries>((arg/coeff).series(rel, order+n, options)).shift_exponents(-n).convert_to_poly(true); should appear after the patch. If it comes before, the patch does not solve anything. Bye, Chris Dams

2 2