Opened 6 months ago

Last modified 6 months ago

#72978 assigned defect

swi-prolog @9.2.9: error: called object type 'int' is not a function or function pointer

Reported by: kwolcott Owned by: JanWielemaker (Jan Wielemaker)
Priority: Normal Milestone:
Component: ports Version: 2.11.5
Keywords: sequoia arm64 Cc:
Port: swi-prolog

Description (last modified by ryandesign (Ryan Carsten Schmidt)) 

:info:build /opt/local/var/macports/build/swi-prolog-69760e54/work/swipl-9.2.9/src/pl-thread.c:7784:13: error: called object type 'int' is not a function or function pointer
:info:build  7784 |   if ( false(def, P_THREAD_LOCAL) )
:info:build       |        ~~~~~^
:info:build 1 error generated.

Attachments (1)

port_swi-prolog_install_failed.log.bz2​ (15.0 KB) - added by kwolcott 6 months ago.

Download all attachments as: .zip

Change History (5)

Changed 6 months ago by kwolcott

Attachment: port_swi-prolog_install_failed.log.bz2​ added

comment:1 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Keywords: sequoia arm64 added
Owner: set to JanWielemaker
Port: swi-prolog added
Status: new → assigned
Summary: swi-prolog port fails to build on arm64: called object type 'int' is not a function or function pointer → swi-prolog @9.2.9: error: called object type 'int' is not a function or function pointer
Version: → 2.11.5

comment:2 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)

It looks like this was ​fixed one year ago but is apparently not included in this version.

comment:3 Changed 6 months ago by JanWielemaker (Jan Wielemaker)

It is probably not just one commit. There is a hole lot of changed to make the system compile cleanly on modern C compilers and exploit some of these goodies to simplify the code. I do not have time to backport these. I rather spent my time on moving to a new stable series (9.4.x). I'd expect that to be released later this year. Surely 9.4.0 will be pretty close to the current 9.3.30. Ideally we'd have some note in the swi-prolog port.

comment:4 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)

Meanwhile, if it's just a matter of the code not being compatible with new compilers, you can list all the incompatible compilers in compiler.blacklist and MacPorts will pick a different one.

Note: See TracTickets for help on using tickets.