Opened 3 weeks ago

Last modified 2 weeks ago

#71135 new defect

ucblogo @6.2.4: error: incompatible function pointer types passing 'void (void)' to parameter of type 'void (*)(int)' [-Wincompatible-function-pointer-types]

Reported by: frink0 (Liam Stitt) Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: sequoia Cc:
Port: ucblogo

Description

Hi. This doesn't build, but the current version on github (still tagged as 6.2.4) builds without issue.

Change History (3)

comment:1 Changed 2 weeks ago by frink0 (Liam Stitt)

Port: ucblogo added

comment:2 in reply to:  description Changed 2 weeks ago by ryandesign (Ryan Carsten Schmidt)

Keywords: sequoia added
Summary: ucblogo: port fails to build on Sequoiaucblogo @6.2.4: error: incompatible function pointer types passing 'void (void)' to parameter of type 'void (*)(int)' [-Wincompatible-function-pointer-types]

Replying to frink0:

Hi. This doesn't build,

We also see a build failure on our buildbot; presumably this is the same error you saw:

https://build.macports.org/builders/ports-15_x86_64-builder/builds/17977/steps/install-port/logs/stdio

main.c:106:19: error: incompatible function pointer types passing 'void (void)' to parameter of type 'void (*)(int)' [-Wincompatible-function-pointer-types]
  106 |           signal(SIGINT, logo_stop);
      |                          ^~~~~~~~~

but the current version on github (still tagged as 6.2.4) builds without issue.

I'm not sure what you mean. The latest released version is 6.2.4. It was released March 27, 2023 (not July 2, 2024, as claimed on the web site). It has the problem you experienced.

Maybe you mean the latest code in their GitHub repository which has not yet been tagged as a stable version builds for you. In that case, we would want to identify which specific change fixes the problem and backport that patch to 6.2.4. It may be one or more of the changes mentioned in this bug report.

comment:3 Changed 2 weeks ago by frink0 (Liam Stitt)

Hi. Yes, I meant the current GitHub HEAD.

Note: See TracTickets for help on using tickets.