Opened 4 years ago
Last modified 4 years ago
#62569 new defect
ossp-uuid @1.6.2: fatal error: 'sys/types.h' file not found
Reported by: | aforeman | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.4 |
Keywords: | bigsur | Cc: | jmroot (Joshua Root) |
Port: | ossp-uuid |
Description
Note that this bug has been reported before. The bug report was closed without being fixed!
Attachments (1)
Change History (3)
Changed 4 years ago by aforeman
comment:1 Changed 4 years ago by jmroot (Joshua Root)
Cc: | jmroot added |
---|
comment:2 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Summary: | Error: Failed to build ossp-uuid: command execution failed → ossp-uuid @1.6.2: fatal error: 'sys/types.h' file not found |
---|---|
Version: | → 2.6.4 |
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, even if you had selfupdated or synced right before installing.
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 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.)
Please confirm that you have selfupdated recently and that the patch file for this port is up to date: