[MacPorts] #61363: libiconv @1.16_1 build failure on os x 10.4: stdio.h: No such file or directory

[MacPorts]

#61363: libiconv @1.16_1 build failure on os x 10.4: stdio.h: No such file or
directory
------------------------+------------------------
  Reporter:  sheepdoll  |      Owner:  ryandesign
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.6.3
Resolution:             |   Keywords:  tiger
      Port:  libiconv   |
------------------------+------------------------

Comment (by ryandesign):

 Replying to [comment:15 sheepdoll]:
 > One issue with these legacy small machines is the whole package
 including man pages and docs are also downloaded and installed. This eats
 valuable drive space.

 Correct, ports install manpages, and there is no option to turn this off.
 Other documentation is sometimes available as a separate port or a variant
 that you can choose not to install, but other times it is included
 unconditionally in the main port. Our decisions about what to include in a
 port tend to be guided by what features many users will expect to be
 available, even if not all users need those features, and even if it comes
 at the expense of some disk space.

 > Pre-compiled binaries may be the solution to this bug this bug.
 Especially as apple had an 8GB limit to the maximum an ata drive could
 store at the time. A full install of X-code takes 2GB.

 I'm not familiar with an 8GB limit. From [https://lowendmac.com/2014
 /maximum-hard-drive-size/ what I read], on very early Mac OS X-capable
 Macs, the boot partition can be no larger than 8GB and must reside within
 the first 8GB of the disk, but the disk can be up to 128GB in size. Or you
 can add a second disk, such as a FireWire disk. So you should be able to
 have a small boot disk and then a larger disk or partition that you
 install MacPorts on.

 > As I recall my other G4 (running lion) had an Endian issue with some of
 the rendered images, part of why I wanted to do an install for the G3
 tiger.

 I'm not sure exactly what issue you're referring to here, but if the
 software you're trying to install has endian issues on a G4, then you'll
 almost certainly see the same issues on a G3, since all PowerPC processors
 used in Macs use the same endianness. Snow Leopard and Lion and all later
 versions of macOS cannot be installed on a PowerPC, so you certainly do
 not have Lion on a G4.

 Replying to [comment:16 sheepdoll]:
 > I tried {{{port -b install libgcc7}}} and got a suggestion to file a bug
 as this package does not exits for "10.4.11 Tiger"
 >
 > So how do I get the precompiled-binaries (pakages) for gcc7?
 {{{http://packages.macports.org/NameOfThePort/}}} does not seem to have
 any legacy powerpc binaries.

 Apologies, the wording of the message is a little unclear. The message is
 not intended to instruct you to file a bug report unconditionally. Rather,
 it is meant to let you know that you can file a bug report if you believe
 the condition to be a bug.

 It it not a bug that there is no binary package available for Tiger. We
 have never offered any binary packages for any port for Tiger. For a time
 we offered binaries for Leopard on PowerPC, but the hardware doing those
 builds has failed and I have not spent the time to replace it. We are all
 volunteers who have limited time to work on MacPorts, and we are more
 likely to spend our time trying to fix the countless problems that Apple's
 release of Xcode 12 has caused for our ports, and the countless problems
 that Apple's impending release of Apple Silicon-based machines will cause,
 because those problems affect or will affect a much larger number of
 users.

 > THese are unlikly to change much for a 20 some year old system.

 That's not true in MacPorts. We don't have separate collections of ports
 for different operating systems, and we don't freeze our entire ports
 collection for old systems. Our ports tree sees a hundred changes every
 day. After each change, our build machines for 10.6 and later build the
 ports and make the binaries available. We could set up Power Macs running
 10.4 and 10.5 to try to build binaries for those systems, but right now we
 don't have that.

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