Re: [MacPorts] #74362: port 2.12.6 does not build on PPC Leopard, Mac OS X 10.5.8, because of error: ‘CURLOPT_NOPROXY’ undeclared (first use in this function)

MacPorts noreply at macports.org
Sat Sep 5 18:03:34 UTC 2026


#74362: port 2.12.6 does not build on PPC Leopard, Mac OS X 10.5.8, because of
error: ‘CURLOPT_NOPROXY’ undeclared (first use in this function)
------------------------+-----------------------------
  Reporter:  ballapete  |      Owner:  (none)
      Type:  defect     |     Status:  closed
  Priority:  Normal     |  Milestone:  MacPorts Future
 Component:  base       |    Version:  2.12.6
Resolution:  fixed      |   Keywords:  leopard
      Port:  port       |
------------------------+-----------------------------

Comment (by fhgwright):

 Replying to [comment:8 ballapete]:
 > Replying to [comment:7 fhgwright]:
 > > Replying to [comment:6 ballapete]:
 > > > When will a functioning software be available for Mac OS X 10.5.8,
 Leopard?
 > >
 > > In the meantime, the easiest way to get the fix is probably:
 > >
 > > {{{
 > > sudo port build MacPorts
 > > cd $(port work MacPorts)/MacPorts-2.12.6
 > > sudo make install
 > > }}}
 >
 > Why can I perform something manually without applying patches that port
 cannot?
 >
 > >
 > My concern is not having an outdated version of MacPorts – as long as it
 works for me it's fine. Over one week ago it stopped working: it's not
 possible to update Portfiles and patch files. And maybe port is on strike
 and won't perform anything until the advertised new version is installed.
 (Did not try yet.)
 >
 > This needs a fix.

 Presumably your only issue is that `port selfupdate` is failing due to
 tripping over the broken 10.5 build and not honoring `-p`.  If your ports
 tree is new enough to include the `MacPorts` port with the patch, then
 what I suggested above should work, and then things should work normally
 afterward.  If your ports tree is too old, you may have to do a `port
 sync` first to get the updated `MacPorts` port.

 Admittedly, this requires using `port sync`, which I usually don't trust
 since its documentation is so outdated that it still talks about how it
 interacts with SubVersion, with no mention of what it may or may not do if
 you're using `git`. :-)

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


More information about the macports-tickets mailing list