Make file problem

[Geoff Gillett]

Hmm yes I did change sources.conf while trying to get macports to  
work though the proxy at work. I gave up, a month ago. Interestingly  
this global change only affected a few ports.

Thanks for the help I expect the problem will disappear now.
Is there a way to use macports though a proxy?

Geoff.

On 05/06/2007, at 4:44 AM, Ryan Schmidt wrote:

> On Jun 4, 2007, at 11:41, Geoff Gillett wrote:
>
>> Error: Target com.apple.destroot returned: shell command " cd "/ 
>> opt/local/var/db/dports/build/ 
>> _opt_local_var_db_dports_sources_rsync.rsync.macports.org: 
>> 873_dpupdate_dports_devel_ncursesw/work/ncurses-5.6" && make  
>> install DESTDIR=/opt/local/var/db/dports/build/ 
>> _opt_local_var_db_dports_sources_rsync.rsync.macports.org: 
>> 873_dpupdate_dports_devel_ncursesw/work/destroot " returned error 2
>> Command output: cd man && make DESTDIR="/opt/local/var/db/dports/ 
>> build/_opt_local_var_db_dports_sources_rsync.rsync.macports.org: 
>> 873_dpupdate_dports_devel_ncursesw/work/destroot" install
>> Makefile:54: *** target pattern contains no `%'.  Stop.
>> make: *** [install] Error 2
>>
>> I am running OSX 10.4.9 on ppc and have run selfupdate. This error  
>> has been happening for well over a month I get the same error with  
>> freetype (Makefile:54: *** target pattern contains no `%'. ) and I  
>> think a few other ports. I have done full cleans.
>
> I haven't heard of this problem before... I have no problem  
> installing ncursesw or freetype on 10.4.9 on PowerPC or Intel.
>
> Do you have the latest version of Xcode, 2.4.1? If not, get it from  
> Apple Developer Connection.
>
> Searching for this error on Google I get this message:
>
> http://lists.trolltech.com/qt-interest/2005-02/thread01024-0.html
>
> It seems that this error can occur if your path contains a colon,  
> and it looks like yours does:
>
> /opt/local/var/db/dports/build/ 
> _opt_local_var_db_dports_sources_rsync.rsync.macports.org: 
> 873_dpupdate_dports_devel_ncursesw
>
> We need to get that colon out of there. How did it get there? Did  
> you change your rsync definition in /opt/local/etc/ports/ 
> sources.conf to include a colon and the port number? If so, remove  
> that again.
>