Re: Vim upgrade lost spelling and syntax highlights
On 2014-03-05 00:08, LuKreme wrote: On 04 Mar 2014, at 11:34 , Rainer Müller rai...@macports.org wrote: On Tue, 04 Mar 2014 09:42:32 -0700, LuKreme wrote: Can't open file /opt/local/share/vim/syntax/syntax.vim Warning: Cannot find word list en.utf-8.spl or “en.ascii.spl Do you customize the 'runtimepath' setting in any way in your .vimrc? No. The only thing that has anything like a path is set spellfile=~/.spell.en.add Maybe some plugin changes runtimepath? Try without your .vimrc. The correct path for these files would be at /opt/local/share/vim/vim74/ (it's missing the vim74 directory in the message above...). I can't think of another reason why else vim would look in the wrong directory... Rainer ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: [MacPorts] #42672: x264 @20130823_0: universal build failure on Apple clang, i386 issues.
On 3/5/14 7:59 AM, René J.V. Bertin wrote: On Mar 05, 2014, at 09:55, Ryan Schmidt wrote: environment variables to build each architecture, if desired. It is not possible to specify different variants for each architecture; variants apply to the port as a whole. But I presume it would be possible to have architecture-specific options for a variant? If so, what I was suggesting as (temporary) fix, was to tweak the i386-specific asm options to render it harmless. Is it the case that the asm variant only works for the x86_64 architecture? Apparently, yes. If so, my proposed fix would be that the asm variant only be selectable if x86_64 is within the architectures that will be built, and if so, to only apply to that architecture and not any others. Are we saying the same thing? The other way of looking at it is this: is there a reason NOT to use the asm variant (at least for x86_64)? I suppose it exists for performance reasons, and if justifiable it could in that case be the default. In this case (and until the i386 issue is fixed), it would be activated for the x86_64 part, but not for i386. That would at least get rid of the suggestion that asm is used for all architectures. One could keep the +asm variant (which would lead to a pure i386 build), and one might add a +noasm variant (that would disable the asm parts in the x86_64 binaries) if there are usage cases that are incompatible with the asm code. Again, this would only make sense if the asm option is purelyinternal, without introducing changes to the library's ABI... ___ https://trac.macports.org/changeset/117612 +asm variant dropped and --disable-asm asserted whenever configuring for i386. This allows +universal to build with asm optimizations for x86_64 and without for i386. Also fixes -universal build for i386. Other possible archs are handled by the port itself. No ABI impact. Thanks for the suggestion. https://trac.macports.org/changeset/117612 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Vim upgrade lost spelling and syntax highlights
On 04 Mar 2014, at 09:42 , LuKreme krem...@kreme.com wrote: Can't open file /opt/local/share/vim/syntax/syntax.vim Warning: Cannot find word list en.utf-8.spl or “en.ascii.spl” Any ideas? I completely removed vim and reinstalled it port install vim +huge still get the same error. Have pared the vimdc file down to just the following: $ cat .vimrc setlocal spell spelllang=en_us set spellfile=~/.spell.en.add syntax on set ignorecase smartcase set tw=72 set encoding=utf-8 setglobal fileencoding=utf-8 set fileencodings=ucs-bom,utf-8,latin1 set incsearch nnoremap Q gqap noremap Q gq set nocompatible filetype on filetype plugin indent on set guifont=Menlo:h14 hi SpellBad term=reverse ctermbg=124 gui=undercurl guisp=Red set noantialias I can’t uncomment the top three lines without an error, but it worked fine before. -- I have not failed, I've just found 10,000 ways that won't work. - Thomas Edison ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Vim upgrade lost spelling and syntax highlights
On 06 Mar 2014, at 09:37 , LuKreme krem...@kreme.com wrote: I completely removed vim and reinstalled it port install vim +huge OK, that’s odd. After restarting my machine, it’s now working… Erm… That makes no sense, but I am going to just go with it for now. Maybe it was just… no no, never mind, not going to think about it or I’ll spend 15 hours trying to figure out why rebooting would fix this. May— NO! I’m going to take my blue pill and be happy. Thanks all. -- THE DEATH OF A WARRIOR OR THE OLD MAN OR THE LITTLE CHILD, THIS I UNDERSTAND, AND I TAKE AWAY THE PAIN AND END THE SUFFERING. I DO NOT UNDERSTAND THIS DEATH-OF-THE-MIND. --The Light Fantastic ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: [MacPorts] #42672: x264 @20130823_0: universal build failure on Apple clang, i386 issues.
On Mar 06, 2014, at 17:32, MacPorts wrote: Comment: Better solution. +asm variant dropped and --disable-asm asserted whenever configuring for i386. This allows +universal to build with asm optimizations for x86_64 and without for i386. Also fixes -universal build for i386. Other Exactly what I meant, but in clearer wording. R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Tried to upgrade php5 now completely messed up
I tried to do a simple port upgrade php5 since I was very behind and now I cannot get php working again. I uninstalled all php related packages, did a port clean all and now re-installing fails: # port install php5 +apache2 --- Computing dependencies for php5 --- Fetching archive for php5 Warning: Your DNS servers incorrectly claim to know the address of nonexistent h osts. This may cause checksum mismatches for some ports. --- Attempting to fetch php5-5.3.28_0+apache2.darwin_12.x86_64.tbz2 from http: //packages.macports.org/php5 --- Attempting to fetch php5-5.3.28_0+apache2.darwin_12.x86_64.tbz2 from http: //mse.uk.packages.macports.org/sites/packages.macports.org/php5 --- Attempting to fetch php5-5.3.28_0+apache2.darwin_12.x86_64.tbz2 from http://lil.fr.packages.macports.org/php5 --- Fetching distfiles for php5 --- Attempting to fetch php-5.3.28.tar.bz2 from http://jm.php.net/get/php-5.3.28.tar.bz2/from/this/mirror?dummy= --- Verifying checksums for php5 Error: Checksum (rmd160) mismatch for php-5.3.28.tar.bz2 Error: Checksum (sha256) mismatch for php-5.3.28.tar.bz2 *** The non-matching file appears to be HTML. See this page for possible reasons for the checksum mismatch: https://trac.macports.org/wiki/MisbehavingServers *** The file has been moved to: /opt/local/var/macports/distfiles/php5/php-5.3.28.tar.bz2.html Error: org.macports.checksum for port php5 returned: Unable to verify file checksums Please see the log file for port php5 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_php5/php5/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port php5 failed -- Greg Gulik http://www.gulik.com/greg/ greg @ gulik.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Tried to upgrade php5 now completely messed up
On Thu, Mar 6, 2014 at 12:53 PM, Greg Gulik g...@gulik.org wrote: The non-matching file appears to be HTML. See this page for possible reasons for the checksum mismatch: https://trac.macports.org/wiki/MisbehavingServers *** The file has been moved to: /opt/local/var/macports/ distfiles/php5/php-5.3.28.tar.bz2.html So have you visited that webpage and inspected the downloaded file to see why you received HTML instead of a tarfile? -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: list active ports with non-default variants
On Thu, Mar 6, 2014 at 12:48 PM, Bradley Giesbrecht pixi...@macports.org wrote: Does anyone have a command for listing active ports with non-default variants? I'm not aware of any, but I'd love to find there is one. I usually end up dumping a list of installed ports to a file and then removing variants that I know are in my default configuration. Then I go port by port, comparing what's left. I'd love a command like port installed --without-default-variants that would omit variants that are enabled by befault by the port or user configuration. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: list active ports with non-default variants
Don’t forget have that third state: set as default in the variants.conf file but not really a default. How should that be represented here? On Mar 6, 2014, at 13:51, Arno Hautala a...@alum.wpi.edu wrote: I'm not aware of any, but I'd love to find there is one. I usually end up dumping a list of installed ports to a file and then removing variants that I know are in my default configuration. Then I go port by port, comparing what's left. I'd love a command like port installed --without-default-variants that would omit variants that are enabled by befault by the port or user configuration. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: list active ports with non-default variants
Hi, Does anyone have a command for listing active ports with non-default variants? I'm not aware of any, but I'd love to find there is one. I usually end up dumping a list of installed ports to a file and then removing variants that I know are in my default configuration. Then I go port by port, comparing what's left. I'd love a command like port installed --without-default-variants that would omit variants that are enabled by befault by the port or user configuration. We should really extend the requested mechanism to track user-requested variants. That would also give us a clean upgrade path when changing default variants. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Error setting python34 to python
Ticket #41146 (https://trac.macports.org/ticket/41146) says this is fixed, that that has not been my experience today. As you can see from the terminal clips below, I cannot set python34 to python. I am running MacOS 10.9.2. $ sudo port install python34 --- Computing dependencies for python34 --- Fetching archive for python34 --- Attempting to fetch python34-3.4.0rc2_0.darwin_13.x86_64.tbz2 from http://packages.macports.org/python34 --- Attempting to fetch python34-3.4.0rc2_0.darwin_13.x86_64.tbz2.rmd160 from http://packages.macports.org/python34 --- Installing python34 @3.4.0rc2_0 --- Activating python34 @3.4.0rc2_0 To make python 3.4 the default (i.e. the version you get when you run 'python'), please run: sudo port select --set python python34 --- Cleaning python34 --- Updating database of binaries: 100.0% --- Scanning binaries for linking errors: 100.0% --- No broken files found. $ sudo port select --set python python34 Selecting 'python34' for 'python' failed: could not create new link /opt/local/bin/pythonw: target /opt/local/bin/pythonw3.4 doesn't exist $ port -v installed python34 The following ports are currently installed: python34 @3.4.0rc2_0 (active) platform='darwin 13' archs='x86_64' -- Hell hath no limits, nor is circumscrib'd In one self-place; but where we are is hell, And where hell is, there must we ever be --Christopher Marlowe, *Doctor Faustus* (v, 121-24) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Error setting python34 to python
In article ca+bf-zy39rmuepl+mxvsghfekd3-mvgynbtei4c3ouooch7...@mail.gmail.com, Thad Humphries thad.humphr...@gmail.com wrote: Ticket #41146 (https://trac.macports.org/ticket/41146) says this is fixed, that that has not been my experience today. As you can see from the terminal clips below, I cannot set python34 to python. I am running MacOS 10.9.2. $ sudo port install python34 --- Computing dependencies for python34 --- Fetching archive for python34 --- Attempting to fetch python34-3.4.0rc2_0.darwin_13.x86_64.tbz2 from http://packages.macports.org/python34 --- Attempting to fetch python34-3.4.0rc2_0.darwin_13.x86_64.tbz2.rmd160 from http://packages.macports.org/python34 --- Installing python34 @3.4.0rc2_0 --- Activating python34 @3.4.0rc2_0 To make python 3.4 the default (i.e. the version you get when you run 'python'), please run: sudo port select --set python python34 --- Cleaning python34 --- Updating database of binaries: 100.0% --- Scanning binaries for linking errors: 100.0% --- No broken files found. $ sudo port select --set python python34 Selecting 'python34' for 'python' failed: could not create new link /opt/local/bin/pythonw: target /opt/local/bin/pythonw3.4 doesn't exist $ port -v installed python34 The following ports are currently installed: python34 @3.4.0rc2_0 (active) platform='darwin 13' archs='x86_64' The vestigial pythonw symlink synonyms for python have been removed upstream in python3.4. It looks like port select needs to be changed to accommodate that. You should also be careful about setting python to a Python 3 variant. That's not recommended as many Python packages still assume that python refers to a Python 2 variant. port select should provide a python3 name as well and, ideally, for future compatibility, a python2 one as well so that someday python can mean python3, all as recommended in Python PEP 394. http://legacy.python.org/dev/peps/pep-0394/ -- Ned Deily, n...@acm.org ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Tried to upgrade php5 now completely messed up
On Mar 6, 2014, at 9:53 AM, Greg Gulik g...@gulik.org wrote: I tried to do a simple port upgrade php5 since I was very behind and now I cannot get php working again. I uninstalled all php related packages, did a port clean all and now re-installing fails: # port install php5 +apache2 --- Computing dependencies for php5 --- Fetching archive for php5 Warning: Your DNS servers incorrectly claim to know the address of nonexistent h osts. This may cause checksum mismatches for some ports. You might read this: http://trac.macports.org/ticket/39868#comment:9 --- Attempting to fetch php-5.3.28.tar.bz2 from http://jm.php.net/get/php-5.3.28.tar.bz2/from/this/mirror?dummy= You might visit this fetch target in you web browser and check result: http://jm.php.net/get/php-5.3.28.tar.bz2/from/this/mirror?dummy= On my system there is no ip for jm.php.net: $ dig +noall +short +time=2 jm.php.net $ dig +noall +short +time=2 us1.php.net php-mirror.nexcess.net. 208.69.120.58 You can try downloading the php5 distfiles from a different mirror: $ sudo port clean --dist php5 $ sudo curl http://us1.php.net/distributions/php-5.3.28.tar.bz2 -o /opt/local/var/macports/distfiles/php5/php-5.3.28.tar.bz2 $ sudo port -v checksum php5 $ sudo port install php5 Regards, Bradley Giesbrecht (pixilla) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Error setting python34 to python
In article nad-5c4801.14272706032...@news.gmane.org, Ned Deily n...@acm.org wrote: The vestigial pythonw symlink synonyms for python have been removed upstream in python3.4. It looks like port select needs to be changed to accommodate that. I've opened MacPorts ticket #42746 for this ... You should also be careful about setting python to a Python 3 variant. That's not recommended as many Python packages still assume that python refers to a Python 2 variant. port select should provide a python3 name as well and, ideally, for future compatibility, a python2 one as well so that someday python can mean python3, all as recommended in Python PEP 394. ... and #42747 for this. -- Ned Deily, n...@acm.org ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Tried to upgrade php5 now completely messed up
On Mar 6, 2014, at 11:53, Greg Gulik wrote: --- Attempting to fetch php-5.3.28.tar.bz2 from http://jm.php.net/get/php-5.3.28.tar.bz2/from/this/mirror?dummy= --- Verifying checksums for php5 Error: Checksum (rmd160) mismatch for php-5.3.28.tar.bz2 Error: Checksum (sha256) mismatch for php-5.3.28.tar.bz2 *** The non-matching file appears to be HTML. See this page for possible reasons for the checksum mismatch: https://trac.macports.org/wiki/MisbehavingServers *** Thanks for reporting the problem. I updated the php fetch group (including removing the dead jm mirror) in r117645. “sudo port selfupdate” to receive this change. Also, consider moving from the deprecated php5 port to either the php53, php54, or php55 ports. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
