libsndfile build error on OS X 10.8 with old /Developer dir present

[benedikt@…]

After the upgrade to mountain lion and Xcode 4.4 two days ago MacPorts started rebuilding all my installed ports. Everything went fine ( except for some minor tweaks), but it fails building libsndfile. I already found the #include bug it had a couple of years ago, but that was fixed. This one look's the same to me.

sudo port upgrade outdated 
dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid
--->  Computing dependencies for libsndfile
--->  Building libsndfile
Error: org.macports.build for port libsndfile returned: command execution failed
Please see the log file for port libsndfile for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_audio_libsndfile/libsndfile/main.log
Error: Problem while installing libsndfile
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

I've also attached to log file in which one can see what i mean.

I tried to uninstall libsndfile and it simply does nothing, even with the -f option. Clang build libsndfile just fine when I download it and compile it by hand, but not from within MacPorts

[benedikt@…]

build log

[benedikt@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

This log was not from a clean build attempt. Please "sudo port clean libsndfile", then try again, then attach the new main.log to this ticket if it fails again.

[benedikt@…]

Sry I did so many build that I forgot to clean it before. Here is the fresh one.

[ryandesign (Ryan Carsten Schmidt)]

It builds fine for me on Mountain Lion 10.8.0 and Xcode 4.4.

Your log says:

:info:build /System/Library/Frameworks/CoreFoundation.framework/Headers/CFArray.h:49:1: error: unknown type name 'CF_IMPLICIT_BRIDGING_ENABLED'

I haven't seen this before, and there's only one Google result for "CF_IMPLICIT_BRIDGING_ENABLED" which wasn't helpful.

[benedikt@…]

That's why I'm asking

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #35383.

[ks+macports@…]

Something (prolly CFArray.h or sndfile-play.c) needs to #include "CFBase.h". IMO, CFArray.h is broken, but that's Apple's problem.

 > grep -rsn CF_IMPLICIT_BRIDGING_ENABLED /System/Library/Frameworks/*/Headers
...
/System/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:297:#ifndef CF_IMPLICIT_BRIDGING_ENABLED
/System/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:299:#define CF_IMPLICIT_BRIDGING_ENABLED _Pragma("clang arc_cf_code_audited begin")
/System/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:301:#define CF_IMPLICIT_BRIDGING_ENABLED
...

[ks+macports@…]

/System/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:146 eventually includes /System/Library/Frameworks/CoreFoundation.framework/Headers/CFArray.h before it defines CF_IMPLICIT_BRIDGING_ENABLED at line 297. Looks like a broken CoreFoundation header. Try to force -DCF_IMPLICIT_BRIDGING_ENABLED on the cc line?

:info:build   CC     sndfile-play.o
:info:build In file included from sndfile-play.c:61:
:info:build In file included from /System/Library/Frameworks/CoreAudio.framework/Headers/AudioHardware.h:83:
:info:build In file included from /System/Library/Frameworks/CoreAudio.framework/Headers/CoreAudioTypes.h:28:
:info:build In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:146:
:info:build In file included from /Developer/Headers/FlatCarbon/MacTypes.h:1:
:info:build In file included from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:18:
:info:build In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20:
:info:build In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:18:
:info:build In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:39:
:info:build /System/Library/Frameworks/CoreFoundation.framework/Headers/CFArray.h:49:1: error: unknown type name 'CF_IMPLICIT_BRIDGING_ENABLED'
:info:build CF_IMPLICIT_BRIDGING_ENABLED
:info:build ^
:info:build /System/Library/Frameworks/CoreFoundation.framework/Headers/CFArray.h:50:18: error: expected ';' after top level declarator

[benedikt@…]

How do I force it? I'd like to test that.

[ks+macports@…]

Replying to benedikt@…:

How do I force it? I'd like to test that.

Maybe:

CFLAGS='-DCF_IMPLICIT_BRIDGING_ENABLED' port install libsndfile

I haven't tried it.

[benedikt@…]

Just tried it and it didn't help.

[MacPorts@…]

Cc Me!

[thomas@…]

Cc Me!

[seancd91@…]

I had the same issue, too. However, I noticed that the log files referenced "/Developer/Headers/FlatCarbon/MacTypes.h" (line 472 on main1.log), which is from Xcode 4.2. I later placed my /Developer directory in the trash, cleaned and reinstalled libsndfile, and it compiled successfully. Maybe it was an issue with the configuration file or autotools.

Hope this helps.

[benedikt@…]

Well that's cool it worked. Thank you!

[g@…]

Why can I delete the /Developer directory? Is it useless at all? If this is not the case: why do we close this one?

[benedikt@…]

It's useless for Xcode > 4.4, because Xcode then keeps everything inside the Xcode App. So as long as you don't use an SDK not supported by Xcode 4.4 you can delete the /Developer directory. I didn't do that, because I didn't trust the switch to the new directory and I didn't think of any problems this might cause. So by deleting the /Developer folder the issue was fixed and the bugreport can be closed since I'm using Xcode 4.4 and Mountain Lion.

[adam@…]

"worksforme?" That's a crap answer for a problem that's biting a lot of users.

Look at how many duplicates of this bug are in the database. It's a real problem that's causing real headaches for people, and the fact that it can be hacked around by those in the know does nothing to mitigate its severity. Doing a "port upgrade outdated" should just work for users, even if they've just installed XCode 4.4, even if they had an earlier version of XCode installed before that.

Sure, removing the /Developer directory lets the whole process complete -- assuming users don't have any real reason to keep XCode 4.2 around. But it's an ugly workaround, and it's really hard to find. Do we honestly expect everyone to end up finding and reading through this particular bug report? No. And for those users, ports will just be broken.

This is a make system issue that should be trivial to fix for anyone familiar with how the whole ports build setup works. Unfortunately, I'm not in that camp or I'd send in a patch.

[adam@…]

Cc Me!

[mparchet@…]

Cc Me!

[mparchet@…]

Cc Me!

[MacPorts@…]

Cc Me!

[andreas@…]

Cc Me!

[jmroot (Joshua Root)]

Try after r98107. If that works, please report it upstream (as the port has no maintainer).

[jmroot (Joshua Root)]

Assuming fixed since nobody has said otherwise.