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 <[email protected]>:

> 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
> 
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Reply via email to