[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:4 sheepdoll]:
 > The drive space is limitid, so I did remove the bloated OSX Gui SDKs as
 I was not expecting to build anything other than X11 unix type tools.

 What exactly do you mean by "OSX Gui SDKs"? What exactly did you remove?
 We'll probably ask you to reinstall it.

 > Now it is even worse I get the error:
 > {{{
 > $ sudo port install ghostscript
 > Error: Port ghostscript requires a full Xcode installation, which was
 not found on your system.
 > Error: You can install Xcode from the Mac App Store or
 https://developer.apple.com/xcode/
 > Error: Follow https://guide.macports.org/#project.tickets to report a
 bug.
 > Error: Processing of port ghostscript failed
 > }}}

 ghostscript doesn't specifically require a full Xcode install, but
 MacPorts will consider that all ports require a full Xcode install if
 either /usr/lib/libxcselect.dylib or
 /Library/Developer/CommandLineTools/usr/bin/make do not exist, which
 includes all systems running Mountain Lion or earlier.

 MacPorts will only get to the point of showing you this message if it
 cannot find Xcode installed. It determines that you have Xcode by running
 `xcodebuild -version`; try running that and see what it says. If
 `xcodebuild` doesn't exist or doesn't work, reinstall Xcode.

 > Somehow the re-install of Xcode removed the command line tools or paths
 without warning.

 Shouldn't have happened. The Xcode 2.5 installer defaults to installing
 Xcode and the command line tools; they should only not have been installed
 if you deliberately unchecked the checkbox in the installer.

 Based on the above, sounds like Xcode is not installed properly; reinstall
 it.

 > I am now re-installing macports and will report back when I have more
 info.

 Reinstalling MacPorts should change nothing. All you should need to do is
 correctly install the full unmodified Xcode, including its command line
 tools.

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