#28752 closed defect (fixed)
libvpx fails to build if dev tools are installed outside /Developer
| Reported by: | intrprog-sacrificial1@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | developer_dir | Cc: | |
| Port: | libvpx |
Description
libvpx fails to build if dev tools are installed outside /Developer. That says it all, basically (using 10.6.6, BTW). It fails during configure, here is the relevant part of the log: ... Darn, the error log is gone now that I've been able to build it correctly. Anyway, the configure check for pthread.h failed, because the compiler was invoked with -isysroot /Developer/SDKs/MacOSX10.6.sdk .
I do not install any variant of the dev tools in /Developer these days, because between the iOS SDK version, the version for Mac development only (the iOS SDK variant has from time to time bugs that prevent "real" Mac development), Xcode 4, and the prerelease versions (which one must install alongside the shipping ones since one cannot build App Store apps with them), there is no longer a canonical version that should go in /Developer. I wonder why a Unix dependency management system needs to look in the /Developer domain anyway.
Workaround is to create a symlink in /Developer/ (this folder nevertheless exists for CHUD) called SDKs to <wherever I installed the Xcode for Mac development>/SDKs.
Change History (5)
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Keywords: | developer_dir added; /Developer removed |
|---|
comment:2 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | changed from macports-tickets@… to ryandesign@… |
|---|---|
| Status: | new → assigned |
comment:3 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:4 Changed 14 years ago by intrprog-sacrificial1@…
That was fast, thanks. I forgot to tell this, but it might affect more than just libvpx - I was trying to build ffmpeg, and it's on libvpx that it tripped, but the problem might be in the other dependencies since by the time those were being built, the workaround was in place.
comment:5 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Similar problems might absolutely exist in other ports. If you find them, please file individual tickets about them so we can fix them.
Replying to intrprog-sacrificial1@…:
libvpx specifically looks for SDKs in /Developer. Yes, we should correct this.