From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 58274@debbugs.gnu.org
Subject: bug#58274: giac 1.9.0-21 fails to build
Date: Mon, 03 Oct 2022 10:34:39 -0400 [thread overview]
Message-ID: <87ill1j7r4.fsf@gmail.com> (raw)
Hi,
The build of giac fails like:
--8<---------------cut here---------------start------------->8---
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I. -I.. -g -O2 -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -DTIMEOUT -DHAVE_LIBMICROPYTHON -fpermissive -DQUICKJS -MT alg_ext.lo -MD -MP -MF .deps/alg_ext.Tpo -c alg_ext.cc -o alg_ext.o >/dev/null 2>&1
pari.cc:752:17: error: typedef ‘giac::PFGEN’ is initialized (use ‘decltype’ instead)
752 | typedef GEN (*PFGEN)(ANYARG);
| ^~~~~
pari.cc:752:24: error: ‘ANYARG’ was not declared in this scope
752 | typedef GEN (*PFGEN)(ANYARG);
| ^~~~~~
pari.cc: In function ‘giac::gen giac::in_pari(const giac::gen&, const giac::context*)’:
pari.cc:829:19: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
829 | argvec[k]= (GEN) v[j].val;
| ^~~~~~~~~~~~~~
pari.cc:847:19: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
847 | argvec[k]=(long int*)(pos -1);
| ^~~~~~~~~~~~~~~~~~~
pari.cc:855:17: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
855 | argvec[k]=(long int*) v[j].val;
| ^~~~~~~~~~~~~~~~~~~~
pari.cc:883:16: error: ‘PFGEN’ was not declared in this scope; did you mean ‘GEN’?
883 | res = ((PFGEN)call)(_ARGS_);
| ^~~~~
| GEN
pari.cc:883:22: error: expected ‘)’ before ‘call’
883 | res = ((PFGEN)call)(_ARGS_);
| ~ ^~~~
| )
pari.cc:887:20: error: expected primary-expression before ‘int’
887 | m = (long)((int (*)(ANYARG))call)(_ARGS_);
| ^~~
pari.cc:887:20: error: expected ‘)’ before ‘int’
887 | m = (long)((int (*)(ANYARG))call)(_ARGS_);
| ~^~~
| )
pari.cc:887:49: error: expected ‘)’ before ‘;’ token
887 | m = (long)((int (*)(ANYARG))call)(_ARGS_);
| ~ ^
| )
pari.cc:891:14: error: expected primary-expression before ‘long’
891 | m = ((long (*)(ANYARG))call)(_ARGS_);
| ^~~~
pari.cc:891:14: error: expected ‘)’ before ‘long’
891 | m = ((long (*)(ANYARG))call)(_ARGS_);
| ~^~~~
| )
pari.cc:891:44: error: expected ‘)’ before ‘;’ token
891 | m = ((long (*)(ANYARG))call)(_ARGS_);
| ~ ^
| )
pari.cc:895:10: error: expected primary-expression before ‘void’
895 | ((void (*)(ANYARG))call)(_ARGS_);
| ^~~~
pari.cc:895:10: error: expected ‘)’ before ‘void’
895 | ((void (*)(ANYARG))call)(_ARGS_);
| ~^~~~
| )
pari.cc:895:40: error: expected ‘)’ before ‘;’ token
895 | ((void (*)(ANYARG))call)(_ARGS_);
| ~ ^
| )
make[2]: *** [Makefile:814: pari.lo] Error 1
--8<---------------cut here---------------end--------------->8---
--
Thanks,
Maxim
next reply other threads:[~2022-10-03 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 14:34 Maxim Cournoyer [this message]
2022-10-07 20:17 ` bug#58274: giac 1.9.0-21 fails to build Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ill1j7r4.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=58274@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).