I would like to install the php-intl extension for PHP on my Mac. I know the current PHPÂ installation was installed with the OS (Mac OS X 10.6).
So I am wondering if I install the php5-intl package using Macports, will it install a second version of PHP (which I don't want), or will it upgrade my existing installation?
If I can't upgrade my current PHP installation that way, how can I proceed?
Installing the MacPorts php5-intl port will install PHP's intl extension for use with MacPorts php5, which it will also install; you'll also get MacPorts' copy of the apache2 server. MacPorts is designed to be self-contained; it's not designed to modify or integrate with any software components Apple provided with your OS. This is a good thing; Apple occasionally makes unexpectedly changes to their OS components which could break things installed by MacPorts.
If you want to give MacPorts apache2 and php5 a try, check out the MacPorts MAMP guide in the wiki.
Related
I was watching this, and, as you can see, the first command I am told to put in is:
sudo apt-get install python-setuptools
When I do this, it outputs:
sudo: apt-get: command not found
I have no idea why this is the case.
How can I resolve this so I am following the tutorial correctly?
Mac OS X doesn't have apt-get. There is a package manager called Homebrew that is used instead.
This command would be:
brew install python
Use Homebrew to install packages that you would otherwise use apt-get for.
The page I linked to has an up-to-date way of installing homebrew, but at present, you can install Homebrew as follows:
Type the following in your Mac OS X terminal:
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
After that, usage of Homebrew is brew install <package>.
One of the prerequisites for Homebrew are the XCode command line tools.
Install XCode from the App Store.
Follow the directions in this Stack Overflow answer to install the XCode Command Line Tools.
Background
A package manager (like apt-get or brew) just gives your system an easy and automated way to install packages or libraries. Different systems use different programs. apt and its derivatives are used on Debian based linux systems. Red Hat-ish Linux systems use rpm (or at least they did many, many, years ago). yum is also a package manager for RedHat based systems.
Alpine based systems use apk.
Warning
As of 25 April 2016, homebrew opts the user in to sending analytics by default. This can be opted out of in two ways:
Setting an environment variable:
Open your favorite environment variable editor.
Set the following: HOMEBREW_NO_ANALYTICS=1 in whereever you keep your environment variables (typically something like ~/.bash_profile)
Close the file, and either restart the terminal or source ~/.bash_profile.
Running the following command:
brew analytics off
the analytics status can then be checked with the command:
brew analytics
As Homebrew is my favorite for macOS although it is possible to have apt-get on macOS using Fink.
MacPorts is another package manager for OS X:.
Installation instructions are at The MacPorts Project -- Download & Installation after which one issues sudo port install pythonXX, where XX is 27 or 35.
Conda can also be used as package manager. It can be installed from Anaconda.
Alternatively, a free minimal installer is Miniconda.
apt-get command is only available on Debian or Debian-based Linux distributions (such as Ubuntu, Linux Mint, Kali). It is not accessible on macOS. Alternatively, you can use package managers like Homebrew, MacPorts, and Nix. You can find equivalent commands for each as follows
brew install package_name
sudo port install package_name
nix-env -i package_name
Before installing above package managers, you need to install XCode first. Follow the operation instructions from this guide How to Fix "sudo apt-get command not found" Error on Mac Terminal.
Alternatively You can use the brew or curl command for installing things, wherever apt-get is mentioned with a URL...
For example,
curl -O http://www.magentocommerce.com/downloads/assets/1.8.1.0/magento-1.8.1.0.tar.gz
I am trying to install openmpi from Macports on Sierra 10.12.5. It seems that it is a straight forward command:
sudo port install openmpi
When I do this, I get the error:
sudo: port: command not found
I gathered from similar threads that this may be due to openmpi already being installed. How can I check if it is installed, and if so, uninstall it so that I can reinstall it using Macports with the above command? Any thoughts would be great. Thanks!
By default, the port command is installed at /opt/local/bin/port. The installer normally modifies your PATH environment variable to include '/opt/local/bin' so that you can launch stuff installed by MacPorts just by entering the name of the command. I think you should re-do the MacPorts installation. Follow:
https://www.macports.org/install.php
You almost certainly want to use the macOS package installer. You may have to restart Terminal for the new PATH to take effect.
I am running Mac OS 10.7.5, and I was wondering how I can install an older version of git. Also, which version do people recommend? Since I get C files if I download an older version, do I run them with my bash profile?
While installing CodeLite IDE in Ubuntu following error occurs.
Any idea?
ERROR:
The following packages have unmet dependencies:
codelite : Depends: libjbig0 but it is not installable
Depends: liblzma5 (>= 5.1.1alpha+20120614) but 5.1.1alpha+20110809-3 is to be installed
Depends: libpango-1.0-0 (>= 1.18.0) but it is not installable
Depends: libpangocairo-1.0-0 (>= 1.14.0) but it is not installable
E: Unable to correct problems, you have held broken packages.
I had a similar problem. You may need to check your version of Ubuntu, and that you've added the correct repositories. If this is the problem, then the fix is very simple!
Firstly, check your version of Ubuntu. From terminal you can do this with the command lsb_release -a. The important part, for our purpose, is the codename. I'm using Ubuntu 13, aka "saucy".
Now let's look at the multiverse repository that you added. From the terminal you can do this with sudo gedit /etc/apt/sources.list. Go down to the end of the file, and you should see something like:
## This software is not part of Ubuntu, but is offered by third-party
## developers who want to ship their latest software.
deb http://repos.codelite.org/ubuntu/ saucy universe
Make sure that your version has your ubuntu codename (in my case 'saucy'). The example code on the website is for Ubuntu 14, and so I wrongly had a 'trusty' source here. Edit the line so that it is correct for your version of Ubuntu, and then save and close the file.
Lastly, you'll need to update your repos so that the change goes through. From the terminal, run sudo apt-get update. All being well, you should now be able to sudo apt-get install codelite without the errors.
My problem was caused by too much cutting-and-pasting code from the codelite website. I followed exactly the same page as you did, and their example code is for people with Ubuntu trusy (14).
You will need to be more specific on how you tried to install codelite.
The official Debian repository manages an ancient version of codelite which we (the codelite team) do not support.
In order to get the most up-to-date version (that we support) please install it from codelite's official website (select the Download at menu at the top)
Before installing, make sure you delete the folder ~/.codelite (incase you are upgrading)
Also, the official Debian installer is split into 2 pakacges codelite and codelite-plugins make sure you purge them both before installing codelite from our repository
I'm the author of Howto install the latest codelite in Ubuntu - EuroBytes. I have tested the latest codelite on Trusty.
If you still have issues with codelite, remove like so: sudo apt-get purge codelite
Note that the dependencies links are dead. But, i managed to install it anyways:
codelite 6.1 on Ubuntu Trusty Thar 14.04.
Image from: Howto install the latest codelite in Ubuntu - EuroBytes
Install like so:
sudo apt-add-repository "deb http://repos.codelite.org/ubuntu/ $(lsb_release -sc) universe"
sudo apt-key adv --fetch-keys http://repos.codelite.org/CodeLite.asc
sudo apt-get update
sudo apt-get install codelite wxcrafter
Feel free to contact me here or on my site, for any issues you may have.
Source:
Howto install the latest codelite in Ubuntu - EuroBytes
I just got Macports installed on my mac, of which os version is Snow Leopard (10.6). I used Macports to install several packages through 'sudo port install' command, and all these packages are reported active after the installation. I just wonder that whether these packages are really working? For example, macports tells me that 'gcc44 #4.4.2_0 (active)', however in python it says '[GCC 4.0.1 (Apple Inc. build 5493)] on darwin'.
So I just want to know that if there is some problem with my method of installing or my macports needs some configuration after installation?
Any help is appreciated! I am really new in Mac OS.
I believe Python is declaring the version of gcc used to build it which should be the gcc installed on your Mac i.e. the version that came with the Mac OS Development tools. This should be located in /usr/bin/gcc.
You should find the gcc version matches when you execute
/usr/bin/gcc -v
I do not think anything is wrong with your setup or configuration. It just shows Python was compiled using the gcc provided by Apple
Macports installs software not to conflict with the versions provided by Apple. If they replaced the C compiler and libraries, really bad things might happen when Apple provided operating system updates.
gcc is the command for Apple's version of gcc, at /usr/bin and version 4.0.1 for Leopard.
gcc-mp-4.4 is the command for gcc version 4.4 as provided by MacPorts, located at /opt/local/bin.
Similarly there will be versions of python in /opt/local/bin.
Like houmam, I prefer to explicitly invoke versions by name. If you want to connect particular versions to python, I think that the MacPorts package python_select (this has now been replace by port select python) implements this by using symbolic links. I've never used it.
It probably is just that compiler that was picked by the build was that installed by XCode. You can try typing which gcc to see which one is in your path. The macports one would by default be in /opt/local somewhere.