[MacPorts] #65561: Need help with Port - unalz
MacPorts
noreply at macports.org
Fri Jul 29 13:27:38 UTC 2022
#65561: Need help with Port - unalz
---------------------+----------------------
Reporter: RobK88 | Owner: RobK88
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.7.2
Resolution: | Keywords:
Port: unalz |
---------------------+----------------------
Comment (by RobK88):
Ryan and Joshua -- Many thanks for all the feedback.
I will definitely add a comment in the Portfile regarding the misuse of
CPP.
And I am planning to eliminate ALL the `reinplace` statements, when I
incorporate all the patch files from the Debian Project. And the first
two `reinplace` statements are no longer needed because I added `PortGroup
makefile 1.0` to the portfile.
(FYI -- Debian never bothered deleting all the `register` keywords in the
source. As you know the `register` keyword has been deprecated in C++17.
It will just compile fine on a compiler supporting C++17 but a warning
message will be thrown. I am debating whether to just keep `register` in
the source. It may help when the source is being compiled on older
compilers).
Ryan, thank you for your last comment! I checked the logs, and you are
right. The Apple clang compiler does understand the -stdlib flag. The
code did compile but it failed to link due to missing symbols. So I will
need to add CXXFLAGS everywhere CPP is being used to link! Duh! I should
have looked at the logs more carefully.
And finally, I would be grateful if you could give me some advice
regarding the homepage and master_sites. The homepage for `unalz` has
disappeared from the net. But I can find in in the Wayback Machine. So I
could use that instead in the portfile. But the link to the source is no
longer available (even on the Wayback Machine). I will keep looking for
another website for the source code. Alternatively, I could use the link
to the source code at the Debian project. (But then I will need to update
the portfile accordingly since as you know Debian uses its own
standardized format for source code filenames). Or I could leave the
portfile as is since Macports already has a copy of the source in its
repos.
--
Ticket URL: <https://trac.macports.org/ticket/65561#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list