I have installed the latest version of MacTeX-2010, an oft-updated distribution of texlive. However, after my last fink update-all, fink insists that its version of texlive (from 2008) is a requirement. My question is,
What should I do after installing fink's texlive so that my system completely ignores fink's version?
I am using OS.X 10.5.8 with fink 0.29.14.
It's all about paths.
Fink arranges to have /sw/bin in front of /bin and /usr/bin on your $PATH (so that fink tool can override the system tools). You need to arrange to have you 2010 tex installation come ahead of the fink one.
The usual place to do this would be in your .bash_profile (login shells) or .bashrc (non-login interactive shells) .
There may be other paths which need diddling, too.
An alternative would be to work with fink (talk to the current texlive maintainer, take over the texlive maintenance, or start a mactex package) to get a sufficiently up-to-date package.
Related
I've installed a package using brew to a new Mac, imagemagick, and carried over a number of utilities that look for convert, a part of imagemagick in /usr/local/bin. These utilities can't find convert, using which, it's in /opt/homebrew/bin/convert.
In addition, I'm trying to get vscode to work from a command line. It's set up but running code gives the error ./MacOS/Electron: No such file or directory. Electron has been installed using brew but can only be found, again, in /opt/homebrew/bin/convert.
Any thoughts?
Since Homebrew v3.0.0, the default prefix is different depending on the chip architecture. The defaults are the following:
/opt/homebrew on Apple silicon
/usr/local on Intel
The main reason for this change was for Rosetta 2 compatibility.
It appears that you're trying to transition from an Intel machine to an Apple Silicon one. The simplest way to do this might be to reinstall all the formulae again via brew bundle. This shouldn't take very long thanks to the use of pre-built binaries.
Alternatively, you can always manually add /opt/homebrew/bin to your PATH (/usr/local is already in path).
I'd like to install an X11 version of Emacs on Catalina, but haven't found anything online that tells me how I might accomplish this.
The following worked for some previous versions of MacOS, including, I believe Mojave.
$ brew tap d12frosted/homebrew-emacs-plus
$ brew install /emacs-plus --with-x11
Unfortunately, at the moment, if you do this, you get only the "app" version of Emacs, not the X11 version.
The default Emacs recipe that comes with Homebrew does not currently support the "--with-x11" or "--with-x" option.
Is there another Emacs cask somewhere that supports X11?
P.S. I know that I could try to build Emacs directly from the Emacs sources myself, but from past experience, I am afraid that there be dragons along this path.
P.P.S. I seem to have gotten a working version of an X11 emacs installed by rsyncing the directory /usr/local/Cellar/emacs over from a Mac that is running Mojave. But clearly this is less than ideal, so I'm still looking for how I might accomplish this the "right" way.
I maintain my own brew formula for X11 emacs that you may be able to use. I wrote about this in a blog entry here.
This isn't really a programming question -- probably better for serverfault.com or unix.stackexchange.com, but I'll post this reply here anyway.
My last attempts to try to use homebrew to install X11 capable apps, especially Emacs, failed. Once upon a time I had edited the homebrew recipe to make it compile a local version with X11 support, but I was giving up on maintaining that against the quickly moving target of homebrew and the mass migration of homebrew away from supporting X11.
So, really your best option is to build Emacs from source and install it.
(I've moved entirely away from homebrew as a result -- I only use pkgsrc now, and that gives one an easy way to reliably build Emacs with X11 support and manage all the dependencies, etc.)
I want to install the latest version of emacs, but if I do this will it be in conflict with the version that comes pre-packaged with os x? Do I need to delete the native emacs? Also, it seems emacsforosx.com is a popular option, but I lot of people swear by homebrew... why would I go with one option over the other?
There is no reason to remove the system-supplied Emacs; any well-behaved, properly packaged third-party version will install fine alongside, not over, the system binaries and libraries.
Installing a current version of emacs is normal practice because the OSX provided version is outdated. You have a number of options, but I've found using the 'homebrew' method the easiest.
Due to changes in OSX 10.11, you need to take some additional steps when installing homebrew. If you already have homebrew installed, you will probably need to 'fix' the permissions on /usr/local. If you don't have homebrew installed, then there are some additional steps you will need to take to create the /usr/local path. This is documented on the hombrew site at El Capitan and Homebrew
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
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.