I've been working with Haskell lately, and installed gtk2hs (a gtk library for Haskell) a few days ago using MacPorts. For some reason, MacPorts saw fit to install GHC 6.10 over my previous GHC 6.12 install, but I didn't really care.
Now I find myself desiring the improved parallelism support of the latest Haskell Platform, so I installed it today, and it installed successfully - except that when I type in "ghc -v" in Terminal, I am informed that I have GHC 6.10 still.
I have tried using uninstall-hs, and it informs me that I have three Haskells on my system: versions 6.12, 6.12.3, and 7.04. I'm not sure how that 6.12.3 showed up, and what happened to the 6.10? Most importantly, how can I start running version 7.04? Thanks in advance for your help!
You should completely purge your MacPorts install of GHC and your current Platform installation and install the Haskell Platform directly with the OS X installer. After that, future versions of the Haskell Platform can be upgraded to cleanly simply by installing them.
The following command should remove your MacPorts GHC:
$ sudo port uninstall --follow-dependents ghc
You might want to execute something like find /usr /opt/local -name '*ghc*' after uninstalling everything to check that there's no remaining traces.
To really clear out the old install, you've got to go in and delete things by hand.
This will be very useful: Everywhere that GHC/Haskell Platform installs
Might want to look here also: http://www.vex.net/~trebla/haskell/sicp.xhtml
Related
Hi I'm trying to install IRAF with anaconda I follow these steps, but when I run iras, and I want to make something, this program doesn't recognize the commands of IRAF
i follow this tutorial: https://astroconda.readthedocs.io/en/latest/installation.html
I don't know how to fix it.
The Astroconda IRAF is a 32-bit version and does not work on M1 Macs, since they are not able to run 32-bit code.
To install IRAF for an M1 Mac, you should compile it manually, as described in https://iraf-community.github.io/install. This installs the latest 64-bit IRAF version. PyRAF (for Python 3) can then simply installed with pip3, see https://iraf-community.github.io/pyraf.html.
However, it is not recommended to start with IRAF unless there is a real need for it. IRAF is old software with an uncertain future and no institutional support. The Astropy Python package and its ecosystem provide good alternatives for many tasks of IRAF. https://astropy.org
In the end, created an env to install graph-tool thru the channel vgauthier.
Thinking by now that I might have as well used earlier version of python or installed a whole new python latest version just for this.
But as it is all part of the learning process to creating dev. env.. (at the same time worrying my Mac has too many installations with much too interlinked dependencies)
Someone kindly let me know if this rings any bell or got any suggestion:
Incompatible library version states that _cairo.cpython-36m-darwin.so requires later version of libcairo.2.dylib.
Errors could have been from:
having on .condarc file, wrong priorities btw channels, so having trouble finding the right files
(modified to the order of conda-forge > ~dir/vgauthier > default
my having given up on installing pygobject after googling it is not supported on Mac OS (which was apparently wrong or I just wasnt searching well)
Solution to easy setup of graph-tool for conda-installed python users:
Get the benefit of GUI (seriously a god option) ->
https://medium.com/#ronie/installing-graph-tool-for-python-3-on-anaconda-3f76d9004979
To still continue with command line (still get the idea from GUI)
conda install -c pkgw-forge gtk3
conda install -c https://conda.anaconda.org/fallen pygobject
(if there are cairo blah blah missing, look up setup directions for igraph which has more information and help, having been an older library)
Do these before installing graph-tool, which Im still wondering why I cannot remove from the system though. ;)
For others, https://git.skewed.de/count0/graph-tool/wikis/installation-instructions#compiler-choice-in-macos-x
Ok, I know how to install Perl modules with cpan and have been doing it for years. But when I try to install the DateTime module on this particular mac, it fails, claiming that it cannot find a compiler.
Here is some of the output from attempting to install one of the prerequisites, Params::Validate: ( I get the same kinds of errors from attempting to install the module in question.)
Configuring Params-Validate-1.00
Running Build.PL
/usr/libexec/gcc/powerpc-apple-darwin10/4.2.1/as: assembler (/usr/bin/../libexec/gcc/darwin/ppc/as or /usr/bin/../local/libexec/gcc/darwin/ppc/as) for architecture ppc not installed
Installed assemblers are:
/usr/bin/../libexec/gcc/darwin/x86_64/as for architecture x86_64
/usr/bin/../libexec/gcc/darwin/i386/as for architecture i386
lipo: can't open input file: /var/tmp//cc3Aefez.out (No such file or directory)
Warning: ExtUtils::CBuilder not installed or no compiler detected
Proceeding with configuration, but compilation may fail during Build
Why is Build.PL looking for a ppc compiler? If that is the problem where do I tell it (or cpan, or cpanm) that this machine is not a ppc box?
I'm running 10.6.8. The version of perl is v5.10.0 built for darwin-thread-multi-2level
I most definitely have the Developer tools installed.
I'm running cpan and cpanm via sudo.
I'd be grateful for any assistance anyone can offer.
known problem with Xcode on Lion, Apple couldn't help messing around with nm, breaking Perl again (previously) and who knows what else
p5p discussion
perlbrew's info
You are on an unsupported Perl. Upgrade to stable.
I've got 10.7 installed which comes with Perl 5.12.3 installed. I did a CPAN install:
$ sudo cpan
password:
cpan> install DateTime
And, the whole thing works. Is this something you need for a third party file, or do you want to use this because you're familiar with this particular package?
There are several built in Time packages with Perl 5.10. Would one of these work for you? Otherwise, you might need to install ExtUtils::CBuilder and see if that helps.
Or, install a more modern version of Perl such as ActiveState which is pretty simple to install, its cpan utility works pretty good on a Mac, and it's version 5.14 which is even newer than the version that comes with Lion.
I think what's happening is that the installer is trying to compile something (possibly an XS module) and to do that it needs to use the same compiler that was used to compile whichever version of Perl is on your system, and it can't find it.
Your best bet would be to install your own version of Perl 5.10 using perlbrew as this gaurantees the compiler is available (make sure you edit your .profile so Terminal uses your new Perl), then re-open Terminal, switch to the perlbrew version of Perl 5.10 and you should be fine from then on.
If you have problems installing the perlbrew Perl then as daxim noted above refer to the Lion fix
I want the latest version of openmpi. I like to use macports because it is easy to install, uninstall, and upgrade software. I have installed the latest mpi via building from source, but no one seems to be able to get it to build properly with macports. There is always a build error. There are tickets (and you can see the logs at ), but they seem to be collecting dust and it seems strange that no one had found a solution.
I have tried uninstalling the built in version (I know, openmpi says not to do that--but it works fine if I reinstall it--even in a different directory), but I still the same build errors. I also tried with different gcc.
Does anyone know what is so difficult about getting openmpi via macports?
sudo port install openmpi
worked for me
I've installed Snow Leopard over Leopard with macports and rubygems already installed. This was regular install, not a clean "archive and erase" install.
It turned out, that SL has 64bit versions of shared libraries and many development utilities do not work. For example, "port" command complains on incompatible tcl library, or ruby cannot load 32bit bundles.
What is the easiest way to solve these issues?
I was googling for the answer for about 4 days already and finally came up with a step-by-step manual on fixing macports and rubygems:
http://oleganza.tumblr.com/post/127709563/snow-leopard-with-legacy-macports-and-rubygems
In short: for proper use of macports and rubygems you would have to:
Install trunk macports from source (or use 1.8 version when it is released)
Add alias for "gem install with 64bit architecture"
Reinstall all ports (not automated yet)
Reinstall all gems (100% automated)
This would take 10-20 minutes of your personal time and another 20
minutes of machine time in order to build and install stuff.
I would be glad to get more answers in order to fix other issues we might meet later.
Since it's really hard to force MacPorts to recompile all ports (in the proper order), I just did:
mv /opt /opt.old
Then install MacPorts 1.8, and bring back any configs you need from /opt.old/local/etc/
Otherwise, you'll get assorted errors complaining about your existing libs' architecture, (e.g. "Command output: ld: warning: in /opt/local/lib/libz.dylib, file is not of required architecture").
This isn't as clean as 'port uninstall installed' but works fast and good enough for me.
Richard Dooling's MacPorts On Snow Leopard explains that to fix the older install of MacPorts, which is broken after the upgrade to Snow Leopard, you should just download and install the new compatible version over the old one and then simply follow the migration instructions - which also say the same.