Re: Can't build from source
On Mon, Jun 26, 2006 at 02:28:57AM +1200, Chris Bannister wrote: On Fri, Jun 23, 2006 at 10:51:18AM -0700, Andrew Sackville-West wrote: Lothar says you need autoconf package. I would suggest you may need more than just that. You have to have a complete build environment along with all the dependencies of the particular package you are building. Begin by checking the INSTALL or README files for a list of required dependiencies. Also, I'm sure there is a meta-package for a complete build toolchain, but I don't know and can't readily find it. apt-get install build-essential thanks signature.asc Description: Digital signature
Re: Can't build from source
On Fri, Jun 23, 2006 at 10:51:18AM -0700, Andrew Sackville-West wrote: Lothar says you need autoconf package. I would suggest you may need more than just that. You have to have a complete build environment along with all the dependencies of the particular package you are building. Begin by checking the INSTALL or README files for a list of required dependiencies. Also, I'm sure there is a meta-package for a complete build toolchain, but I don't know and can't readily find it. apt-get install build-essential -- Chris. == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Can't build from source
Hi Lawrence, On Fri, 2006-06-23 at 15:49 +0800, Lawrence Li wrote: When trying to compile from source, I follow these steps: # tar xvzf package.tar.gz (or tar xvjf package.tar.bz2) # cd package # ./configure # make # make install But somehow I always ended up stuck at ./configure or make. The error msg for the former is usually No such file or directory, while for make, it's usually this: make: *** No targets specified and no makefile found. Stop. Most packets come with a INSTALL and/or README file. One of these files usually describes how to compile and install the program/library. Another program (namely Privoxy) prompted with the following msg when I entered make: To build this program, you must run *** autoheader autoconf ./configure and then run GNU make. *** Shall I do this for you now? (y/n) y So I chose y, only to get a new error msg: /bin/sh: line 1: autoheader: command not found Autoheader comes with package autoconf. You should install this packet. -- Lothar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Can't build from source
On Fri, Jun 23, 2006 at 03:49:37PM +0800, Lawrence Li wrote: hi list: This is probably newbie question, but I've encountered several obstacles when trying to compile from sources. [...] When trying to compile from source, I follow these steps: # tar xvzf package.tar.gz (or tar xvjf package.tar.bz2) # cd package # ./configure # make # make install But somehow I always ended up stuck at ./configure or make. The error msg for the former is usually No such file or directory, while for make, it's usually this: make: *** No targets specified and no makefile found. Stop. Another program (namely Privoxy) prompted with the following msg when I entered make: To build this program, you must run *** autoheader autoconf ./configure and then run GNU make. *** Shall I do this for you now? (y/n) y So I chose y, only to get a new error msg: /bin/sh: line 1: autoheader: command not found Lothar says you need autoconf package. I would suggest you may need more than just that. You have to have a complete build environment along with all the dependencies of the particular package you are building. Begin by checking the INSTALL or README files for a list of required dependiencies. Also, I'm sure there is a meta-package for a complete build toolchain, but I don't know and can't readily find it. Meanwhile, you may find something like apt-get build-dep package is helpful as it will pull in all the dependencies for a particular package. Also, read the output of ./configure in detail as they usually tell you what you are missing. One by one you can install all the requirements until the tings works. Thankfully, this process gets easier and easier the more you build as you begin to build-up a greater repository of dependencies on your machine. hth A signature.asc Description: Digital signature
Re: Can't build from source
Thanks Andrew, Lothar, I've just installed autoconf, but Lothar is right to say that I need more. I'll look into the README, INSTALL and ./configure outputs. Lawrence On 24/06/06, Andrew Sackville-West [EMAIL PROTECTED] wrote: On Fri, Jun 23, 2006 at 03:49:37PM +0800, Lawrence Li wrote: hi list: This is probably newbie question, but I've encountered several obstacles when trying to compile from sources. [...] When trying to compile from source, I follow these steps: # tar xvzf package.tar.gz (or tar xvjf package.tar.bz2) # cd package # ./configure # make # make install But somehow I always ended up stuck at ./configure or make. The error msg for the former is usually No such file or directory, while for make, it's usually this: make: *** No targets specified and no makefile found. Stop. Another program (namely Privoxy) prompted with the following msg when I entered make: To build this program, you must run *** autoheader autoconf ./configure and then run GNU make. *** Shall I do this for you now? (y/n) y So I chose y, only to get a new error msg: /bin/sh: line 1: autoheader: command not found Lothar says you need autoconf package. I would suggest you may need more than just that. You have to have a complete build environment along with all the dependencies of the particular package you are building. Begin by checking the INSTALL or README files for a list of required dependiencies. Also, I'm sure there is a meta-package for a complete build toolchain, but I don't know and can't readily find it. Meanwhile, you may find something like apt-get build-dep package is helpful as it will pull in all the dependencies for a particular package. Also, read the output of ./configure in detail as they usually tell you what you are missing. One by one you can install all the requirements until the tings works. Thankfully, this process gets easier and easier the more you build as you begin to build-up a greater repository of dependencies on your machine. hth A -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEnCoWaIeIEqwil4YRAhGuAKC7JLVKGNO2VtsIffiPwbJRHrXJGACgzb6/ l94mE4EMZtfrDjXS5a2h73M= =I7TU -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Can't build from source
Thanks Andrew, Lothar, I've just installed autoconf, but Andrew is right to say that I need more. I'll look into the README, INSTALL and ./configure outputs. Lawrence On 24/06/06, Andrew Sackville-West [EMAIL PROTECTED] wrote: On Fri, Jun 23, 2006 at 03:49:37PM +0800, Lawrence Li wrote: hi list: This is probably newbie question, but I've encountered several obstacles when trying to compile from sources. [...] When trying to compile from source, I follow these steps: # tar xvzf package.tar.gz (or tar xvjf package.tar.bz2) # cd package # ./configure # make # make install But somehow I always ended up stuck at ./configure or make. The error msg for the former is usually No such file or directory, while for make, it's usually this: make: *** No targets specified and no makefile found. Stop. Another program (namely Privoxy) prompted with the following msg when I entered make: To build this program, you must run *** autoheader autoconf ./configure and then run GNU make. *** Shall I do this for you now? (y/n) y So I chose y, only to get a new error msg: /bin/sh: line 1: autoheader: command not found Lothar says you need autoconf package. I would suggest you may need more than just that. You have to have a complete build environment along with all the dependencies of the particular package you are building. Begin by checking the INSTALL or README files for a list of required dependiencies. Also, I'm sure there is a meta-package for a complete build toolchain, but I don't know and can't readily find it. Meanwhile, you may find something like apt-get build-dep package is helpful as it will pull in all the dependencies for a particular package. Also, read the output of ./configure in detail as they usually tell you what you are missing. One by one you can install all the requirements until the tings works. Thankfully, this process gets easier and easier the more you build as you begin to build-up a greater repository of dependencies on your machine. hth A -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEnCoWaIeIEqwil4YRAhGuAKC7JLVKGNO2VtsIffiPwbJRHrXJGACgzb6/ l94mE4EMZtfrDjXS5a2h73M= =I7TU -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
