apache2 @2.4.52: error: implicit declaration of function 'ERR_GET_FUNC' is invalid in C99

[josephsacco]

The recent upgrade for openssl3 breaks apache2. Log file attached.

-Joseph

[josephsacco]

main.log

[Schamschula (Marius Schamschula)]

I'm not sure what is going on here. I got a clean rebuild on Mojave.

[josephsacco]

Apologies for being sloppy. This error occurs on Monterey.

-Joseph

[ryandesign (Ryan Carsten Schmidt)]

Here's a confirming log from the buildbot: ​https://build.macports.org/builders/ports-12_arm64-builder/builds/8149/steps/install-port/logs/stdio

[jmroot (Joshua Root)]

ERR_GET_FUNC is gone in openssl 3. ​https://www.openssl.org/news/changelog.html#openssl-30

[ryandesign (Ryan Carsten Schmidt)]

I'm not working on this right now if anyone else wants to.

[mascguy (Christopher Nielsen)]

Replying to jmroot:

ERR_GET_FUNC is gone in openssl 3. ​https://www.openssl.org/news/changelog.html#openssl-30

Agreed, based on the changelog. However, unless I'm missing something (?), why would builds be succeeding for pre-Monterey macOS versions...?

​https://ports.macports.org/port/apache2/builds/

[mascguy (Christopher Nielsen)]

It appears to be an implicit function declaration, causing a compilation failure on ARM. Yet, wouldn't one expect a link-time failure on x86_64, if that function truly doesn't exist anymore...?

ssl_engine_init.c:1375:22: error: implicit declaration of function 'ERR_GET_FUNC' is invalid in C99 [-Werror,-Wimplicit-function-declaration]

[Schamschula (Marius Schamschula)]

I get the same error on my Intel MBP running Monterey.

[jmroot (Joshua Root)]

Replying to mascguy:

Unless they're dynamically loading the library at runtime, I suppose.

Yes, that is exactly how apache modules work. It will be a runtime failure when built with a compiler that allows implicit declarations.

[Schamschula (Marius Schamschula)]

In 9535fdff21d764948182c6bc3f3c9e6fc318f23f/macports-ports (master):

apache2: fix "ERR_GET_FUNC" is invalid with openssl 3.0

Uses upstream patch
See: #63846

[ryandesign (Ryan Carsten Schmidt)]

Replying to mascguy:

why would builds be succeeding for pre-Monterey macOS versions...?

​https://ports.macports.org/port/apache2/builds/

Implicit declaration of function is an error in Xcode 12 or later, which is used by macOS 11 and later builders. macOS 10.15 and earlier builders use earlier Xcode versions in which implicit declaration of function is only a warning.

[mascguy (Christopher Nielsen)]

Replying to ryandesign:

Implicit declaration of function is an error in Xcode 12 or later, which is used by macOS 11 and later builders. macOS 10.15 and earlier builders use earlier Xcode versions in which implicit declaration of function is only a warning.

That's understood. What I failed to originally consider though, is the dynamic, pluggable nature of Apache. (And runtime linking, vs. build-time.)

Regardless, we need to step back, and consider where implicit function declarations are truly errors across-the-board. This is certainly one great example, and there are undoubtedly others.

[neverpanic (Clemens Lang)]

This issue was fixed with [9535fdff21d764948182c6bc3f3c9e6fc318f23f/macports-ports].