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]

#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 ballapete):

 Replying to [comment:12 fhgwright]:
 > Replying to [comment:10 ballapete]:
 >
 > What???  You're using a git tree as your primary ports tree ''and''
 relying on a ton of uncommitted changes?  You really ''are'' asking for
 trouble, aren't you?
 >
 It feels quite practical. Every few weeks I have to edit this or that
 Portfile to fix changes. And afterwards I re-portindex, because the
 programme does not like Portfiles containing '>>>>' or such…

 > Relying on uncommitted changes on a long-term basis is also a really bad
 idea.  Git commits and branches are lightweight and easily created; use
 them liberally.  You can always rearrange them later.  Any change that
 remains uncommitted for more than a day is a mistake.

 This might be true fo a developer who works with others on some project. I
 am just keeping adjustments until it's not necessary, until either a
 software developer or a MacPorts maintainer has implemented them.

 > Read what I wrote again.  I never said to use `port install`; I said to
 run `make install` from the appropriate directory in the build tree, which
 is not the same thing.  And of course this has to be on the machine in
 question; running it on a different machine doesn't help.

 I just took Port- and patch file from an up-to-date Mac. Building the
 software happened on the PowerBook with Leopard.

 OK, tomorrow trying `make install`. I assumed the "make" was a typo – when
 port starts why should make finish? (Because of patch phase?)

 > BTW, it appears that it's OK to rerun the package installer over an
 existing installation, but don't take my word for it without a good
 backup.

 Tomorrow… (with 13 hours of sunshine again, and maybe knowing then what
 "the package installer" is)


 Anyway, there should be an easier way to work around a failed
 `selfupdate`. Or to perform updating the ports descriptions and patch
 files despite an outdated base system.

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