[MacPorts] #64102: gettext @0.21 : build fails on tiger due to new libproc.h requirement

MacPorts noreply at macports.org
Thu Dec 2 02:32:45 UTC 2021


#64102: gettext @0.21 : build fails on tiger due to new libproc.h requirement
------------------------+------------------------
  Reporter:  alex-free  |      Owner:  ryandesign
      Type:  defect     |     Status:  accepted
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.7.1
Resolution:             |   Keywords:  tiger
      Port:  gettext    |
------------------------+------------------------

Comment (by alex-free):

 Replying to [comment:6 kencu]:
 > FYI, quite a bit of libproc is actually already in libSystem.dylib on
 Tiger Intel. It only needs the libproc.h header (see TigerBrew for an
 example) to work on Tiger.
 >
 > I did not bring this header into MacPorts because the guts are not there
 in Tiger PPC, which was all I really cared about. But it might do the job
 for Tiger Intel in some or most cases.
 >
 > libproc is hard to duplicate (I tried three years ago) as it needs
 kernel support for lots of things to work. Some of the simpler things
 libproc is used for, like the name or location of the process, can be
 duplicated in other ways, though.
 >
 > I did build a new kernel for TigerPPC that had some of the libproc
 support in it -- but then I realized that was a non-starter for MacPorts
 anyway, so abandoned that idea.

 Thanks for the insight. I know your custom kernel may be out of the realm
 for MacPorts, but I'd like to see how you did it just to learn more about
 how one goes about doing something like that.

 While trying to sort this issue out, I came across your post on messing
 around with libproc. I actually tried using the TigerBrew headers before
 reporting this and I still encountered linking issues, some proc library
 was unavailable. I can try this again and give more specific results if
 you'd like. Best scenario here is that upstream changes this requirement
 to an ifdef for systems without libproc in my opinion.

-- 
Ticket URL: <https://trac.macports.org/ticket/64102#comment:8>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list