#34102: configure: error: Could not find a working Foundation implementation -------------------------------+-------------------------------------------- Reporter: cquiter@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.0.4 Keywords: | Port: -------------------------------+-------------------------------------------- Comment(by cquiter@…): Thanks, I looked at (#28452, #30298) but noticed they had other errors in their config.log that I don't have. I tried moving /usr/local then building as well as installing with the disk image, but no luck. Installing with the disk image causes a bash process to run at 33% CPU for at least an hour until I reboot the system. I should note that MacPorts installed correctly and started acting up only after I tried to install python bindings for opencv. I tried to reinstall. Then I tried to uninstall/reinstall. However, I get the same result. I also tried removing MacPorts from the .profile. I tried installing the 2.1.0 .pkg and the package says it installs (no CPU problems) but when I use port I get errors about /opt/local/etc/macports files. After copying defaults I get: {{{ Craigs-MacBook-Pro:~ cquiter$ port Warning: No index(es) found! Have you synced your source indexes? port registry doesn't exist at "/opt/local/var/macports/registry/registry.db" and couldn't write to this location while executing "registry::open $db_path" (procedure "mportinit" line 633) invoked from within "mportinit ui_options global_options global_variations" Error: /opt/local/bin/port: Failed to initialize MacPorts, port registry doesn't exist at "/opt/local/var/macports/registry/registry.db" and couldn't write to this location }}} I get the same error about the Foundation implementation when building 2.1.0-beta1. Also, I have Foundation.framework but not Foundation.h. Reinstall OS X, really?! Replying to [comment:1 ryandesign@…]:
Please remember to use WikiFormatting.
"Could not find a working Foundation implementation" has been reported to us a couple times before (#28452, #30298) but we were never able to find out why it happened.
Do you have anything in /usr/local? If so, that might be interfering; try moving it aside.
Do you have /System/Library/Frameworks/Foundation.framework? Do you have /System/Library/Frameworks/Foundation.framework/Headers/Foundation.h? If not, reinstall OS X.
Compiling MacPorts manually should of course work, but out of curiosity, why do you want to do so instead of using our pre-made disk images?
Since we are about to release MacPorts 2.1.0, you could also test whether version 2.1.0 beta 1 works better, but I don't recall us making any changes with regard to this configure check so I doubt it.
-- Ticket URL: <https://trac.macports.org/ticket/34102#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS