I just installed MacPorts and issued the command:
sudo port install automake
Throughout the process I see this message:
Warning: Deactivate forced. Proceeding despite dependencies.
What does it mean? Why did it happen? Is it critical and, if so, should I do anything about it?
Thanks,
gb
Based upon my own experience this is not critical and you should in most cases don't have to do anything about it. It is only a warning.
This warning is shown when an old version of a software package 'A' is uninstalled and replaced by a newer version, while another previously installed software package 'B' depends on it.
This package 'B' was built with the old version of package 'A' in mind, and might break if the newer version isn't compatible. However, for most updates this is not a problem.
(After upgrading packages you will notice that macports scans your files for linking errors, which, I believe, should detect this kind of problems and automatically fix them.)
Related
I recently upgraded Octave to v.7.1.0 and am having trouble installing various packages, such as signal and tablicious. I can't tell if it is due to a compatibility issue or if I'm doing something else wrong. How can one tell if a package is compatible with the Octave version?
When i try to install signal, I get
error: the following dependencies were unsatisfied:
signal needs control >= 2.4
Then, when I try to install control, it gives a ton of warnings mostly indicating this warning:
warning: load path C:\Users\myname\AppData\Roaming\octave\api-v57\packages\signal-1.4.1: No such file or directory`
Again, not sure if it is something I'm doing wrong or if the packages are incompatible with this version of Octave. I can't decipher the errors/warnings.
Thank you.
When using IHaskell via JupyterLab, there seems to be only partial support for new-style cabal projects.
When creating a workbook in a cabal project's directory, IHaskell picks up the .ghc.environment file. So the kernel sees exactly the same package versions as used by cabal. Nice!
However, some other things work less smoothly:
Module paths: modules from the same cabal package cannot be imported, presumably because IHaskell doesn't know where cabal keeps compiled module files.
Language extensions: My cabal file has ViewPatterns under language-extensions which is not automatically enabled in the IHaskell session.
Although there is only one ihaskell package installed, this message appears on the JupyterLab console:
Disabling IHaskell widget support due to an encountered error:
The installed IHaskell support libraries do not match the instance of IHaskell you are running.
This *may* cause problems with functioning of widgets or rich media displays.
This is most often caused by multiple copies of IHaskell being installed simultaneously in your environment.
To resolve this issue, clear out your environment and reinstall IHaskell.
If you are installing support libraries, make sure you only do so once:
# Run this without first running `stack install ihaskell`
stack install ihaskell-diagrams
If you continue to have problems, please file an issue on Github.
Are there any known workarounds for these problems?
I've been installing "hamlib 1.2.15.3" (sourceforge) on my RaspberryPi under Raspbian and everything
worked great for a while.
When I noticed an unimplemented feature, I downloaded the newest developer version here:
here (something like this, but this link may change every day: http://n0nb.users.sourceforge.net/hamlib-3.0~git-6e44327-20140321.tar.gz)
So I downloaded it and did the usual: untar to a folder, ./configure, make, make install.
After all was done, I launched rotctl and there comes this message: rotctl: symbol lookup error: /usr/local/lib/libhamlib.so.2: undefined symbol: g313_caps
I thought the package wasn't flawless and I tried to install the old version again. But it's still like that. Also I tried ldconfig every now and then.
To be honest: I'm a beginner when it comes to linux, so I don't know what I have done there. Maybe I was doing a major mistake, a normal linux user wouldn't do. Maybe it was wrong to install that package without uninstalling the older version. Also I don't even know how to do that.
Basically there is only one file in the source code, I need to change to the newer version. So, if there is anyone who could tell me, how to make a clean uninstall, I could replace only this file in the source and install again. I think that would do the thing.
Or shall I rather ask the people from the hamlib developer team?
Thank you in advance.
I’ve just installed the Haskell Platform on my Mac running Mavericks 10.9. The cabal version included (1.16) is out of date, and prompts me to run “cabal update” and then “cabal install cabal-install". Doing so installs cabal 1.20.0.3, but it installs in ~/Library/Haskell. This is not in my executable path, so further attempts to run cabal result in executing version 1.16 from /usr/bin, which was not updated.
I guess I could get around this by changing my executable path to include ~/Library/Haskell, with higher preference than /usr/bin. But I don’t really want to do this. And I don’t want to maintain multiple out of date versions of the software in hidden locations on my system. How do I get cabal to update the executable in the right place? Running with sudo did not help.
Edit: Updated my path, but somehow it still doesn’t work:
[76 of 76] Compiling Main ( Main.hs, dist/build/cabal/cabal-tmp/Main.o )
Linking dist/build/cabal/cabal ...
Warning: No documentation was generated as this package does not contain a library. Perhaps you want to use the --executables flag.
Installing executable(s) in
/Users/lethe/Library/Haskell/ghc-7.6.3/lib/cabal-install-1.20.0.3/bin
Installed cabal-install-1.20.0.3
Updating documentation index /Users/lethe/Library/Haskell/doc/index.html
euclid:Public lethe$ which cabal
/Users/lethe/Library/Haskell/bin/cabal
euclid:Public lethe$ cabal --version
cabal-install version 1.16.0.2
using version 1.16.0 of the Cabal library
euclid:Public lethe$ echo $PATH
/Users/lethe/Library/Haskell/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/usr/local/git/bin:/usr/texbin
It claims it installed cabal 1.20.0.3 to ~/Library/Haskell, and since the path is updated, it claims it’s going to execute the version in ~/Library/Haskell, but it also claims the executed version is 1.16.0.2. What’s going on here?
I also tried ghc-pkg recache and cabal install cabal-install-1.20.0.3 (with version number specified), but executed version is still 1.16.0.2
There are a couple of solutions:
1) Try updating the PATH variable such that it looks in your local path first.
(Add this to your .bash_profile: export PATH=$HOME/Library/Haskell/bin:$PATH. Source the profile and then retry the whereis command to identify which binary you are using, it should use your local one)
Though this didn't work for me. I had to resort to the next step to make it work:
2) Brute force fix: Delete /usr/bin/cabal.
Hope this helps.
According to 23skiddo at GitHub, the way to get cabal to install in the system-wide directory is cabal install --global. Also if your shell is executing the wrong path to an executable you probably need to clear the cache with hash -d cabal or hash -r.
I once had an alias to a command and forgot about it. That is not picked up by "which ".
Try $(which cabal) --version. If it shows 1.20 there may be some similar problem. Use compgen -a to list your aliases.
/Users/lethe/Library/Haskell/ghc-7.6.3/lib/cabal-install-1.20.0.3/bin also is not /Users/lethe/Library/Haskell/bin.
Also:
There is a new Haskell-Plattform release 2014.2 now. This comes with Cabal 1.18 and GHC 7.8.3.
It updates easily to Cabal 1.20 (I don't know why it does not come with 1.20 in the first place).
I already tried many different setups between using Haskell-Plattform, Homebrew ghc + haskell-plattform and also http://ghcformacosx.github.io/
Last one makes most sense to me after trying all different ways to use Haskell on OSX.
If you switch between different "distributions" make sure you really get rid of "everything" that is installed from other versions of Haskell.
I think the most important thing is to recognize that all of those installations are more or less the same. It just moves paths and preferences around.
I wanted to install wine through macports. I followed instructions on following site: http://www.easypctutorials.com/how-to-install-wine-on-mac-os-x
Now when I try the sudo install command for anything, terminal first returns this:
Warning: /opt/local/etc/macports/variants.conf specifies invalid variant syntax '“+universal”', ignored.
and then it always fails to install the software.
Now, I want to know how to remove +universal or what could be done to install wine or anything else otherwise. Even MacPorts doesn't get updated citing the same thing. Even if I search for ports, it says the same thing.
Just remove the line containing +universal from variants.conf (or clear out variants.conf completely) and skip this step of the how-to. It is no longer needed, MacPorts will automatically ensure the dependencies are available in the correct architecture when you attempt to install wine.