New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #28752 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

libvpx fails to build if dev tools are installed outside /Developer

Reported by: intrprog-sacrificial1@… Owned by: ryandesign@…
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

comment:1 in reply to: ↑ description Changed 2 years ago by ryandesign@…

  • Keywords developer_dir added; /Developer removed

Replying to intrprog-sacrificial1@…:

I wonder why a Unix dependency management system needs to look in the /Developer domain anyway.

libvpx specifically looks for SDKs in /Developer. Yes, we should correct this.

comment:2 Changed 2 years ago by ryandesign@…

  • Owner changed from macports-tickets@… to ryandesign@…
  • Status changed from new to assigned

comment:3 Changed 2 years ago by ryandesign@…

  • Status changed from assigned to closed
  • Resolution set to fixed

comment:4 Changed 2 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 2 years ago by ryandesign@…

Similar problems might absolutely exist in other ports. If you find them, please file individual tickets about them so we can fix them.

Note: See TracTickets for help on using tickets.