issues with Xcode 4.3 in port install - help !

[Dominik Reichardt]

> 
> 
> Am 17.02.2012 um 17:55 schrieb Arturo Rinaldi <arty.net2 at gmail.com>:
> 
>> Nella citazione in data Fri Feb 17 17:40:46 2012, Dominik Reichardt ha scritto:
>>> I think the macports.conf instructions are partly wrong.
>>> Changing
>>> 
>>> #developer_dir       /Developer
>>> To
>>> 
>>> developer_dir
>>> doesn't make much sense. I'd say
>>> 
>>> developer_dir       /applications/xcode.app/contents/Developer
>>> makes more sense but I could ve wrong
>>> 
>>> Dom
>>> 
>>> Am 17.02.2012 um 16:54 schrieb Arturo Rinaldi <arty.net2 at gmail.com <mailto:arty.net2 at gmail.com>>:
>>> 
>>>> Nella citazione in data Fri Feb 17 15:46:49 2012, Jeremy Lavergne ha scritto:
>>>>>> do you mean "command line tools" in the preferences pane as unix tools ? i already did that !
>>>>> 
>>>>> I think he is referring to developer_dir in your macports.conf
>>>>> 
>>>>> 
>>>> 
>>>> i just followed the instructions at
>>>> https://trac.macports.org/wiki/Migration
>>>> 
>>>> sudo xcode-select -switch /Applications/Xcode.app
>>>> 
>>>> and then :
>>>> 
>>>> xcode-select -print-path returns -------> /Applications/Xcode.app/Contents/Developer
>>>> 
>>>> also modified
>>>> macports.conf and macports.conf.default
>>>> as described but still having the same error :
>>>> 
>>>> ---> Configuring libmowgli
>>>> Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
>>>> Log for libmowgli is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libmowgli/libmowgli/main.log
>>>> Error: Status 1 encountered during processing.
>>>> To report a bug, see <http://guide.macports.org/#project.tickets>
>>>> 
>>>> also made before this
>>>> 
>>>> sudo port clean all
>>>> 
>>>> Regards
>>>> 
>> 
>> @Ryan : i'll investigate on this
>> 
>> @Dom : i put that path as first try and still nothing
>> 
>> Regards
> 
> Thanks for checking.
> Another thing to try, the SDKs folder is not symlinked to the root of the developer folder anymore. Maybe you need to symlink it. It's in xcode.app/contents/developer/platforms/macos (or similar, not at my mac atm).
> 

Ok, can't figure out what's going wrong, too. My previous idea that the developer_dir entry in macports.conf needs to point was obviously wrong. The migration instructions are correct.
But I can't do anything through macports as well. 
It *seems* to not be able to find the SDK headers or any headers...
My "port upgrade outdated" tries to build libvpx. This fails and the config.err shows:

check_header pthread.h
check_cpp
BEGIN /tmp/vpx-conf-1628-10099.c
    1	#include "pthread.h"
    2	int x;
END /tmp/vpx-conf-1628-10099.c
/usr/bin/clang -pipe -O2 -arch x86_64 -isysroot -mmacosx-version-min=10.7 -m64 -fomit-frame-pointer -arch x86_64 -O3 -fPIC -E -o /tmp/vpx-conf-1628-25052.o /tmp/vpx-conf-1628-10099.c
/tmp/vpx-conf-1628-10099.c:1:10: fatal error: 'pthread.h' file not found
#include "pthread.h"
         ^
1 error generated.

check_header unistd.h
check_cpp
BEGIN /tmp/vpx-conf-1628-10099.c
    1	#include "unistd.h"
    2	int x;
END /tmp/vpx-conf-1628-10099.c
/usr/bin/clang -pipe -O2 -arch x86_64 -isysroot -mmacosx-version-min=10.7 -m64 -fomit-frame-pointer -arch x86_64 -O3 -fPIC -E -o /tmp/vpx-conf-1628-25052.o /tmp/vpx-conf-1628-10099.c
/tmp/vpx-conf-1628-10099.c:1:10: fatal error: 'unistd.h' file not found
#include "unistd.h"
         ^
1 error generated.

check_header stdio.h
check_cpp
BEGIN /tmp/vpx-conf-1628-10099.c
    1	#include "stdio.h"
    2	int x;
END /tmp/vpx-conf-1628-10099.c
/usr/bin/clang -pipe -O2 -arch x86_64 -isysroot -mmacosx-version-min=10.7 -m64 -fomit-frame-pointer -arch x86_64 -O3 -fPIC -Wall -Wdeclaration-after-statement -Wdisabled-optimization -Wpointer-arith -Wtype-limits -Wcast-qual -Wno-unused-function -E -o /tmp/vpx-conf-1628-25052.o /tmp/vpx-conf-1628-10099.c
/tmp/vpx-conf-1628-10099.c:1:10: fatal error: 'stdio.h' file not found
#include "stdio.h"
         ^
1 error generated.

of course these headers are there both in /usr/include and SDK/usr/include (for both SDKs in the xcode.app).
So... there is something going on with the SDKs I guess

Dom