Skip to content

Conversation

@trustbyte
Copy link
Contributor

Description

Type(s)
  • bugfix
  • enhancement
  • security fix
Tested on

macOS 26.1 25B78 arm64
Command Line Tools 26.1.0.0.1.1761104275

Verification

Have you

  • followed our Commit Message Guidelines?
  • squashed and minimized your commits?
  • checked that there aren't other open pull requests for the same change?
  • referenced existing tickets on Trac with full URL in commit message?
  • checked your Portfile with port lint?
  • tried existing tests with sudo port test?
  • tried a full install with sudo port -vst install?
  • tested basic functionality of all binary files?
  • checked that the Portfile's most important variants haven't been broken?

@trustbyte
Copy link
Contributor Author

@barracuda156 Ideas how to fix this port that uses mk-configure?

@barracuda156
Copy link
Contributor

@trustbyte I didn’t update it myself, so no, no idea.

@trustbyte
Copy link
Contributor Author

Sorry, should have been more exact, it is an mk-configure error (I suspect) and maybe as of owner of that one you have something on the matter.

@barracuda156
Copy link
Contributor

Maybe take a look at what FreeBSD is doing: https://github.com/freebsd/freebsd-ports/blob/main/devel/libmaa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants