I asked this on Haskell-cafe, and the only answer I got was -- try stackoverflow, it is more closely watched.
When I try to install the latest Haskell Platform, the installation always fails.
I've tried this several times over several days. Here is todays situation:
Package downloaded from Haskell Wiki: http://lambda.galois.com/hp-tmp/2011.2.0.1/Haskell%20Platform%202011.2.0.1-i386.pkg, http://hackage.haskell.org/platform/mac.html
My system: OS X 10.6.8 (was 10.6.7 the first time I had this problem), 2.4 GHz Intel Core 2 Duo. According to df -H I have 221G of free disk.
I have Xcode 3.2.5.
After downloading, I go through the installation steps, and right at the end it says "Installation failed, contact the software developer" or words to that effect.
Is this a known problem? Any Comments or suggestions?
NEW TRY on 7-1:
I was very puzzled by references to "NeoOffice" in previous log messages before (see my comment below). I completely removed NeoOffice from my machine and ran the Haskell Platform installation again. Now the console system log says:
--
Jul 1 11:06:43 jrv installd[1489]: Starting
Jul 1 11:06:43 jrv installd[1489]: uid=0, euid=0
Jul 1 11:06:43 jrv installd[1489]: PackageKit: * Missing bundle identifier: /Library/Receipts/Print Selection Service.pkg
Jul 1 11:07:41 jrv Installer[1472]: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
If so, I'm surprised no one else has seen this problem.
New Edit July 2:
The problems with Library/Receipts/Print Selection Service and others were red herrings, due to the installer finding broken installations, but eliminating these had no effect on the final outcome. Maybe this is something new in 10.6.8?
After eliminating those, I unpacked both the current Haskell Platform and the previous one, and have tried comparing them, but to no real avail. Running diff on the Distribution file of both yields that previous one has a "choice4" while current has a "choice14", but with my meager knowledge of os x packages I don't see that that makes a difference.
I ran installer in verbose mode from the command line, and now get:
sudo installer -verbose -pkg Haskell\ Platform\ 2011-2.2.0.1-i386.pkg -target /
installer: Package name is Haskell Platform
installer: Upgrading at base path /
installer: Preparing for installation….....
installer: Preparing the disk….....
installer: Preparing Haskell Platform….....
installer: Waiting for other installations to complete….....
installer: Configuring the installation….....
installer:
installer: Writing files…..... (lots of writing files, then )
installer: Moving items into place….....(lots of these)
installer: Running package scripts…..... (lots of these, too, and finally:)
installer: Running package scripts….....
##
installer: The upgrade failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
I.e., no real additional information.
I'm out of ideas, but at least I've eliminated a couple of broken apps from my machine :-)
Thanks for all the comments so far.
JRV
I think this is as close as I can come to an answer. I have to infer that something in my installation of HaskellPlatform had gotten messed up, which caused the installation to fail.
When the installation failed the first time (for whatever reason) it installed some of the elements of the platform, but did not make it completely usable.
Finally, I removed all traces (as far as I could tell) of HakellPlatform, cabal and GHC from my computer. After this, I re-downloaded the HP, and reinstalled successfully.
So far the new installation _did_not_fail_, and is working OK.
Thanks to all who commented. I learned a lot.
Related
Whenever I see the update manager glowing that I have an update I get annoyed and click it, so I'm almost always updating something and usually this has gone fine without any problems...
Recently it told me there was a new kernel update, so I clicked install like I usually do but it just got stuck, for hours. When I examined the terminal output it was hanging on a DKMS installation step, so I grabbed all the active DKMS processes and found that the specific thing it was hanging on was installing something called EVDI (which is related to the DisplayLink Ubuntu driver, I think). After letting it sit there doing nothing for more than a day I killed it and had to Timeshift back to before I had done the installation as it corrupted my kernel.
I examined the log file in /var/lib/dkms/evdi/5.2.14/build/make.log and found that it has many errors reported, and the one that starts the chain is:
make -f ./scripts/Makefile.build obj=scripts
make[1]: *** [arch/x86/Makefile:211: archscripts] Error 2
I can provide the full log file if you want, it's just long.
I've tried to google around this and haven't been able to find anyone with this specific issue, so any help is much appreciated! I have also tried installing the DisplayLink driver from source (since it includes an install of EVDI) but it also hangs in the same place (for hours) -- it gets stuck at [[ Installing EVDI DKMS module ]].
I've thought about straight up removing all references to EVDI and hoping that it would then rebuild it, but I am not sure if this would cause further problems. In a different answer I saw that I could remove all DKMS instances of a package from all kernels by doing something like sudo dkms remove package --all but this is entirely new territory for me and I have decided I should wait for someone smarter than me to tell me whether that's a good idea or not before I end up irreparably breaking my installation.
I'm running Linux Mint 20.1 Cinnamon (Cinnamon v 4.8.6), Linux kernel 5.8.0-44-generic, on a Dell XPS 13 with an i7-1065G7 CPU (no GPU). Everything does work fine right now, I just would like to not be stuck on this version of the Linux kernel forever! Any help is very much appreciated :)
Ultimately fixed by booting into an old 5.4 kernel, purging DKMS + all of the 5.8 kernels and a troublesome 5.4 kernel (had to do some things by hand as apt would not remove some directories), then reinstalling everything and updating grub from the 5.4 kernel. Just tested an update via the update manager (now running on the latest 5.8 kernel) and it worked fine! Unclear what exactly was causing the problem but glad it's fixed and hope this helps others if they stumble into something like this.
I downloaded the latest version of Unity platform-agnostic self-extracting installation script and successfully installed it:
$ sudo sh ./unity-editor-installer-5.4.0p1+20160810.sh
Installer for Unity 5.4.0p1
Press Enter to begin extracting to ./unity-editor-5.4.0p1
Unpacking Unity 5.4.0p1 ...
Extraction complete. Run ./unity-editor-5.4.0p1/Editor/Unity to begin
Then I tried to run the Editor:
$ ./unity-editor-5.4.0p1/Editor/Unity
These two windows appear immediately when the command above is run:
and nothing more happened for the whole night. No error messages, no console output, no log files and no syslog entries. top utility shows that Unity process utilizes one core for 100% of it's CPU time.
I run OpenSUSE 13.2 with up-to-date nVidia graphics drivers. My system also matches all dependencies and requirements listed here, and I didn't see any other instructions except "run the installation script, then run the editor". Unity works OK on Windows with the same hardware.
So my questions are:
How (if possible) to run Unity Editor on non-Ubuntu distributions?
Where can I find error messages (if any) which might clarify the reasons of the issue?
This seems to be a common linux bug.
I can't make any assurances but what worked for me (and what seems to be the most suggested fix on the unity forums) is to do two things:
update or install NPM
create the directory "~/.local/share/unity3d/Packages"
If your npm is up to date, the directory thing seems to be the big to-do (it worked like crackers for me).
If you've got both...well, at least you get the joy of adventure trying to figure out what else could be going against you.
I must admit i'm not much of a coder or computer scientist, but in the past a friend installed Weechat on my windows computer using Cygwin (via the Cygwin terminal of course). I have a new computer now thats running windows 8.1 and have installed Cygwin with all of the necessary packages, and downloaded the latest stable version of Weechat (1.2). I am stuck from there though and don't really know which direction to move in, the only thing I have done with Cygwin so far is moved the home terminal folder to a more easier accessible location. Would it be possible to get a step by step walkthrough of how the installation progresses after downloading both the Cygwin component and the Weechat files and scripts?
Before we you can start using WeeChat, there are a few other pieces of software you need to install with CygWin. WeeChat relies on them for its functionality, which is why they are called dependencies.
You can find a detailed list of dependencies and further instructions on this link:
Weechat on Windows
Feel free to ask for further help if the above guide wouldn't suffice.
EDIT
WeeChat is currently available via the CygWin native repositories.
Simply search for weechat in the CygWin package manager.
I already have CygWin installed, what now?
No worries, simply rerun the setup-x86-64.exe* you've downloaded. This process won't remove any of your previously installed packages. At the end of the installation process you'll be able to look for and install WeeChat.
* (on 32-bit systems, the installer would be named setup-x86.exe)
I initially installed haskell platform ( 2013 version; 7.6.3 ghc ) on my mac. Everything was working great. Just now saw the haskell platform website again and found new version was released ( Haskell Platform 2014.2.0.0 for Mac OS X, 64bit ). I installed it, and un-installed the older version using uninstall-hs.
Now when i type "cabal" or "cabal update" on my terminal, it hangs. Actually when i look into Activity Monitor, i can see that it is invoking some "sh script & possibly some find command" infinitely. I initially guess may be it is building some indexes. but it has been running for an hr or so.
Please advice. I cannot install any other package using cabal.
As suggested by Zeta, you can remove (or to be safe, backup) ~/.cabal and ~/.ghc first. I also have a Mac OS X 10.9.4 and recently upgraded. I ran the uninstall-hs script, and installed the new Haskell Platform 2014. Even without backing up those directories though, I still had an event free uninstall/update.
Also, ensure to double check your paths in your ~/.bash_profile, as they will need to be updated.
Here is an example of mine, to hopefully give you some clues as what may need to be done.
# Haskell / Cabal
export PATH="$HOME/Library/Haskell/bin:$PATH"
export PATH="$HOME/Library/Haskell/ghc-7.8.3-x86_64/lib/cabal-install-1.20.0.3/bin:$PATH"
export PATH="$HOME/.emacs.d/hslint:$PATH"
export PATH="$HOME/Library/Haskell/ghc-7.8.3-x86_64/lib/cgrep-6.4.4/bin:$PATH"
As for cabal try $ which cabal and cabal -V to verify you are running the latest 1.20 cabal version and that it's set in your $PATH.
I installed Cygwin on Windows 7 and it installed properly.
I selected various packages; including curl and wget.
Yet, my anti-virus (AVG 2011) detected it as malware, with 4 red bars and put it into the Virus Vault!
I then sent the suspected file to Kaspersky's filescanner online but it came back as clean from their online scan
I then proceeded to uninstall Cygwin and restart Windows; now it's left me a bit wary of using it on Windows 7 again for fear of a virus.
Is wget always detected as a virus, and should I always be this cautious with cygwin?
Is there much difference between the Windows versions of wget and the Linux/unix ones?
Some sources I read suggested I download the older wget versions to reduce the risk of virus; the Wget version in question that was detected as a virus was the latest one.
What's the best way to deal with this issue?
If you downloaded wget from an official Cygwin repository, there's nearly no chance of a virus.
I think AVG is a little bit overzealous, and since wget is used to download data from the internet, it is recognized as a malware.
Nothing to be afraid about, you can ignore the problem I think.
You should maybe just contact the AVG team to make them aware of the situation.