|Justin Walker on Mon, 17 Nov 2003 00:47:29 +0100|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|Re: Building gp2c|
On Sunday, November 16, 2003, at 03:15 PM, Bill Allombert wrote:
On Sun, Nov 16, 2003 at 01:26:49PM -0800, Justin Walker wrote:Hi, again,
doc/Makefile.am:13: `#' comment at start of rule is unportable You must have automake to proceed. Sorry.What version of automake do you have ? All the version I tested did not break here. It seems yours try to improove its reputation of being nefarious.
:-} This is from version 1.6.3.
Somehow, the creation of 'dotest' from 'dotest.in' produced this line: command=`echo "/usr/bin/gcc -c -o %s.o -O3 -DGCC_INLINE -Wall -fomit-fram\ e-pointer -no-cpp-precomp -fno-common -I/usr/local/include %s.c && -o %s.dylib \ -shared -mimpure-text -O3 -DGCC_INLINE -Wall -fomit-frame-pointer -no-cpp-preco\ mp -fno-common %s.o " | sed -e s/%s/$i.gp/g` A similar line is present in scripts/Makefile.Obviously something cut long line with '\<newline>' for no reason. Could you check the pari.cfg file you used for modules_build ? grep modules_build pari.cfg should do. If the \ are also here it is a bug in PARI not in gp2c.
I think the "\" things are artifacts from my mailer. The line in scripts/dotest, as well as in scripts/Makefile and pari.cfg, looks like
... -I/usr/local/include %s.c && -o %s.dylib ...i.e., all one line. The problem is the "&& -o". Some macro that came between the "&&" and the "-o" does not have a value.
Anyway you can try to fix it manually by removing the \<newline> and get something likecommand=`echo "/usr/bin/gcc -c -o %s.o -O3 -DGCC_INLINE -Wall -fomit-frame-pointer -no-cpp-precomp -fno-common -I/usr/local/include %s.c && -o %s.dylib -shared -mimpure-text -O3 -DGCC_INLINE -Wall -fomit-frame-pointer -no-cpp-precomp -fno-common %s.o " | sed -e s/%s/$i.gp/g`
I think this line will elicit the same response (-o not found), because following the "&&", there should be a command, right? And what produces this line? Is it one of the "auto" commands?
What is expected there? I used 'gcc', and got complaints about undefined symbols like main, avma, bot, fetch_user_var, gadd, gcmp, ... , pari_err, polx.
What version of autoconf do you use, and what is /bin/sh here?
Autoconf is v. 2.57, and "/bin/sh" is the same as "/bin/bash". I think that 'bash' will behave differently when named 'sh', but I'm not positive.
Thanks for the help. Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Men are from Earth. | Women are from Earth. | Deal with it. *--------------------------------------*-------------------------------*