Re: upgrading VIM errors

2009-01-20 Thread Rainer Müller
Mark Hattam wrote:
 Portfile changed since last build; discarding previous state.
 ---  Fetching vim
 ---  Verifying checksum(s) for vim
 ---  Extracting vim
 ---  Applying patches to vim
 ---  Configuring vim
 ---  Building vim
 ---  Staging vim into destroot
 ---  Deactivating vim @7.2.077_0
 ---  Installing vim @7.2.077_1
 ---  Activating vim @7.2.077_1
 ---  Cleaning vim
 
 So the Portfile's changed but the same _1 version ... and it worked.

Thanks for the confirmation that the patch supplied by Bryan works. I
didn't bump the revision as the problem only affected users on install
and not users who already got it installed.

Rainer
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-20 Thread Joel Thibault (MacPorts)
On Tue, Jan 20, 2009 at 12:38 PM, Timothy Goins
ohce86-at-kitcarson.net|MacPorts|
doxvk95gt...@sneakemail.com wrote:

 When I attempt to *upgrade outdated* openssl and vim fail; all other ports
 upgrade.  Here is the error stream for the vim failure:
 t...@cotopaxi:~$ sudo port upgrade vim
 ---  Building vim
 Error: Target org.macports.build returned: shell command  cd
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_vim/work/vim72
  make all  returned error 2
 Command output: Starting make in the src directory.
 If there are problems, cd to the src directory and run make there
 cd src  make all
 /usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/include
 -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/FlatCarbon  -O
 -D_FORTIFY_SOURCE=1 version.c -o objects/version.o
   /usr/bin/gcc-4.0   -L/opt/local/lib -L/usr/local/lib -o vim
 objects/buffer.o objects/charset.o objects/diff.o objects/digraph.o
 objects/edit.o objects/eval.o objects/ex_cmds.o objects/ex_cmds2.o
 objects/ex_docmd.o objects/ex_eval.o objects/ex_getln.o objects/fileio.o
 objects/fold.o objects/getchar.o objects/hardcopy.o objects/hashtab.o
  objects/if_cscope.o objects/if_xcmdsrv.o objects/main.o objects/mark.o
 objects/memfile.o objects/memline.o objects/menu.o objects/message.o
 objects/misc1.o objects/misc2.o objects/move.o objects/mbyte.o
 objects/normal.o objects/ops.o objects/option.o objects/os_unix.o
 objects/pathdef.o objects/popupmnu.o objects/quickfix.o objects/regexp.o
 objects/screen.o objects/search.o objects/spell.o objects/syntax.o
  objects/tag.o objects/term.o objects/ui.o objects/undo.o objects/window.o
 objects/os_macosx.o objects/os_mac_conv.o  objects/netbeans.o
  objects/version.o   -lm  -lncurses -liconv -framework Carbon
 Undefined symbols:
   __Xsetlocale, referenced from:
   _get_locale_val in ex_cmds2.o
   _ex_language in ex_cmds2.o
   _ex_language in ex_cmds2.o
   _ex_language in ex_cmds2.o
   _main in main.o
   _main in main.o
   _enc_locale in mbyte.o
   _mac_lang_init in os_mac_conv.o
 ld: symbol(s) not found
 collect2: ld returned 1 exit status
 make[1]: *** [vim] Error 1
 make: *** [all] Error 2

 Error: Unable to upgrade port: 1



Try doing a selfupdate and clean first, at least for vim:

$ sudo port selfupdate
$ port clean --all vim
$ sudo port upgrade vim

That fixed the problem for me.

Joel



-- 
Joel Thibault [AIM: Jole Tebo]
Software Engineer in Boston
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-20 Thread William Davis


On Jan 20, 2009, at 12:48 PM, Joel Thibault (MacPorts) wrote:



On Tue, Jan 20, 2009 at 12:38 PM, Timothy Goins ohce86-at- 
kitcarson.net |MacPorts| doxvk95gt...@sneakemail.com wrote:
When I attempt to *upgrade outdated* openssl and vim fail; all other  
ports upgrade.  Here is the error stream for the vim failure:


t...@cotopaxi:~$ sudo port upgrade vim
---  Building vim
Error: Target org.macports.build returned: shell command  cd /opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_editors_vim/work/vim72  make all   
returned error 2

Command output: Starting make in the src directory.
If there are problems, cd to the src directory and run make there
cd src  make all
/usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/ 
include -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/ 
FlatCarbon  -O -D_FORTIFY_SOURCE=1 version.c -o objects/ 
version.o
  /usr/bin/gcc-4.0   -L/opt/local/lib -L/usr/local/lib 	-o vim  
objects/buffer.o objects/charset.o objects/diff.o objects/digraph.o  
objects/edit.o objects/eval.o objects/ex_cmds.o objects/ex_cmds2.o  
objects/ex_docmd.o objects/ex_eval.o objects/ex_getln.o objects/ 
fileio.o objects/fold.o objects/getchar.o objects/hardcopy.o objects/ 
hashtab.o  objects/if_cscope.o objects/if_xcmdsrv.o objects/main.o  
objects/mark.o objects/memfile.o objects/memline.o objects/menu.o  
objects/message.o objects/misc1.o objects/misc2.o objects/move.o  
objects/mbyte.o objects/normal.o objects/ops.o objects/option.o  
objects/os_unix.o objects/pathdef.o objects/popupmnu.o objects/ 
quickfix.o objects/regexp.o objects/screen.o objects/search.o  
objects/spell.o objects/syntax.o  objects/tag.o objects/term.o  
objects/ui.o objects/undo.o objects/window.o   objects/ 
os_macosx.o objects/os_mac_conv.o  objects/netbeans.o  objects/ 
version.o   -lm  -lncurses -liconv -framework Carbon

Undefined symbols:
  __Xsetlocale, referenced from:
  _get_locale_val in ex_cmds2.o
  _ex_language in ex_cmds2.o
  _ex_language in ex_cmds2.o
  _ex_language in ex_cmds2.o
  _main in main.o
  _main in main.o
  _enc_locale in mbyte.o
  _mac_lang_init in os_mac_conv.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[1]: *** [vim] Error 1
make: *** [all] Error 2

Error: Unable to upgrade port: 1


Try doing a selfupdate and clean first, at least for vim:

$ sudo port selfupdate
$ port clean --all vim
$ sudo port upgrade vim

That fixed the problem for me.

Joel



--
Joel Thibault [AIM: Jole Tebo]
Software Engineer in Boston


fixed it for me also


William Davis
frstanATbellsouthDOTnet
Mac OS X.5.6 Darwin 9.5.0
XQuartz 2.3.2 (xorg-server 1.4.2-apple31)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-20 Thread Timothy Goins
Thanks, Joel, that worked.  However, I ran into two problems that I  
found interesting.  When I ran t...@cotopaxi:~$ sudo port clean --all  
vim the call returned /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_editors_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.


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!


Thanks again,

Tim

On Jan 20, 2009, at 10:48 AM, Joel Thibault wrote:

[snip]

Undefined symbols:
  __Xsetlocale, referenced from:
  _get_locale_val in ex_cmds2.o
  _ex_language in ex_cmds2.o
  _ex_language in ex_cmds2.o
  _ex_language in ex_cmds2.o
  _main in main.o
  _main in main.o
  _enc_locale in mbyte.o
  _mac_lang_init in os_mac_conv.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[1]: *** [vim] Error 1
make: *** [all] Error 2

Error: Unable to upgrade port: 1


Try doing a selfupdate and clean first, at least for vim:

$ sudo port selfupdate
$ port clean --all vim
$ sudo port upgrade vim

That fixed the problem for me.

Joel




smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-20 Thread 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 t...@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.



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-18 Thread Bryan Blackburn
On Mon, Jan 19, 2009 at 12:06:38AM +, Mark Hattam said:
[...]
 iMac:~ mark$ sudo port upgrade outdated
 ---  Fetching vim
 ---  Verifying checksum(s) for vim
 ---  Extracting vim
 ---  Applying patches to vim
 ---  Configuring vim
 ---  Building vim
[...]
 Undefined symbols:
   __Xsetlocale, referenced from:

Looks like #17606:

http://trac.macports.org/ticket/17606

Bryan

[...]

 Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-18 Thread Mark Hattam


On 19 Jan 2009, at 00:20, Bryan Blackburn wrote:


On Mon, Jan 19, 2009 at 12:06:38AM +, Mark Hattam said:
[...]

iMac:~ mark$ sudo port upgrade outdated
---  Fetching vim
---  Verifying checksum(s) for vim
---  Extracting vim
---  Applying patches to vim
---  Configuring vim
---  Building vim

[...]

Undefined symbols:
 __Xsetlocale, referenced from:


Looks like #17606:

http://trac.macports.org/ticket/17606

Bryan

[...]


Mark



The previous version upgrade built without a problem ... so this seems  
a newer problem - or a problem that didn't affect 7.2.077_0


vim7.2.077_0  7.2.077_1

Today update seems to have been forced as a result of the X11  
changes detailed in the email

subject: [45603] trunk/dports
x11 dependent ports: Force port: based X11 dependencies

Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-18 Thread Timothy Goins
I get exactly the same error output; however, I'm upgrading (or trying  
to) from vim @7.2.021_0 (active).  Also lots of xorg upgrades that  
succeed and a python that doesn't.  Frustrating!  openssl and vim are  
the only active ports that are outdated and won't upgrade on my system.


Tim
On Jan 18, 2009, at 5:06 PM, Mark Hattam wrote:

Did a selfupdate on Macports 1.7 running on OSX 10.5.6, then a port  
outdated ...


iMac:~ mark$ sudo port outdated
The following installed ports are outdated:
vim7.2.077_0  7.2.077_1


iMac:~ mark$ sudo port upgrade outdated
---  Fetching vim
---  Verifying checksum(s) for vim
---  Extracting vim
---  Applying patches to vim
---  Configuring vim
---  Building vim
Error: Target org.macports.build returned: shell command  cd /opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_editors_vim/work/vim72  make all   
returned error 2
Command output: /usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/ 
opt/local/include -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/ 
Headers/FlatCarbon  -O -D_FORTIFY_SOURCE=1 -o objects/ 
quickfix.o quickfix.c
/usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/ 
include -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/ 
FlatCarbon  -O -D_FORTIFY_SOURCE=1 -o objects/regexp.o  
regexp.c


[lots more of these FORTIFY_SOURCE lines ending with ...]

/usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/ 
include -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/ 
FlatCarbon  -O -D_FORTIFY_SOURCE=1 version.c -o objects/ 
version.o
 /usr/bin/gcc-4.0   -L/opt/local/lib 	-o vim objects/buffer.o  
objects/charset.o objects/diff.o objects/digraph.o objects/edit.o  
objects/eval.o objects/ex_cmds.o objects/ex_cmds2.o objects/ 
ex_docmd.o objects/ex_eval.o objects/ex_getln.o objects/fileio.o  
objects/fold.o objects/getchar.o objects/hardcopy.o objects/ 
hashtab.o  objects/if_cscope.o objects/if_xcmdsrv.o objects/main.o  
objects/mark.o objects/memfile.o objects/memline.o objects/menu.o  
objects/message.o objects/misc1.o objects/misc2.o objects/move.o  
objects/mbyte.o objects/normal.o objects/ops.o objects/option.o  
objects/os_unix.o objects/pathdef.o objects/popupmnu.o objects/ 
quickfix.o objects/regexp.o objects/screen.o objects/search.o  
objects/spell.o objects/syntax.o  objects/tag.o objects/term.o  
objects/ui.o objects/undo.o objects/window.o   objects/ 
os_macosx.o objects/os_mac_conv.o  objects/netbeans.o  objects/ 
version.o   -lm  -lncurses -liconv -framework Carbon

Undefined symbols:
 __Xsetlocale, referenced from:
 _get_locale_val in ex_cmds2.o
 _ex_language in ex_cmds2.o
 _ex_language in ex_cmds2.o
 _ex_language in ex_cmds2.o
 _main in main.o
 _main in main.o
 _enc_locale in mbyte.o
 _mac_lang_init in os_mac_conv.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[1]: *** [vim] Error 1
make: *** [all] Error 2

Error: Unable to upgrade port: 1


Previous updates to VIM have worked OK.

iMac:~ mark$ sudo port installed | grep vim
 vim @7.2.077_0 (active)


Previously today, gd2 was updated
---  Deactivating gd2 @2.0.35_2
---  Installing gd2 @2.0.35_3

whose upgrade process downloaded, built, installed and activated 70  
(seventy) xorg- packages ...



Mark

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users




smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-18 Thread Ryan Schmidt


On Jan 18, 2009, at 18:51, Adam Dershowitz wrote:

Along the way it also installed python26!  It looks like this is  
because it installed xorg-xcb-proto @1.3_0+python26.  I am not sure  
if this will work or not because I have not, and was not planning  
to run:  sudo python_select python26.


It is not necessary to run sudo python_select python26 unless you  
want to be able to type python and have it run python26. Any port  
that depends on python26 (or any other python) should function  
correctly without using python_select. Perhaps the message printed by  
the python ports could be worded differently, so that it is not  
implied that running python_select is necessary.



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-18 Thread Bryan Blackburn
On Sun, Jan 18, 2009 at 07:49:16PM -0600, Ryan Schmidt said:

 On Jan 18, 2009, at 18:51, Adam Dershowitz wrote:

 Along the way it also installed python26!  It looks like this is  
 because it installed xorg-xcb-proto @1.3_0+python26.  I am not sure if 
 this will work or not because I have not, and was not planning to run:  
 sudo python_select python26.

 It is not necessary to run sudo python_select python26 unless you want 
 to be able to type python and have it run python26. Any port that 
 depends on python26 (or any other python) should function correctly 
 without using python_select. Perhaps the message printed by the python 
 ports could be worded differently, so that it is not implied that running 
 python_select is necessary.

There could be some ports which do in fact need a version selected as the
Current version setting for the framework
(${prefix}/Library/Frameworks/Python.framework/Version/Current and the
symlinks in just Python.framework/) are used when linking to it.

Thought I believe it's been suggested before that the first python port
installed should probably be automatically python_select'd...

Bryan

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users