portfile test for macosx 10.6.8 + libc++

Ken Cunningham ken.cunningham.webuse at gmail.com
Tue Jul 19 07:52:33 PDT 2016

You are completely correct, of course - upstream fixes would be ideal, and much preferred over fixing the portfile to repair upstream deficiencies. Most ports that use configure already seem to get these things brought in from the GnuLib replacements, I've found.

But I suppose I'm torn between what is ideal and what is attainable. I don't see upstream being responsive to these requests - quite reasonably I guess. Better things to do than support 8+ year old hardware. Most of these fixes seem to be added in case-by-case by the individual portfile maintainers.

These ports are all working for me here. My goal is only to be helpful, and allow others to share the outcome of my efforts. 

But I can certainly blog the modifications somewhere and let those interested find it that way, rather than clutter up macports with it, if that is preferred.



On 2016-07-19, at 7:20 AM, Ryan Schmidt wrote:

> On Jul 19, 2016, at 8:25 AM, Ken Cunningham wrote:
>> Perfect. Thanks!
>> There are a series of EFI32 machines stuck at 10.6.8 or at most 10.7. These can be EFI-hacked to run 10.11 but that hasn't worked for me yet.
>> I have found that almost any port I have tried to install can be installed on this system (so far), with minor surgery to replace a missing function or two (strnlen and getline being the two most common) and often replacing a few missing libraries or missing includes to fix errors during the build.
>> My goal would be to suggest minor mods to portfiles to allow others to do the same if they choose -- and perhaps to leverage this to similar systems (10.7 and 10.8 libc++) if it's easy to do so.
> Those issues you mentioned don't sound like they should be conditionalized in the portfile. If software wants to use functions like strnlen or getline which are not on all systems, the software should check for the existence of those functions in its configure script, and if not available, define and use suitable alternatives. Missing libraries or includes similarly sound like something that should affect all systems. If any conditionalizing needs to be done, it should be done in the project's build system, not the MacPorts portfile, since the problem is not unique to MacPorts.

More information about the macports-dev mailing list