Install Older Version Of Osx

 



For common Un*x operating systems (including macOS), all you need to do is run:

Stack latest stable version; haskell-stack-git git version; In order to use stack setup with older versions of GHC or on a 32-bit system, you may need the ncurses5-compat-libs AUR package installed. If this package is not installed, Stack may not be able to install older (. I expected the “make install-openni2” command from libfreenect2’s readme would take care of that stuff, but it does not. The second omission is the troubleshooting stuff on their wiki. In particular, for my specific MacBook, I had to plug the Kinect adapter into the USB port on the left-hand side, NOT the right-hand side, as the device. The serial version works well for smaller analyses but if you plan to run large analyses using many parallel chains, you should use the MPI version instead. Refer to the User Manual, and the INSTALL document on GitHub for help with installation of the program. Works like a charm — I've been upgrading git all the time using this package and never had the slightest problem. My only issue is that it lags slightly behind the latest & greatest supported git package — it's really a pity it's not kept up-to-date with, say, the Linux version. MongoDB Version¶. This tutorial installs MongoDB 4.4 Community Edition. To install a different version of MongoDB Community, use the version drop-down menu in the upper-left corner of this page to select the documentation for that version.

or:

Note that this script will ask for root access using sudo in orderto use your platform's package manager to install dependencies and toinstall to /usr/local/bin. If you prefer more control, follow themanual installation instructions for your platform below.

Binaries for other operating systems are listed below, and available onthe GitHub release page. For thefuture, we are open to supporting more OSes (to request one, pleasesubmit an issue).

Binary packages are signed with this signing key.

Install older version of osx

If you are writing a script that needs to download the latest binary, you canuse URLs like https://get.haskellstack.org/stable/<PLATFORM>.<EXTENSION>(e.g. https://get.haskellstack.org/stable/linux-x86_64.tar.gz) that alwayspoint to the latest stable release.

Windows¶

We recommend installing to the default location with these installers, as thatwill make stack install and stack upgrade work correctly out of the box.

If in doubt: you should prefer the 64-bit installer.

You may see a 'Windows Defender SmartScreen prevented an unrecognized app fromstarting' warning when you try to run the installer. If so, click onMore info, and then click on the Run anyway button that appears.

Manual download¶

  • Download the latest release:

  • Unpack the archive and place stack.exe somewhere on your %PATH% (see Path section below) and you can then run stack on the command line.

  • Now you can run stack from the terminal.

macOS¶

We generally test on the current version of macOS and do our best to keep it compatible with the three most recent major versions. Stack may also work on older versions (YMMV).

Version

Installer script¶

Run:

Manual download¶

  • Download the latest release:
  • Extract the archive and place stack somewhere on your $PATH (see Path section below)
  • Now you can run stack from the terminal.

Using Homebrew¶

If you have the popular brew tool installed, you can just do:

  • The Homebrew formula and bottles are unofficial and lag slightly behind new Stack releases,but tend to be updated within a day or two.
  • Normally, Homebrew will install from a pre-built binary (aka 'pour from abottle'), but if brew starts trying to build everything from source (whichwill take hours), seetheir FAQ on the topic.

Notes¶

After installation, running stack setup might fail with configure: error: cannot run C compiled programs. in which case you should run:

Starting with macOs 10.14 (Mojave) running xcode-select --installmight not be enough. You will need to install additional headers by running:

If you are on OS X 10.11 ('El Capitan') and encounter either of theseproblems, see the linked FAQ entries:

If you are on OS X 10.12 ('Sierra') and encounter GHC panic while building, see this issue

Ubuntu¶

Version

Use the generic Linux option.

There is also a Ubuntupackagefor Ubuntu 16.10 and up, but the distribution's Stack version lags behind, so werecommend running stack upgrade --binary-only after installing it. For older stackversions which do not support --binary-only, just stack upgrade may work too. Theversion in Ubuntu 16.04 is too old to upgrade successfully, and so in that casestack should be installed from a releasetarball.

Debian¶

Use the generic Linux option.

There is also a Debianpackagefor Stretch and up, but the distribution's Stack version lags behind, so runningstack upgrade --binary-only is recommended after installing it. For older stackversions which do not support --binary-only, just stack upgrade may work too.

CentOS / Red Hat / Amazon Linux¶

Use the generic Linux option.

There is also an unofficialCopr repo.Note that this Stack version may lag behind,so we recommend running stack upgrade after installing it.

Fedora¶

Use the generic Linux option.

Fedora includes builds of stack, but the version may lag behind,so we recommend running stack upgrade after installing it.

openSUSE / SUSE Linux Enterprise¶

Use the generic Linux option.

There is also an unofficial SUSE package. Note that this Stackversion may lag behind, so we recommend running stack upgrade after installingit. To install it:

  1. Add the appropriate OBS repository:

    • openSUSE Tumbleweed

      all needed is in distribution

    • openSUSE Leap

    • SUSE Linux Enterprise 12

  2. Install:

Arch Linux¶

There is an official package in the Arch community repository. So you caninstall it by simply doing:

Note that this version may slightly lag behind, but it should be updated withinthe day. The package is also always rebuilt and updated when one of itsdependencies gets an update.

  • stacklatest stable version
  • haskell-stack-gitgit version

In order to use stack setup with older versions of GHC or on a 32-bit system,you may need thencurses5-compat-libsAUR package installed. If this package is not installed, Stack may not be ableto install older (< 7.10.3) or 32-bit GHC versions.

If you use theArchHaskell repository, youcan also get the haskell-stack-tool package from there.

NixOS¶

Users who follow the nixos-unstable channel or the Nixpkgs master branch can install the latest stack release into their profile by running:

Alternatively, the package can be built from source as follows.

  1. Clone the git repo:

  2. Create a shell.nix file:

    Note that the tests fail on NixOS, so disable them with --no-check. Also, haddock currently doesn't work for stack, so --no-haddock disables it.

  3. Install stack to your user profile:

For more information on using Stack together with Nix, please see the NixOSmanual section onStack.

Osx

Linux (generic)¶

Installer script¶

Run:

or:

Itunes

Manual download¶

  • Download the latest release:

  • Extract the archive and place stack somewhere on your $PATH (see Path section below)

  • Ensure you have required system dependencies installed. These include GCC, GNU make, xz, perl, libgmp, libffi, and zlib. We also recommend Git and GPG. To install these using your package manager:

    • Debian / Ubuntu: sudo apt-get install g++ gcc libc6-dev libffi-dev libgmp-dev make xz-utils zlib1g-dev git gnupg netbase
    • Fedora / CentOS: sudo dnf install perl make automake gcc gmp-devel libffi zlib zlib-devel xz tar git gnupg (use yum instead of dnf on CentOS and Fedora <= 21)
      • Fedora 24: In order to use stack setup on a 32-bit system, you may need to run sudo dnf install ncurses-compat-libs. If this package is not installed, Stack may not be able to install 32-bit GHC versions.Also sudo dnf install ncurses-compat-libs if you nee

    • Arch Linux: sudo pacman -S make gcc ncurses git gnupg xz zlib gmp libffi zlib

      • In order to use stack setup with older versions of GHC or on a 32-bit system, you may need the ncurses5-compat-libs AUR package installed. If this package is not installed, Stack may not be able to install older (< 7.10.3) or 32-bit GHC versions.
        • Gentoo users, make sure to have the ncurses package with USE=tinfo (without it, stack will not be able to install GHC).

  • Now you can run stack from the terminal.

Path¶

You can install stack by copying it anywhere on your PATH environment variable. A good place to install is the same directory where stack itself will install executables. On Windows, that directory is %APPDATA%localbin, e.g. c:UsersMichaelAppDataRoaminglocalbin. For other systems, it's $HOME/.local/bin.

If you don't have that directory in your PATH, you may need to update your PATH (such as by editing ~/.bashrc).

If you're curious about the choice of these paths, see issue #153

Shell auto-completion¶

To get tab-completion of commands on bash, just run the following (or add it to.bashrc):

For more information and other shells, see the shell auto-completion page

China-based users¶

If you're attempting to install stack from within China:

  • As of 2020-02-24, the download link has limited connectivity from within mainland China. If this is the case, please proceed by manually downloading (ideally via a VPN) and installing stack per the instructions found on this page pertinent to your OS.

  • After install, your ~/.stack/config.yaml will need to be configured before stack can download large files consistently from within China (without reliance on a VPN). Please add the following to the bottom of the ~/.stack/config.yaml file (for Windows: use the %STACK_ROOT%config.yaml):

Using an http proxy¶

To use stack behind a http proxy with ip address IP and port PORT, first set up an environment variable http_proxy and then run the stack command. e.g.

Note that on most operating systems, it is not mandatory for programs to follow the 'system-wide' http proxy. Some programs, such as browsers, do honor this 'system-wide' http proxy setting, while other programs, including bash, do not. That means configuring 'http proxy setting' in your Control Panel (Windows) or System Preferences (Mac) would not result in stack traffic going through the proxy.

Upgrade¶

There are essentially four different approaches to upgrade:

  • The stack tool itself ships with an upgrade command, which download a stack binary or build it from source and install it to the default install path (e.g. ~/.local/bin or %APPDATA%localbin; see the Path section above). You can use stack upgrade to get the latest official release, and stack upgrade --git to install from Git and live on the bleeding edge. Make sure the default install directory is on your PATH and takes precedence over the system installed stack, or copy stack from that directory to the system location afterward. For more information, see this discussion.

  • If you're using a package manager and are happy with sticking with the officially released binaries from the distribution (which may the lag behind latest version of Stack significantly), simply follow your normal package manager strategies for upgrading (e.g. apt-get update && apt-get upgrade).

  • The get.haskellstack.org script supports the -f argument to over-write the current stack executable. For example:

    curl -sSL https://get.haskellstack.org/ | sh -s - -f

or:

  • Manually follow the steps above to download the newest binaries from the release page and replace the old binary.

Install Older Versions¶

To install a specific version of stack, navigate to the desired version on the GitHub release page,and click the appropriate link under its 'Assets' drop-down menu.

Alternatively, use the URL https://github.com/commercialhaskell/stack/releases/download/vVERSION/stack-VERSION-PLATFORM.EXTENSION.For example, the tarball for stack 2.1.0.1, osx-x86_64 is athttps://github.com/commercialhaskell/stack/releases/download/v2.1.0.1/stack-2.1.0.1-osx-x86_64.tar.gz.

Here's a snippet for appveyor.yml files, borrowed from dhall's appveyor.yml.Change the values of PATH and VERSION as needed.

So you have a MacBook (or something else that runs OSX) and you want to play with the Kinect sensor, but you’re having trouble because there are about 1 billion sets of wrong instructions on the internet on how to connect this Kinect. Let me save you a little grief.

Hardware

I have the Kinect “v2”, aka Kinect for Xbox One, aka Kinect for Windows, aka (in my case) Model 1520. The instructions below work for my version. The only serious difference if you have the older Kinect should be that you use a different version of libfreenect, but I haven’t tested that.

Software

How To Install Older Version Of Osx

You have more than one option as far as software goes. If you’re a commercial developer, you might consider trying out Zigfu’s ZDK, which has an OSX-ready image and integrates with several modern packages, including Unity3d, out of the box.

If you’re more of a hobbyist (as I am at the moment) and don’t have the $200 for a Zigfu license, the lovely folks behind the Structure Sensor have taken on maintenance of the OpenNI2 library, including a macOS build. Your first step should be to download the latest version of that library and unzip it somewhere.

Unfortunately, their package isn’t quite complete, and you’ll also need a driver to connect the Kinect (I know, it’s getting old to me too). This is where our ways may diverge, gentle reader, for in my case I discovered that I needed OpenKinect’slibfreenect2, whereas an older sensor would require libfreenect.

Assuming that you’re using the XBox One sensor, you’ll want to read the README.md that comes with your copy of libfreenect2. It contains all the necessary instructions for getting the right tools + dependencies and building all the things.

There are two additional things that are currently left out of their readme file. The first is that when you want to use the OpenNI2 tools, you’ll need to copy the drivers from

libfreenect2/build/lib

into

{bin-folder}/OpenNI2/Drivers

for whatever you’re running. So to run NiViewer, which is in the Tools folder, you’d copy it to

{openni-base-folder}/Tools/OpenNI2/Drivers

I expected the “make install-openni2” command from libfreenect2’s readme would take care of that stuff, but it does not.

Install Older Version Of Os X On Partition

The second omission is the troubleshooting stuff on their wiki. In particular, for my specific MacBook, I had to plug the Kinect adapter into the USB port on the left-hand side, NOT the right-hand side, as the device requires USB3, and I had to run Protonect and NiViewer using the “cl” pipeline. The default pipeline setting can be changed by doing this:

export LIBFREENECT2_PIPELINE=cl

You can also pass in the pipeline for Protonect:

bin/Protonect cl

With that setting in place, you should see a window with 2 (NiViewer) or 4 (Protonect) windows, each capturing different parts of the raw Kinect stream:

Install Older Version Of Osx

From here you’re on your own, but I hope you found this at least a bit helpful!