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 fhgwright):

 Replying to [comment:13 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.

 Git isn't just for collaboration - it also helps keep track of your own
 changes, and allows you to pick and choose which ones you want to include
 at any given time.

 > > 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.

 You also could have obtained it with git.  Even assuming you're not
 keeping your local master branch up to date, you could (assuming
 'upstream' is your name for the main repo):
 {{{
 git fetch upstream
 git checkout upstream/master sysutils/MacPorts
 cd sysutils/MacPorts
 sudo port build
 cd $(port work)/MacPorts-2.12.6
 sudo make install
 cd -
 cd ../..
 git restore --staged sysutils/MacPorts
 git restore sysutils/MacPorts
 }}}


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

 If I'd meant `port install`, why would I have included the `cd`?

 `port install` and `make install` in the port's build directory are
 completely different.  If you're not familiar with the difference, study
 the behavior of the phases more closely.

 > > 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)

 The package installer is what you download from the MacPorts website to
 get started.

 > 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.

 The only immediate problem caused by the failed selfupdate is that it
 prevents moving on to the implied `port sync` that follows.  Since you
 seem to think that you can't afford to do a `port sync` anyway, that's not
 much of a problem.

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