Hey there all, I’m debugging an issue with FreeIPMI that you can go read about on the freeipmi-users mailing list if you care, but as part of that, the developer has asked me to git checkout the “master” branch from their github mirror and build against it, including running autogen to create a new “configure” script.
When I do that, ./configure cannot find libraries like gcrypt.h that are in /usr/local/include The maintainer tells me that I can set things like CFLAGS and LDFLAGS to fix this, but it feels like I should not have to do that for what I consider fairly standard library paths that shouldn’t need to be overridden. The ports tree version of freeipmi builds okay, but it’s checking out a “release” version that already has a configure script. So my questions: 1) Does the ports tree magically tweak CFLAGS or whatever when you build a port, to include things like /usr/local/include and /usr/local/lib? I don’t see anything that would do this in /usr/ports/Mk 2) Is there a standard method for ports that need to run autogen? 3) Is there some documentation somewhere on how to make a port (for testing purposes) that effectively just checks out a git hash (either via the git protocol directly, or via the github master tree), that one can use for testing so you can compare apples to apples, see if patches are still necessary, etc? Porter’s handbook shows how to check out a *tag*, but not a commit hash. Obviously, there’s no guarantee that the master.zip will always have the right size and checksum, but there are overrides for that. -Dan
