upgrading VIM errors

[Ryan Schmidt]

On Jan 20, 2009, at 12:58, Timothy Goins wrote:

> Thanks, Joel, that worked.  However, I ran into two problems that I  
> found interesting.  When I ran "tim at cotopaxi:~$ sudo port clean -- 
> all vim" the call returned "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_edito 
> rs_vim/work/.macports.vim.state is not writable - check permission  
> on port directory..."
>
> When I did an "ls -al" the command returned the following:
>
> drwxr-xr-x   4 root  admin   136 Jan 18 16:55 .
> drwxr-xr-x   3 root  admin   102 Jan 18 16:55 ..
> -rw-r--r--   1 root  admin   144 Jan 18 16:55 .macports.vim.state
> drwxr-xr-x  43 root  admin  1462 Jan 18 16:55 vim72
>
> Huh?  So, I did a chmod 666 on .macports.vim.state (although that  
> didn't make much sense to me, since the file and directories were  
> all writable by root) and ran "sudo port -f clean -all vim" and all  
> was well.  I'm going to try a similar procedure on openssl, the  
> only other active ports I can't seem to upgrade.

I cannot explain that; a command run using sudo should have  
permission to do virtually anything.

> Okay, entirely different situation.  "sudo port upgrade openssl"  
> looks for "cc", which somewhere along the way had disappeared from  
> "/usr/bin."  So I created a symlink from /usr/gcc-4.0 to "cc" and  
> all went well!

If /usr/bin/cc was absent from your system, it should not have been;  
if you got that symlink recreated pointing to gcc-4.0, then that's fine.

Ports should compile using /usr/bin/gcc-4.0 (or, more specifically, $ 
{configure.compiler}); if openssl is using "cc", then a bug needs to  
be filed against openssl.