[MacPorts] #62569: ossp-uuid @1.6.2: fatal error: 'sys/types.h' file not found (was: Error: Failed to build ossp-uuid: command execution failed)
MacPorts
noreply at macports.org
Sun Mar 28 00:52:45 UTC 2021
#62569: ossp-uuid @1.6.2: fatal error: 'sys/types.h' file not found
------------------------+--------------------
Reporter: aforeman | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.6.4
Resolution: | Keywords: bigsur
Port: ossp-uuid |
------------------------+--------------------
Changes (by ryandesign):
* version: => 2.6.4
Comment:
Presumably the previous bug that was fixed that you are referring to was
#62227 but there's also #59951 and #62440 still open.
The log you attached shows twelve attempts to install the port. The first
attempt took place on February 6, which was the same day bug #62227 was
fixed, so you might not have received the fix yet on that day.
Attempts two through twelve contain the line `Skipping completed
org.macports.patch (ossp-uuid)` so even if you had synced or selfupdated
after February 6 and received the fix, MacPorts would not have attempted
to apply the new patch. The solution to that would be to clean the port
before trying again, as mentioned as the
[https://guide.macports.org/#project.tickets.prerequisites first thing you
should do before filing a bug report] in our guide. So please do that
(`sudo port clean ossp-uuid`) and of course sync (`sudo port sync`) before
trying again.
(To avoid this type of problem for users, whenever I modify a port's patch
file to fix a problem, I also modify the portfile, even if the portfile
change is an inconsequential one like a whitespace change, so that
MacPorts will recognize that the portfile has changed and auto-clean the
port. That wasn't done when #62227 was fixed which is why you have to
clean manually.)
--
Ticket URL: <https://trac.macports.org/ticket/62569#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list