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 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
GCC48 GCC47 + FFTW-3
Aloha all, today I upgraded fftw (which is required by ImageMagick) and I discovered that fftw automagically moved to fftw-3, which comes with gcc48 as a dependency (I have all my stuff compiled with gcc47). Now, what should I do? remove gcc48 and fftw-3 and reinstall fftw-3 +gcc47? Py27-SciPy and a bunch of other stuff are configured +gcc47 in my rig. Alternatively I could migrate to gcc48, but I would like to do so *without breaking anything*. If I choose this second option, how do I automatically (1) determine which installed ports require/were build with gcc47 (2) remove the lot and (3) rebuild the stuff removed and cleaned so that the new gcc compiler is gcc48? part (1) seems to be as simples as `port installed |grep gcc47' though this might be deceptive. Parts (2) and (3) look more fraught. All in all moving fttw to fttw-3 (without asking) and getting a new compiler (without asking) seem to be pretty rude. 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: GCC48 GCC47 + FFTW-3
On 29 Aug 2013, at 19:29, Ryan Schmidt ryandes...@macports.org wrote: On Aug 29, 2013, at 13:26, David Strubbe wrote: Let me just comment: I am not sure there is any reason to try to swap everything from gcc47 to gcc48. There are probably only a few cases where there would be some incompatibility (and likely only at build time), and so Federico could just rebuild ports insofar as any problem is found. I assume he objects to needing to have both gcc47 and gcc48 installed. By rebuilding everything with gcc48, he could get rid of gcc47. Correct. I found which ports needed gcc47, rebuilt them with gcc48, removed gcc47 and so far so good. If Julia does not break (my 'gfortran' is a symlink for macports provided gfortran) then all should be well. 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: GCC48 GCC47 + FFTW-3
On 29 Aug 2013, at 19:50, Federico Calboli f.calb...@gmail.com wrote: On 29 Aug 2013, at 19:29, Ryan Schmidt ryandes...@macports.org wrote: On Aug 29, 2013, at 13:26, David Strubbe wrote: Let me just comment: I am not sure there is any reason to try to swap everything from gcc47 to gcc48. There are probably only a few cases where there would be some incompatibility (and likely only at build time), and so Federico could just rebuild ports insofar as any problem is found. I assume he objects to needing to have both gcc47 and gcc48 installed. By rebuilding everything with gcc48, he could get rid of gcc47. Correct. I found which ports needed gcc47, rebuilt them with gcc48, removed gcc47 and so far so good. If Julia does not break (my 'gfortran' is a symlink for macports provided gfortran) then all should be well. I can confirm that using macports GCC to have gfortran did hose Julia when I moved from gcc 47 to 48. Serves me right I suppose BW F BW F -- Federico Calboli f.calb...@gmail.com -- 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
port info problem
Dear All, I was checking (out of academic curiosity) the port for R. :~$ port info R R @2.15.3 (math, science) Variants: aqua, debug, gcc43, gcc44, gcc45, gcc46, [+]gcc47, [+]recommended Description: R is a language and environment for statistical computing and graphics. R provides a wide variety of statistical (linear and nonlinear modeling, classical statistical tests, time-series analysis, classification, clustering, ...) and graphical techniques, and is highly extensible. Homepage: http://www.r-project.org/ Build Dependencies: pkgconfig Library Dependencies: gettext, icu, glib2, jpeg, libiconv, cairo, pango, readline, tcl, tk, tiff, xorg-libXmu, xorg-libXScrnSaver, gcc47 Conflicts with: R-framework Platforms:darwin License: GPL-2 GPL-3 Maintainers: kjell.ko...@me.com I was curious to know more about R-framework, due to the conflict with R, so I tried :~$ port info R-framework Error: Inconsistent variant specification: R-framework variant +x11 is required by at least one of +cairo +accelerate +gcc47 +recommended, but specified -x11 Error: Unable to open port: Error evaluating variants WTF? I might not be interested installing a port (in fact I do not install R through macports in the first place), but why can't I get info about it if I want? The fact I do not want macports to install x11 has nothing to do with my ability to read info about a port. Bizarre. BW F ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: port info problem
On 9 Apr 2013, at 12:02, Aljaž Srebrnič g...@macports.org wrote: Hello! well, that is because in your variants.conf you have disabled x11 (-x11), but the default variants of R-framework specifies +cairo, which requires +x11. I know what variants I have disabled, and I do not want to change them. All I am trying to do is to get some info about a port, and I am gobsmacked my ability to get info about a port is tied to my variants choices. So, the way to solve this is: - Enable cairo only if +x11 is requested - Remove cairo from default_variants either of the options are to be implemented by the maintainer. You should open a ticket at http://trac.macports.org and Cc the maintainer. In the meantime, you can check out the port information by entering: $ port info R-framework -cairo Thanks, that kind of does it, but port info should be variant independent -- it's just damn info after all! BW F On 09/apr/2013, at 12:08, Federico Calboli f.calb...@gmail.com wrote: Dear All, I was checking (out of academic curiosity) the port for R. :~$ port info R R @2.15.3 (math, science) Variants: aqua, debug, gcc43, gcc44, gcc45, gcc46, [+]gcc47, [+]recommended Description: R is a language and environment for statistical computing and graphics. R provides a wide variety of statistical (linear and nonlinear modeling, classical statistical tests, time-series analysis, classification, clustering, ...) and graphical techniques, and is highly extensible. Homepage: http://www.r-project.org/ Build Dependencies: pkgconfig Library Dependencies: gettext, icu, glib2, jpeg, libiconv, cairo, pango, readline, tcl, tk, tiff, xorg-libXmu, xorg-libXScrnSaver, gcc47 Conflicts with: R-framework Platforms:darwin License: GPL-2 GPL-3 Maintainers: kjell.ko...@me.com I was curious to know more about R-framework, due to the conflict with R, so I tried :~$ port info R-framework Error: Inconsistent variant specification: R-framework variant +x11 is required by at least one of +cairo +accelerate +gcc47 +recommended, but specified -x11 Error: Unable to open port: Error evaluating variants WTF? I might not be interested installing a port (in fact I do not install R through macports in the first place), but why can't I get info about it if I want? The fact I do not want macports to install x11 has nothing to do with my ability to read info about a port. Bizarre. BW F ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users -- Aljaž Srebrnič a.k.a g5pw My public key: http://bit.ly/g5pw_pubkey ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: macports without XCode
On 8 Nov 2012, at 18:29, William H. Magill mag...@icloud.com wrote: On Nov 07, 2012, at 08:47 AM, Federico Calboli f.calb...@gmail.com wrote: After having a go with homebrew I decided that macport's use of /opt/local is significantly less likely to screw up my system, so I am now quite firmly on the macport side of the camp. One good thing homebrew has though is the fact it only requires the command line tools, not the whole Xcode installation. Is a macports -Xcode +CLT ever going to happen? I do not believe it is possible to acquire/install the Command Line Tools (CLT) WITHOUT first installing Xcode. It is, people using homebrew (and not just them) do it all the time. BW F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
macports without XCode
After having a go with homebrew I decided that macport's use of /opt/local is significantly less likely to screw up my system, so I am now quite firmly on the macport side of the camp. One good thing homebrew has though is the fact it only requires the command line tools, not the whole Xcode installation. Is a macports -Xcode +CLT ever going to happen? BW F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: macports without XCode
On 7 Nov 2012, at 13:49, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: After having a go with homebrew I decided that macport's use of /opt/local is significantly less likely to screw up my system, so I am now quite firmly on the macport side of the camp. One good thing homebrew has though is the fact it only requires the command line tools, not the whole Xcode installation. Is a macports -Xcode +CLT ever going to happen? Some packages provided by MacPorts are actually xcode projects; you can't them without xcode installed. Which packages if I can ask? because they might be packages that I do not want nor need. Some packages also build differently based on the version of xcode installed; you also can't install them without xcode present. How so? I would have imagined it's the CLT that make the difference, after all they mast be installed for macports. BW F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: macports without XCode
On 7 Nov 2012, at 14:06, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: Which packages if I can ask? because they might be packages that I do not want nor need. I grepped to find 148 packages using our xcode includes explicitly (xcode.*1\.0). There may be more that were manually built without using our PortGroup files. Unless these packages are essential to using macports, and thus unavoidable, 148 packages are a trivial percentage of the packages provided by macports. Couldn't I just avoid them altogether? How so? I would have imagined it's the CLT that make the difference, after all they mast be installed for macports. ...and Xcode must also be installed. We do version detection using `xcodebuild -version` (see zlib for an example). We would need an alternative to this if it's not installed. That's fine, and as I said I accept the space penalty of having to have Xcode, but I fail to see why the versioning could not be done on clang or llvm (or whatever thing is in the CLT package that could be used for this) BW F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
gcc 4.7.x and apple driver-driver
Does gcc 4.7 (or any other MP gcc) come with Apple driver-driver (http://opensource.apple.com/source/gcc/gcc-5488/driverdriver.c)? If not, is there a way of geeting such lump of utter goodness in the gcc of choice? Incidentally, if the driver driver is not in the MP gccs, why not? BW F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
+no_x11 as default
Is it there a way of making the option +no_x11 (where available, obviously), the default? I hate when macports tries to install X11 -- I can do it myself from http://xquartz.macosforge.org/landing/, thankyouverymuch. F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: +no_x11 as default
On 9 Aug 2012, at 15:25, Brandon Allbery allber...@gmail.com wrote: On Thu, Aug 9, 2012 at 10:18 AM, Federico Calboli f.calb...@gmail.com wrote: Is it there a way of making the option +no_x11 (where available, obviously), the default? I hate when macports tries to install X11 -- I can do Yes and no. No because +no_x11 is deprecated and being removed from the ports that still have it; Ok, so what happens when ghostscript, ImageMagick, libsdl etc switch option? I ask because: ~$ port installed|grep x11 ghostscript @9.05_2+no_x11 (active) ImageMagick @6.7.8-3_0+no_x11+q16 (active) libsdl @1.2.15_0+no_x11 (active) will the +no_x11 be automagically transformed in -x11? use -x11 +quartz instead, or you're likely to continue to get X11 anyway. just to check: +quartz is meant to indicate I installed XQuartz myself and that macports will not try to install any X related packages? I damn well want to avoid macports switching to XQuartz based bloat. cheers F /opt/local/etc/macports/variants.conf is where you put the variants you want to enable/disable by default. -- brandon s allbery allber...@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
binaries list
Hi All, is there a list of which ports are available as a binary (for Lion)? I noticed that, on upgrade, a number of ports are installed from binaries rather than being compiled on my machine. For small ports this is nice but quite unimportant, but for stuff like the GCC ports it would be nice to know if I'm going to get some serious compilation time in front of me. BW F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: binaries list
On 3 Jul 2012, at 15:45, Jeremy Lavergne wrote: is there a list of which ports are available as a binary (for Lion)? I noticed that, on upgrade, a number of ports are installed from binaries rather than being compiled on my machine. For small ports this is nice but quite unimportant, but for stuff like the GCC ports it would be nice to know if I'm going to get some serious compilation time in front of me. Be worry-free, just have MacPorts run in binary-only mode: sudo port -b install x y z yes, but that would only work if a binary is available! BW F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
on XCode 4.3 and no problems to report
Well, despite the reports, I moved to xcode 4.3, installed the CLI bundle, changed Xcode-select and the macports.conf developer-dir line and all works. I just keep a minimal macports collection though. F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port selfupdate incredibly slow
If you're upgrading from MacPorts 1.x to MacPorts 2.x, then all existing installed ports must be converted. This can take hours depending on how many ports you have installed, but again should be bound by disk speed and not be CPU intensive I should have mentioned, when I installed Lion I had to install MP 2.0.1 from the disk image, so all I see now is post fresh install of MP 2.0.1 from disk image. Bw F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port selfupdate incredibly slow
On 17 Aug 2011, at 11:19, Ryan Schmidt wrote: Correct, MacPorts 1.x was not compatible with Lion, if that's what you mean. so all I see now is post fresh install of MP 2.0.1 from disk image. FYI, installing a MacPorts disk image over an existing MacPorts install would not uninstall any ports you had already installed. As I wiped my disk and installed Lion from a bootable USB key I made with my copy of Lion (I did this to maximise performance), I had nothing in the way of MacPorts All I am saying is, on the same machine the selfupdate step was much faster in SL. I would not know wy that is, but it is a very noticeable difference. Bw F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port selfupdate incredibly slow
On 17 Aug 2011, at 11:25, Ryan Schmidt wrote: As I wiped my disk and installed Lion from a bootable USB key I made with my copy of Lion (I did this to maximise performance), I had nothing in the way of MacPorts Ok. All I am saying is, on the same machine the selfupdate step was much faster in SL. I would not know wy that is, but it is a very noticeable difference. What is selfupdate doing when it is slow? If you run verbosely (sudo port -v selfupdate), does it pause or slow down at a particular point? It pauses for 30 seconds after sent 64 bytes received 636 bytes 280.00 bytes/sec total size is 512 speedup is 0.73 As I said, in SL this delay at this stage was of a 5 seconds at most. Bw F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
port selfupdate incredibly slow
Hi All, I'd like to ask, is it just for me that sudo port -v selfupdate is very slow and CPU intensive? My mac details: 2.2 GHz Intel Core i7, 8GB RAM, OS 10.7 (Lion), installed from scratch -- I made a bootable USB image and wiped my HD. Cheers, F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
