getting rid of py27-nose @1.2.1_1 and gmp @5.0.5_0
Hi All, if I do 'port installed' I get two ports, py27-nose @1.2.1_1 and gmp @5.0.5_0, that are not active -- they have been superseded by py27-nose @1.3.0_0 and gmp @5.1.2_0 -- but are there. Please note I always 'port -u upgrade', so I am at loss why they should be there in the first place. I have thus far failed to get rid of them, and get rid of any leftover crud left by their configuration. I'd be obliged if someone could tell how to do that -- I like to run a tight ship. BW F -- Federico Calboli f.calb...@gmail.com signature.asc Description: Message signed with OpenPGP using GPGMail ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: getting rid of py27-nose @1.2.1_1 and gmp @5.0.5_0
On Dec 10, 2013, at 4:44, Federico Calboli wrote: if I do 'port installed' I get two ports, py27-nose @1.2.1_1 and gmp @5.0.5_0, that are not active -- they have been superseded by py27-nose @1.3.0_0 and gmp @5.1.2_0 -- but are there. Please note I always 'port -u upgrade', so I am at loss why they should be there in the first place. Perhaps one day gmp was outdated but instead of running sudo port upgrade outdated you instead ran sudo port install x where x is a port that depends on gmp; MacPorts would have upgraded gmp first, without knowing that you prefer to uninstall the old version. Same for py27-nose, possibly in a different instance. I have thus far failed to get rid of them, and get rid of any leftover crud left by their configuration. I'd be obliged if someone could tell how to do that -- I like to run a tight ship. You can uninstall them this way: sudo port uninstall gmp @5.0.5_0 py27-nose @1.2.1_1 Or if you want to get rid of all inactive ports you can use: sudo port uninstall inactive ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: getting rid of py27-nose @1.2.1_1 and gmp @5.0.5_0
On 10 Dec 2013, at 11:28, Ryan Schmidt ryandes...@macports.org wrote: I have thus far failed to get rid of them, and get rid of any leftover crud left by their configuration. I'd be obliged if someone could tell how to do that -- I like to run a tight ship. You can uninstall them this way: sudo port uninstall gmp @5.0.5_0 py27-nose @1.2.1_1 Or if you want to get rid of all inactive ports you can use: sudo port uninstall inactive That worked, and seems reasonably obvious -- enough at least to make me feel quite stupid for not having figured it out myself. BW F -- Federico Calboli f.calb...@gmail.com signature.asc Description: Message signed with OpenPGP using GPGMail ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: getting rid of py27-nose @1.2.1_1 and gmp @5.0.5_0
On Dec 10, 2013, at 05:40, Federico Calboli f.calb...@gmail.com wrote: On 10 Dec 2013, at 11:28, Ryan Schmidt ryandes...@macports.org wrote: I have thus far failed to get rid of them, and get rid of any leftover crud left by their configuration. I'd be obliged if someone could tell how to do that -- I like to run a tight ship. You can uninstall them this way: sudo port uninstall gmp @5.0.5_0 py27-nose @1.2.1_1 Or if you want to get rid of all inactive ports you can use: sudo port uninstall inactive That worked, and seems reasonably obvious -- enough at least to make me feel quite stupid for not having figured it out myself. Don’t worry; we have too many different sources of documentation and it’s hard to keep up with them all. “inactive” is what we call a pseudo-portname, which evaluates to a set of ports that can vary based on your installation. Other pseudo-portnames that do what they sound like include “all”, “active”, “installed”, “outdated”, “requested”, and “unrequested”. Pseudo-portnames are documented in the port(1) manpage. You can use these pseudo-portnames with any MacPorts commands where you would use actual port names, though some pseudo-portnames fit better with some commands than others. For example it’s unlikely you’d want to install all 17,000+ ports with “sudo port install all”, however you might want to clean all ports with “sudo port clean all”. Using the “installed” pseudo-portname with the “installed” command (“port installed installed”) is redundant, but using the “actinact” pseudo-portname with it (“port installed actinact”) can be informative (shows you ports you’ve installed that have both an active and at least one inactive version). Another interesting pseudo-portname is “leaves”, which is the set of ports that were both not requested by you and are not needed by any other port; these are often good candidates for uninstalling (with “sudo port uninstall leaves”). Note two caveats: * Leaves include build dependencies. So even if a port is not required to run a port, it may be required to build it, so next time you upgrade a port it may need to reinstall such build dependencies. * Programs or libraries installed by some ports may inadvertently link to libraries they shouldn’t. This would be a bug, but MacPorts is not free of bugs. It is possible that a program you use has inadvertently linked with a library that is a leaf; uninstalling that leaf would cause the program to fail because it cannot find the library. If you encounter this situation, please file a bug report so that we can decide how to fix it: either by adding a dependency on the opportunistically-linked library, or by forcing the program not to use the library. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
where put font forge docs?
I’ve installed the port fontforge @20120731_2. Now I want the Help to call local help files. Following instructions at http://fontforge.org/source-build.html#Documentation, I put the downloaded, unarchived documentation at /usr/local/share/doc/fontforge. But still, after starting fontforge from Terminal and using either the Fn F1 key or the Help Help menu item in fontforge, I get the on-line documentation from fontforge.org instead. How fix? --- Murray Eisenbergmurrayeisenb...@gmail.com 503 King Farm Blvd #101 Home (240)-246-7240 Rockville, MD 20850-6667Mobile (413)-427-5334 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: where put font forge docs?
On Tue, Dec 10, 2013 at 12:25 PM, Murray Eisenberg murrayeisenb...@gmail.com wrote: I’ve installed the port fontforge @20120731_2. Now I want the Help to call local help files. Following instructions at http://fontforge.org/source-build.html#Documentation, I put the downloaded, unarchived documentation at /usr/local/share/doc/fontforge. But still, after starting fontforge from Terminal and using either the Fn F1 key or the Help Help menu item in fontforge, I get the on-line documentation from fontforge.org instead. MacPorts uses /opt/local instead of /usr/local, so try /opt/local/share/doc/fontforge. -- 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: where put font forge docs?
I suspected it would be somewhere in /opt/local. Thanks! Looking further, I see in the fontforge app’s File Preferences menu item window an entry for HelpDir that’s set to default, in fact, to: /opt/local/share/fontforge/doc/fontforge So that’s where I unarchived the docs, and now I do get the locally-installed files. Evidently /opt/local/share/doc/fontforge would work, too, provided one changes the HelpDir preference. I guess it’s “tidy” to keep the docs within /opt/local/share/fontforge, but what will happen on a version upgrade? will they be left unaffected (I would presume)? On Dec 10, 2013, at 12:42 PM, Brandon Allbery allber...@gmail.com wrote: On Tue, Dec 10, 2013 at 12:25 PM, Murray Eisenberg murrayeisenb...@gmail.com wrote: I’ve installed the port fontforge @20120731_2. Now I want the Help to call local help files. Following instructions at http://fontforge.org/source-build.html#Documentation, I put the downloaded, unarchived documentation at /usr/local/share/doc/fontforge. But still, after starting fontforge from Terminal and using either the Fn F1 key or the Help Help menu item in fontforge, I get the on-line documentation from fontforge.org instead. MacPorts uses /opt/local instead of /usr/local, so try /opt/local/share/doc/fontforge. --- Murray Eisenbergmurrayeisenb...@gmail.com 503 King Farm Blvd #101 Home (240)-246-7240 Rockville, MD 20850-6667Mobile (413)-427-5334 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: where put font forge docs?
On Dec 10, 2013, at 11:47, Murray Eisenberg wrote: I guess it’s “tidy” to keep the docs within /opt/local/share/fontforge, but what will happen on a version upgrade? will they be left unaffected (I would presume)? MacPorts will not touch files it did not put there, so they should remain unaffected. However, it seems messy for you to have to install the documentation manually. We should create a port to install it for you. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: where put font forge docs?
On Dec 10, 2013, at 2:06 PM, Ryan Schmidt ryandes...@macports.org wrote: On Dec 10, 2013, at 11:47, Murray Eisenberg wrote: I guess it’s “tidy” to keep the docs within /opt/local/share/fontforge, but what will happen on a version upgrade? will they be left unaffected (I would presume)? MacPorts will not touch files it did not put there, so they should remain unaffected. However, it seems messy for you to have to install the documentation manually. We should create a port to install it for you. Even better! --- Murray Eisenbergmurrayeisenb...@gmail.com 503 King Farm Blvd #101 Home (240)-246-7240 Rockville, MD 20850-6667Mobile (413)-427-5334 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
c compile error on implicit declaration
Hi all I am trying to compile the c code and got the following error. cc -DIWORDSIZE=4 -DMAX_HISTORY=25 -DNMM_CORE=0 -c -g registry.c registry.c:60:3: warning: implicit declaration of function 'sym_forget' is invalid in C99 [-Wimplicit-function-declaration] sym_forget() ; ^ Do anybody have any ideas on it? Thank you Bruce ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Undefined symbols for architecture x86_64 error on fortran compiling
Hi all When I compile a fortran code, I got the error Undefined symbols for architecture x86_64 My mac is 64bits. The fortran compiler used here is ifort. Thank you Bruce___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
