Opened 14 years ago
Closed 13 years ago
#26348 closed defect (invalid)
cmake: stdio.h: No such file or directory
| Reported by: | sharon.dagan@… | Owned by: | cssdev |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | ports | Version: | 1.9.1 |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
| Port: | cmake |
Description
See log.
Attachments (2)
Change History (9)
Changed 14 years ago by sharon.dagan@…
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Owner: | changed from macports-tickets@… to css@… |
| Port: | cmake added |
| Summary: | can't install cmake → cmake: stdio.h: No such file or directory |
The first error in the log appears to be
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_cmake/work/cmake-2.8.2/Utilities/cmcompress/cmcompress.h:41:19: error: stdio.h: No such file or directory
Do you really not have /usr/include/stdio.h? That's pretty essential to compiling most things and is part of a standard install of Xcode, I think. (If not a part of Xcode, then it's a part of Mac OS X.) Try reinstalling Xcode, making sure you have the latest version; currently for Snow Leopard that's 3.2.3. Also consider upgrading from Mac OS X 10.6.1 to 10.6.4 and installing anything else Software Update might suggest.
comment:2 follow-up: 3 Changed 14 years ago by sharon.dagan@…
Of course I have stdio.h... I did not mention, but everything but 'cmake' builds just fine. For example: qt4-mac, wget, lynx - they all build perfectly OK, and then they run OK.
comment:3 Changed 14 years ago by sharon.dagan@…
Replying to sharon.dagan@…:
Of course I have stdio.h... I did not mention, but everything but 'cmake' builds just fine. For example: qt4-mac, wget, lynx - they all build perfectly OK, and then they run OK.
And I'm on 10.6.4.
comment:4 Changed 14 years ago by cssdev
| Status: | new → assigned |
|---|
It seems like something is wrong with your machine configuration, could you perhaps attach the CMakeCache.txt from your ${worksrcpath}? I'm curious if CMake is picking up something else from the environment. It should be /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_cmake/work/cmake-2.8.2/CMakeCache.txt
comment:6 Changed 13 years ago by cssdev
| Priority: | Normal → Low |
|---|
Any update? Similar to #28929, this appears to be an incomplete development configuration. I'll close this ticket for timeout otherwise, because it doesn't appear to be a general problem with the port.
comment:7 Changed 13 years ago by cssdev
| Resolution: | → invalid |
|---|---|
| Status: | assigned → closed |
Closing this ticket due to inactivity. The development environment must not have been installer properly.
main.log