http-parser: Please use the right compiler and -arch flags

[ryandesign (Ryan Carsten Schmidt)]

See summary and ​https://github.com/macports/macports-ports/commit/b97163ec8a73c05d6639d39c01025d612f5ba72f#r30698364.

[ryandesign (Ryan Carsten Schmidt)]

And if possible add a universal variant.

[ryandesign (Ryan Carsten Schmidt)]

Gregorio responded on GitHub:

Will take care of it as soon as I can. Also will try to see if I can use the regular configure; there must be a reason I did it like this but honestly I can't remember.

Looks like this software does not have a configure script.

Could you please point me to a reference for the best way to take care of the architectures?

Autotools configure scripts behave in a predictable standardized way, so MacPorts can automatically tell them how to use the right compiler and arch flags. But when autotools are not used, and the developer writes a custom Makefile, you have to read the Makefile and figure out how to pass this information to the Makefile, since it's going to be different depending on how the developer happened to write it.

Since I'm already looking at the Makefile now, I'll send a PR for the needed changes shortly.

[ryandesign (Ryan Carsten Schmidt)]

​https://github.com/macports/macports-ports/pull/2712

[ryandesign (Ryan Carsten Schmidt)]

In 978d6787fff82f71a0289188ead377d389bb8734/macports-ports (master):

http-parser: Use compiler, arch, universal

Use the right compiler and -arch flags and add a universal variant.

Closes #57247

Only build the library in the build phase; don't run the tests.

Enable the test phase so that the tests can be run if desired.

Fix the Makefile:

• Don't use -Werror
• Don't rebuild the library unless that's needed
• Use -dynamiclib instead of -shared on macOS