The wget utility recently came up in a JavaRanch topic and I recalled that this very useful utility doesn't come natively installed on Mac OS X, even if you install the Developer Tools.
I also recalled that it took me less than 10 minutes to download the sources and build it.
Figuring that I should probably rebuild the latest and greatest, here are the steps I took to build wget 1.9 on Mac OS X 10.3.8 with the Developer Tools installed:
- Get the source from ftp://ftp.gnu.org/pub/gnu/wget/wget-1.9.tar.gz
- Unpack the tarball:
tar xzf wget-1.9.tar.gz - This creates a folder named
wget-1.9. Change the working folder to it:cd wget-1.9/ - Configure the build:
./configure - Build:
make - Install:
sudo make install - The
wgetbinary should now be in your /usr/local/bin folder.
TrackBacks[0]
Comments[69]
Posted by bear on March 2, 2005 11:58:00 PM CST
Reply |
Permalink
Re: Building wget for Mac OS X
howdy, I stumbled across this googling for "wget osx"... I'm on 10.3.5 at work, and I had to use "./configure --without-ssl" to get it to compile right.
Comment from qwe on March 7, 2005 11:51:01 AM CST
I'm on 10.3.8 and didn't have an issue compiling with the instructions stated.
Comment from TheRealBrad on March 8, 2005 8:19:04 AM CST
i can't seem to get it to work either way. I try compiling it, and it seems to compile fine, "wget" appears in /usr/local/bin. but when i try and call the command it gives me a "-bash: wget: command not found"
Comment from Ashton on March 11, 2005 1:32:38 AM CST
It doesn't matter where you put it as long as where you put it is in your $PATH.
To the person who couldn't get it to work after seeing it in /usr/local/bin, make sure you actually have /usr/local/bin in your path and log back into your shell. Your shell won't know about the addition until you log back in. (There is also a command for reloading, but I can't remember what it is.)
To the person who had to use sudo make, it's simply a permissions issue. When you use the default make, you have to make sure your user has adequate permissions on all the directories/files it's trying to access. sudo make will temporarily act as root so you won't have permission issues.
Comment from TheRealBrad on April 27, 2005 10:21:01 AM CDT
I don't have gcc or any of compile stuff. Where I can get it?
Comment from Diego on March 11, 2005 6:42:21 PM CST
You should be able to grab the developers tools from the Apple web site if you not longer have the install disk that came with the OS.
Comment from Anonymous on March 25, 2005 5:20:21 PM CST
Ashton: /usr/local/bin/ isn't in your path by default. either copy wget to /usr/bin/ or add /usr/local/bin/ to your path.
Comment from qwe on March 16, 2005 3:56:45 PM CST
I do that(/usr/local/bin/wget http://www.download.com), and it works. Is there any way that i can avoid this? If you type "alias wget=/usr/local/bin/wget" it works, but you have to type that in everytime you open a new terminal for it to work right. SHouldn't i be able to call wget by typing "wget url"?
Comment from Ashton on March 17, 2005 7:57:32 PM CST
Put /usr/local/bin in your .bash_profile (this is assuming that you're using the bash shell).
1. Create a .bash_profile file (if you don't already have one). You can either 'touch .bash_profile' or use any text editor to do it.
2. Edit the path so that it reads "PATH=$PATH:/usr/local/bin".
3. Make sure that the PATH variable is exported. On another line, add "export PATH".
You can now "source .bash_profile" to get it working with the current terminal. Now every time you start the terminal, /usr/local/bin will be in the path.
Comment from DSH on March 18, 2005 10:20:54 PM CST
Thanks! I needed that clue on .bash_profile for adding to the PATH. Oy!
Comment from Anonymous on August 7, 2005 1:07:42 PM CDT
Hi Bear, are you familiar with curl? A year ago I was writing a script that grabbed something from a web site, and for some reason it was a lot easier to do with curl than with wget. Sorry I can't be more specific; it's been too long.
Comment from Bill Smith on March 25, 2005 6:34:15 PM CST
Actually, though I've heard of it, I haven't looked into curl. Perhaps when I get a few moments...
Thanks.
Comment from Bear on March 29, 2005 2:23:06 PM CST
After I use the make command I end up with the following,
/bin/sh ../libtool --mode=link gcc -O2 -Wall -Wno-implicit -o wget cmpt.o connect.o convert.o cookies.o ftp.o ftp-basic.o ftp-ls.o ftp-opie.o hash.o headers.o host.o html-parse.o html-url.o http.o init.o log.o main.o gen-md5.o netrc.o progress.o rbuf.o recur.o res.o retr.o safe-ctype.o snprintf.o gen_sslfunc.o url.o utils.o version.o -lssl -lcrypto -ldl
mkdir .libs
gcc -O2 -Wall -Wno-implicit -o wget cmpt.o connect.o convert.o cookies.o ftp.o ftp-basic.o ftp-ls.o ftp-opie.o hash.o headers.o host.o html-parse.o html-url.o http.o init.o log.o main.o gen-md5.o netrc.o progress.o rbuf.o recur.o res.o retr.o safe-ctype.o snprintf.o gen_sslfunc.o url.o utils.o version.o -lssl -lcrypto -ldl
ld: Undefined symbols:
_OpenSSL_add_all_algorithms
make[1]: *** [wget] Error 1
make: *** [src] Error 2
Any ideas?????
Thx!
Comment from Felipe on April 10, 2005 10:36:55 AM CDT
ok I solved it (not sure if correctly) using sudo make instead of just make... any comments??
Thx
Felipe
Comment from Felipe on April 10, 2005 11:49:23 AM CDT
Is there any reason for putting it into /usr/local/bin? I should have thought /bin/ was a more natural place to put it, since there are already lots of cmdline tools there.
Comment from Marion Dickten on April 10, 2005 11:55:00 AM CDT
/usr/local/bin/ is for your 'local' command line tools. That is to say, those -you- installed versus those installed by default.
Comment from Anonymous on May 5, 2005 4:10:50 PM CDT
I got wget to build fine. however i was a little miffed at the fact I had to sim link the man page....
for those who wish to know what I did to get it to show using man wget:
cd /usr/share/man/man1
sudo ln -s /usr/local/man/man1/wget.1 wget.1
I did not see any mention to this but i dont have enough brain to remember all the options for all the stuff I know.... thats why god invented man pages
Comment from KingJoe_BOB on May 11, 2005 9:55:06 AM CDT
Always remember to type "rehash" after installing something so that the binaries already in your path, but newly added, are added to the list.
Comment from gwen on May 24, 2005 3:57:35 PM CDT
the wget binary is in my /usr/local/bin folder...but i still cannot use it. when i attempt to use it, i get a "wget command not found". i believe it wasnt installed correctly but i followed the steps exactly. im using tiger if that effects anything. any help?
Comment from Wray on June 17, 2005 3:05:28 PM CDT
>but i still cannot use it.
At the command prompt, type:
echo $PATH
Is /usr/local/bin one of the paths on the list? (the list is colon-separated)
Comment from Bear on June 17, 2005 4:13:00 PM CDT
Or better yet.. change into the /usr/local/bin directory and execute from there to make sure it is indeed a $PATH issue or if the binary just doesn't work.
cd /usr/local/bin
./wget www.google.com
If that works you built it correctly and you just need to add /usr/local/bin to your $PATH so you can execute the command without being in /usr/local/bin. If it doesn't work, there is an issue with the binary file.
Comment from Brad on June 17, 2005 4:52:52 PM CDT
Ok i checked the path and it wasnt in there. so i used
# export PATH=$PATH:/usr/local/bin.
and when echoed it was there.
Now when i open a new shell and echo, the path is back to normal. Apparently its only being added for the sesssion. Is there a way to permanatly add it to the PATH env.
Comment from Wray on June 19, 2005 1:29:01 PM CDT
Add the export to your .bash_profile.
Comment from Bear on June 19, 2005 7:47:41 PM CDT
using tiger and wget-1.10. when i run /.configure it errors saying:
error: no acceptable C compiler found in $PATH
Comment from kjk on June 28, 2005 10:52:06 AM CDT
Do you have the developer tools installed?
I do not believe that the C compiler comes with the base installation.
Comment from Bear on June 28, 2005 10:57:08 AM CDT
that is probably it. thanks.
Comment from kjk on June 28, 2005 11:22:03 AM CDT
Hi everybody,
I'd like to install a path for wget, but i have no idea of how i could do that. Any suggestions?
Anne-So
Comment from Anonymous on June 30, 2005 2:57:32 PM CDT
installed the developer tools and all is well, now. thanks again.
Comment from kjk on July 4, 2005 10:34:53 AM CDT
i'm confused, So i follow the steps sudo make install. go back to root ...cd /usr/local/bin ...dir
it tells me "no such file or directory" anyway so i'm really confused. what should i be doing next. what do i do with the wget in the /usr/local/bin? what is all this about the $PATH? please help. thanks
Comment from Anonymous on July 21, 2005 2:36:11 AM CDT
I don't mean to sound rude or elite, but if you don't know what $PATH is or how to execute something from a command line, why are you trying to use wget? What do you need it for?
Comment from Anonymous on July 21, 2005 10:08:41 AM CDT
if you are the administrator BUT NOT ROOT USER, simply do:
1) unzip the source file
2) cd wget*** *** being the version
3) ./configure
4) make
5) make install
6) you are done, to use wget, simply open a terminal and type "wget link" to download the link to the current directory
hope this helps the confused folks out there
P.S. This is tested to work on OSX 10.4.2
Comment from Anonymous on July 31, 2005 2:13:23 PM CDT
Bear's instructions at the top of the thread work great in 10.3.9. Had to cd to /usr/bin and create a symlink with sudo ln -s /usr/local/bin/wget wget to get it to run.
Comment from Anonymous on August 8, 2005 9:08:32 PM CDT
I'm having trouble with the installation on my G5.
When I run the ./configure command I get :
configuring for GNU Wget 1.9
checking build system type... powerpc-apple-darwin7.9.0
checking host system type... powerpc-apple-darwin7.9.0
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... gcc
checking for C compiler default output... configure: error: C compiler cannot create executables
See `config.log' for more details.
The .log file indicates that the failure is occurring with line 2044, but I'm not sure how to fix this problem.
Any help would be greatly appreciated.
Comment from Anonymous on August 11, 2005 2:24:57 PM CDT
C compiler cannot create executables See `config.log' for more details.
I was getting this error because I was trying to do a minimal install of xcode tools. I just wanted to compile command line programs. After fiddling a bit, this is what I needed to include in the custom setting of the xcode install.
I was getting this error because I was trying to do a minimal install of xcode tools. I just wanted to compile command line programs. After fiddling a bit, this is what I needed to include in the custom setting of the xcode install.
- Developers Tools SOftware - gcc 4 - gcc 3.3 Software Dev Kits - Mac OS X SDK - BSD SDK
Comment from bendy on January 24, 2006 4:20:07 PM CST
@bendy: thanks for the tip! I was trying to do a minimal install of XCode too and was having some trouble with GCC. thanks!
Comment from asemisldkfj on February 11, 2007 8:39:23 PM CST
I can't get wget to compile for Tiger. I get the following output:
checking build system type... Invalid configuration `unknown-apple-darwin8.0.0': machine `unknown-apple' not recognized
configure: error: /bin/sh ./config.sub unknown-apple-darwin8.0.0 failed
Any suggestions?
Thanks!
Comment from Anonymous on September 21, 2005 6:45:15 PM CDT
For those that are having trouble building wget, you might want to use curl instead. Not sure about releases prior to 10.4, but it is defintely included by default in 10.4.x if you installed the BSD subsystem. For more information, open a terminal and type 'man curl'.
-digitalshadow
Comment from Anonymous on September 30, 2005 1:14:57 AM CDT
Hi I have just built wget for Tiger. You just have to use newest updates and dev-tools and everything works fine!!
Comment from moritz on October 7, 2005 7:35:56 PM CDT
wget is up to 1.10.1 now
Comment from Anonymous on October 11, 2005 6:45:49 AM CDT
I am not sure if this is the place to post this, but considering wget isn't included in OSX or xCode Dev Tools, are there other UNIX commands omitted from the installs that one might expect are included but are not? Thanks.
Comment from Anonymous on October 17, 2005 4:25:41 PM CDT
I didn't expect wget to be installed to begin with. I think the first time I've seen it bundled with any OS distro is after RedHat 6 or 7. Especially now that curl is included, wget will probably be depricated at some point.
What other apps did you have in mind?
Comment from brad. on October 17, 2005 5:44:51 PM CDT
ownage thanks a ton sir, just built 1.10 in like a minute with tiger!
Comment from hammackj on October 30, 2005 2:12:53 PM CST
Thank you.
Comment from Anonymous on November 2, 2005 7:37:02 AM CST
I compiled wget 1.10.2 under Tiger 10.4.3 with no trouble at all. However, it doesn't provide the feature I need, so I'm sticking to curl.
-----
Check out the BARTsmart BART Widget for Mac OS X, featuring BART train schedules and news.
-----
Check out the BARTsmart BART Widget for Mac OS X, featuring BART train schedules and news.
Comment from craigtheguru on November 2, 2005 2:39:45 PM CST
I can almost get this to work, but when calling
sudo make install
it says "sudo: must be setuid root"
What does that mean and what might I need to do?
Comment from Eli on November 5, 2005 7:36:18 PM CST
it's working fine on 10.4.3 with Xcode/Developer Tools (gcc) installed.
Comment from Anonymous on November 24, 2005 12:54:02 PM CST
Has anyone tried building a newer version of wget (> v1.9)?
Comment from Anonymous on January 14, 2006 8:32:40 PM CST
Yep! Works great. Thanks.
Just built 1.10.1 on Tiger 10.4.4.
So simple
Comment from Anonymous on March 4, 2006 8:08:36 AM CST
Comment from l on February 10, 2006 10:25:25 PM CST
Try Fink Commander
Just three clicks and there it is....
Comment from Anonymous on February 20, 2006 9:49:07 AM CST
thank you very much for this bit info. this worked great OS X 10.3.9.
your build instructions and this $PATH tid-bit is what was needed for a successful install.
Put /usr/local/bin in your .bash_profile (this is assuming that you're using the bash shell). 1. Create a .bash_profile file (if you don't already have one). You can either 'touch .bash_profile' or use any text editor to do it. 2. Edit the path so that it reads "PATH=$PATH:/usr/local/bin". 3. Make sure that the PATH variable is exported. On another line, add "export PATH". You can now "source .bash_profile" to get it working with the current terminal. Now every time you start the terminal, /usr/local/bin will be in the path.
Comment from Anonymous on March 4, 2006 9:48:52 AM CST
For this project and any other UNIX source project, I get on an intel Mac this error message:
>>>
configuring for GNU Wget 1.9
checking build system type... i386-apple-darwin8.5.1
checking host system type... i386-apple-darwin8.5.1
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... gcc
checking for C compiler default output... configure: error: C compiler cannot create executables
See `config.log' for more details.
>>>
I'm lost. Don't know, why I can't any longer compile from the command line...
And ideas?
CU,
s
>>>
configuring for GNU Wget 1.9
checking build system type... i386-apple-darwin8.5.1
checking host system type... i386-apple-darwin8.5.1
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... gcc
checking for C compiler default output... configure: error: C compiler cannot create executables
See `config.log' for more details.
>>>
I'm lost. Don't know, why I can't any longer compile from the command line...
And ideas?
CU,
s
Comment from Anonymous on March 15, 2006 1:28:31 PM CST
Currently it's ftp://ftp.gnu.org/pub/gnu/wget/wget-1.10.2.tar.gz
It just compiled fine on 10.4.5
Comment from Skeeve on March 26, 2006 2:45:01 PM CST
Thanks, Bear! (And everyone else who had trouble with the $PATH stuff - I don't have bash installed on this laptop)
And thanks to Anonymous who posted the symlink directions (sudo ln -s /usr/local/bin/wget wget) - On my birthday last year, no less! :)
Comment from Sam on March 28, 2006 3:16:45 PM CST
It works also perfectly on OSX 10.4.6
with developer tools Xcode 2.1
with developer tools Xcode 2.1
Comment from Zervaz on June 8, 2006 9:10:38 AM CDT
perfect! Thanks!
Comment from Luke on June 27, 2006 12:06:00 PM CDT
Thanks! This is exactly what I needed -- quick and with directions that worked.
Comment from Anonymous on July 22, 2006 1:04:52 PM CDT
Thank you! A year and a half after your post, you're still serving the community :) I've been using Linux for over ten years, but am still figuring out Mac OS X, esp. when/how behavior matches or differs from Linux. Your post helped.
Comment from Ed on September 11, 2006 5:47:34 PM CDT
I got it to build and install on OS X 10.4.8, and to place the man pages in the proper location:
./configure --mandir=/usr/local/share/man make make install
Comment from Shlomo Swidler on December 10, 2006 7:57:03 AM CST
This is awesome! Thanks a ton!
Comment from Andrew M. on January 7, 2007 4:00:45 AM CST
Thanks, Shlomo! That's exactly what I was wondering.
I noticed a lot of other installers have put manpages in /usr/local/man too. How can I add that directory to my manpath? Or should I just move all that stuff to /usr/share/man?
Shlomo Swidler wrote:
> I got it to build and install on OS X 10.4.8, and to place the man pages in the proper location
Comment from Immanuel Tranz-Mischen on January 11, 2007 6:38:18 PM CST
THANK YOU for the blog! It TOTALLY helped me to get.. wget working on my MacOSX 10.4.8. I had made some common errors: not a full install of the -proper- Dev Tools (I had an old disk, so then I downloaded the latest after that to be able to compile), and also I had to do a "symlink with sudo ln -s /usr/local/bin/wget wget to get it to run" --as did the other poster above. I'm a happy camper, thanks to Bear and you dudes here.
ps. I had cURL recommended to me too, but I have scripts all setup for wget, which I also script through. WGET is my champ.
PEACE, Pix :.
ps. I had cURL recommended to me too, but I have scripts all setup for wget, which I also script through. WGET is my champ.
PEACE, Pix :.
Comment from PIX on February 6, 2007 10:41:58 PM CST
The man page issue is a matter of OS X by default not including /usr/local/man in the MANPATH. To fix for all users simply "sudo vi /usr/share/misc/man.conf" and add "MANPATH /usr/local/man" to the line following "MANPATH /usr/local/share/man".
Comment from Anonymous on February 13, 2007 9:07:01 PM CST
Check this out: After going to the trouble of installing all the new XCode/GCC/etc.. on my MacOSX 10.4.8 and building/compiling WGET.. I found I could just copy the executable to run on my 10.3 OSX.. no problemo. Not sure if it's 10.3 or a 10.2 upgraded to 10.3, but the proper directory was /usr/bin on the older OSX.
Comment from PIX on February 15, 2007 11:31:14 PM CST
configure --infodir=/usr/share/info --mandir=/usr/share/man --bindir=/usr/bin --sysconfdir=/etc; make; sudo make installalso works. You don't need to change any configuration file, environment variable, symbolic link...
Comment from cesarse on May 13, 2007 10:42:19 AM CDT
I'm using OS X Version 10.4.9 and everything went smooth. I have the developer tools installed.
Thanks for the info!
Comment from HC on May 24, 2007 12:43:46 PM CDT
Is having XCode installed a pre-requisite?
I don't have Xcode installed and I receive the following error:
GOMacmini:~/SafariDLs/wget-1.9 go$ ./configure
configuring for GNU Wget 1.9
checking build system type... powerpc-apple-darwin8.10.0
checking host system type... powerpc-apple-darwin8.10.0
checking whether make sets $(MAKE)... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... no
checking for cc... no
checking for cc... no
checking for cl... no
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.
Comment from GO on October 23, 2007 7:43:10 AM CDT
You don't need Xcode per se, but you do need the C compiler. I'm pretty sure that you need to install the Dev Tools (which includes Xcode) to get that.
I always automatically install the dev tools after an OS install, so I'm not sure what comes with the OS and what comes with the dev tools.
Comment from Bear on October 23, 2007 10:45:00 AM CDT
Actually, i compiled it like this:
./configure --prefix=/usr
make
sudo make install
No problems with $PATH at all :) (I compile stuff all the time on Linux)
Comment from SeySayux on March 17, 2008 6:13:32 AM CDT
TrackBack to http://radio.javaranch.com/bear/addTrackBack.action?entry=1109829480523