[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:8 sheepdoll]:
 > install apple-gcc42 +bootstrap seemed to have hung after a 12 hours,
 then exited with an error. (which I forgot to log as it was early in the
 morning.)

 If it exited with an error, then that's not a hang. :)

 Compilers can take a long time to compile. 12 hours or even much more
 might not be an unreasonable time to need to wait on an old PowerPC
 machine.

 > For now I am going to let the apple-gcc42 build run as it is accessing
 the disk.  (when it hung the disk acesses stopped.)  I also noticed that
 the free space went from 792MB to 162MB and I got a low disk space warning
 error. So it looks like the paging file may have overflowed. This is a
 pretty stripped down install to fit onto the 11GB drive.

 How much memory does the computer have? I wouldn't necessarily leap to the
 conclusion that the disk is filling up with swap space, but you can check
 if that is the case by examining the contents of /private/var/vm. It seems
 more likely to me that the build is using up the disk space as any build
 normally would and there just isn't enough space available for all the
 intermediate files it needs to build. 11GB may not be a large enough disk
 for having both the OS and Xcode installed and being able to compile
 software, especially something as large as a compiler.

 If you can temporarily attach an additional larger disk while building,
 you might be able to remove the directory /opt/local/var/macports/build
 and replace it with a symlink to a folder on your larger disk. MacPorts
 doesn't expect you to do this, so I'm not sure if it will fully work, but
 you could try it. Of course doing this will prevent building anything
 unless that additional disk is attached. You can revert the modification
 later by replacing the symlink with a real directory again.

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