Fwd: GIMP | Argument -Wimplicit-function-declaration incompatible with Mac M1 arm64? (#6954)

[Peter West]

As advised by some previous messages regarding -Wimplicit-function-declaration, I reported this to Gimp bugs, and I received the reply below.

As mentioned in the response, gimp2 built for me, but hung on startup.

There’s a question here about the use of gimp-macos-build scripts and jhbuild, which I cannot answer.

Should this question go onto the dev list?

I am reluctant to get into the weeds of the gimp build, as I’ve never built anything complex on Mac before, but if no-one else is in a position to do so, I may have to. Any other M1 users who would like to see Gimp native, please put your hand up.


—
Peter West
pbw at ehealth.id.au
“…whoever says, ‘You fool!’ will be liable to the hell of fire.”

> Begin forwarded message:
> 
> From: "Jehan (@Jehan)" <gitlab-issues at gnome.org>
> Subject: Re: GIMP | Argument -Wimplicit-function-declaration incompatible with Mac M1 arm64? (#6954)
> Date: 10 June 2021 at 5:28:42 pm AEST
> To: pbw at pbw.id.au
> Reply-To: GNOME / GIMP <incoming+33b1afd72909024031f4a147c254c88d at gitlab.gnome.org>
> 
> Jehan <https://gitlab.gnome.org/Jehan> commented <https://gitlab.gnome.org/GNOME/gimp/-/issues/6954#note_1138635>:
> 
> Hi @p-b-west <https://gitlab.gnome.org/p-b-west> !
> 
> The build log includes this warning. Warning: Configuration logfiles contain indications of -Wimplicit-function-declaration; check that features were not accidentally disabled: strchr: found in gimp-2.10.22/config.log finite: found in gimp-2.10.22/config.log
> 
> Well you are our best bet to find the solution to this! Most of devs here don't use macOS which is why we have a hard time even providing the non-M1 build, even less the M1 one! 😕
> 
> In any case, yes there are a bunch of strchr in the code (both core and in plug-ins, as can be checked by a grep through code), so if it turns out this function is not available/disabled or that something needs to be done to have it on the build, you'd be the best fit to investigate it, especially since you at least got a first build to complete!
> 
> The other people who worked on a macOS build and who may be able to help are: @samm-git <https://gitlab.gnome.org/samm-git> and @DesMcGuinness <https://gitlab.gnome.org/DesMcGuinness> (for the main macOS build) and @evultrole <https://gitlab.gnome.org/evultrole> who worked on the M1 build, though I don't know what the status is now (see #5288 <https://gitlab.gnome.org/GNOME/gimp/-/issues/5288>).
> 
> By the way, does the MacPorts build use our gimp-macos-build scripts with jhbuild? Something different? Because obviously we are particularly interested to also have a working upstream M1 build!
> 
> — 
> Reply to this email directly or view it on GitLab <https://gitlab.gnome.org/GNOME/gimp/-/issues/6954#note_1138635>. 
> You're receiving this email because you have been mentioned on gitlab.gnome.org <http://gitlab.gnome.org/>. If you'd like to receive fewer emails, you can unsubscribe <https://gitlab.gnome.org/-/sent_notifications/33b1afd72909024031f4a147c254c88d/unsubscribe> from this thread or adjust your notification settings.
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20210611/0ffa6916/attachment.htm>