OS X: equivalent of Linux's wget. Ask Question 419. How can I do an HTTP GET from a Un*x shell script on a stock OS X system? (installing third-party software is not an option, for this has to run on a lot of different systems which I don't have control on). Just download, install, and run. Works with Mac OS X 10.3-10.12+. Wget is the default download manager in the Unix world and I was surprised to discover that it is not present on Mac by default. There are a few ways to install it, though: direct compilation, homebrew, macports etc. But I prefer the direct compilation simply because it is the easiest way to go.
Checking whether to enable maintainer-specific portions of Makefiles. No checking for perl. /usr/bin/perl configure: error: XML::Parser perl module is required for intltool The first complaint is about a missing XML::Parser module.
In order to install that you have to first install expat and the best way to install expat is using Fink. Installating Fink is a breeze because a dmg is available. Then using the fink commander to installer expat isn't difficult either. From then on you have to return to the commad line something that OS X users hate to do.
But I am not an OS X user. Perl -MCPAN -e shell prompts you for a series of configuration options, I just used the defaults for all of then. Unfortunately that will made the system unusable because a mirror list was not made. To make matters worse, LWP, lynx and wget are all missing on my macbook. That makes it impossible for the CPAN installer to download files. Let's go back to fink and install wget There is more than one way skin a cat. I came up against this link which mentioned two of them: The painless way is to install the module using fink.
Once you pass that hurdle, the next error is about pckconfig. The pkg-config script could not be found. Make sure it is. in your path, or set the PKGCONFIG environment variable. to the full path to pkg-config. Or see to get pkg-config. Configure: error: Library requirements (gimp-2.0 gimpui-2.0) not met; consider adjusting the PKGCONFIGPATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.
That too can be installed with fink but don't think you are out of the woods yet. Checking for gimp-2.0 gimpui-2.0. Package gimp-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `gimp-2.0.pc' to the PKGCONFIGPATH environment variable No package 'gimp-2.0' found configure: error: Library requirements (gimp-2.0 gimpui-2.0) not met; consider adjusting the PKGCONFIGPATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. It's tough but the gimp-2.0.pc file is not present on my macbook even though gimp itself is installed. Gimp 2x is not available if you use fink.
I manually created the.pc files and now, the error is. libintlbindtextdomaincodeset referenced from libglib-2 expected to be defined in /usr/local/lib/libintl.3.dylib libintlbindtextdomain referenced from libglib-2 expected to be defined in /usr/local/lib/libintl.3.dylib libintldgettext referenced from libglib-2 expected to be defined in /usr/local/lib/libintl.3.dylib This is way too much trouble. For some reason the linker is not looking for the libraries in the /sw/lib path, even though the -L option as used in the Makefile clearly says that the linker should look for those libraries there. Now it's finally time to give up.
. This tutorial provides a deep dive of Homebrew, a package manager for Mac OSX (MacOS) like Chocolatey for Windows, apt-get for dpkg, or yum for RPM. Step-by-step instructions are provided here to install Homebrew itself and then install Homebrew packages based on the name of formulae specified for installation in a command such as: brew install wget DEFINITION: A formula provides instructions on how to install packages and their dependencies, such as where to find tar.gzip files for download. Brew installs packages in its own Cellar directory (folder) and adds symlinks to the /usr/local folder. About Homebrew Homebrew is the newest and most popular package utility on OSX. Alternatives to Homebrew:. sudo port install tree.
Homebrew’s web page is at Preparations: XCode CLI. Make a full backup of your system right before following these instructions.
Open the App Store to install XCode, Apple’s IDE for developing Swift and Objective-C to run on iPhones and iPads. PROTIP: Apple’s App Store only installs.app files. So programs invoked from the command line Terminal (such as gcc) need to be installed a different way.
To verify XCode CLI install: /usr/bin/xcodebuild -version This message means that it’s not installed: xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance. Open a Terminal to install XCode CLI: xcode-select -install If XCode is not already installed, you are prompted to install it: Installation is to folder: /Library/Developer/CommandLineTools/. Homebrew requires OS X 10.5+ and the Xcode command line tools. To download the Command Line Utilities, go to and look for your version of “Command Line Tools (macOS 10.14) for XCode 10”, one that doesn’t say “beta”.