Re: [ALUG] Where do I put source files?
On Saturday 13 March 2004 13:51, Chris Walker wrote:
On Sat 13 Mar, MJ Ray wrote:
On 2004-03-13 10:20:01 +0000 Chris Walker
<linux@wymondham.demon.co.uk> wrote:
I've never compiled anything before, I don't know where to put this stuff.
Generally, whereever you want.
OK.
Unpack it (tar xzf filename.tar.gz usually) and read the INSTALL file. (If it doesn't have one, report a bug.) Some people like to put it under /opt/src, some under /usr/local/src or /usr/src and some in a subdirectory of their home. I've even got one system with sources in /Depot/Compile/Sources...
It does have an INSTALL file but it didn't give the location that I wanted.
Apologies if this has already been said, but most source packages adhere to the following installation procedure. 1. cd to the directory where you have unpacked the source 2. type ./configure this runs the configure script which does a huge bunch of checks to try to make sure the compile will be successful. It should tell you for example if any libraries are missing. It is usually possible to pass arguments to configure to tell it where you want files to be put. configure creates (amongst other things) a makefile which tells the compiler how to build the programme from the source. 3. type ./make this compiles the programme and should result in an exectuable 4 type ./make install this installs the executable and any other necessary files in predetermined directories. HTH Ian
On Sat, Mar 13, 2004 at 10:11:17PM +0000, IanBell wrote:
3. type ./make this compiles the programme and should result in an exectuable
4 type ./make install this installs the executable and any other necessary files in predetermined directories.
I think you mean "make" and not "./make". Including the dot and slash, "./", will make the shell try to run "make" from the current working directory, and not search $PATH for it. Wayne.
On Saturday 13 March 2004 23:32, Wayne Cornish wrote:
On Sat, Mar 13, 2004 at 10:11:17PM +0000, IanBell wrote:
3. type ./make this compiles the programme and should result in an exectuable
4 type ./make install this installs the executable and any other necessary files in predetermined directories.
I think you mean "make" and not "./make". Including the dot and slash, "./", will make the shell try to run "make" from the current working directory, and not search $PATH for it.
Wayne.
Whoops, quite right Wayne. Ian
On Sunday 14 March 2004 07:36, IanBell wrote:
On Saturday 13 March 2004 23:32, Wayne Cornish wrote:
On Sat, Mar 13, 2004 at 10:11:17PM +0000, IanBell wrote:
3. type ./make this compiles the programme and should result in an exectuable
4 type ./make install this installs the executable and any other necessary files in predetermined directories.
I think you mean "make" and not "./make". Including the dot and slash, "./", will make the shell try to run "make" from the current working directory, and not search $PATH for it.
Wayne.
Whoops, quite right Wayne.
Ian
And re the "make install"; it's often necessary to be root, so do su -m first. The plain su resets environment variables but -m keeps you in the same directory and with your environment variables unchanged, only with root privileges. This is useful if you need to run programs that aren't on the system path, such as kwrite. Most packages will complain if they needed to be installed as root. -- GT
On Sunday 14 March 2004 11:46, Graham Trott wrote:
On Sunday 14 March 2004 07:36, IanBell wrote:
On Saturday 13 March 2004 23:32, Wayne Cornish wrote:
On Sat, Mar 13, 2004 at 10:11:17PM +0000, IanBell wrote:
3. type ./make this compiles the programme and should result in an exectuable
4 type ./make install this installs the executable and any other necessary files in predetermined directories.
I think you mean "make" and not "./make". Including the dot and slash, "./", will make the shell try to run "make" from the current working directory, and not search $PATH for it.
Wayne.
Whoops, quite right Wayne.
Ian
And re the "make install"; it's often necessary to be root, so do
su -m
first. The plain su resets environment variables but -m keeps you in the same directory and with your environment variables unchanged, only with root privileges. This is useful if you need to run programs that aren't on the system path, such as kwrite.
Most packages will complain if they needed to be installed as root.
-- GT
Whoops another booboo on my part. In my experience virtually all packages need root privilidges to iinstall because the executable is normaly placed somewehre under /usr (to which non root users cannot write). So, unless you intend to install files in your home directory, you will need to be root. As an aside, this process is usually described in the readme or install file of the source. it is always worth reading these both before compiling just in case there are some oddities (and there often are). Ian
- hey all - i am a complete n00b to linux as i am just starting to get into it, i was at the last meeting though at the city gate pub - i need to install my win modem 56k, i have the drivers, but i need to direct the make file to my kernel dir, i have done that run the make file and says that kernel dir dosent exist, - any ideas, and anyone with suse what is the path to your kernel dir, mine is, lib/modules/-version-/kernel cheers Mosez
On Sunday 14 March 2004 10:26, Daniel Mowday wrote:
- hey all - i am a complete n00b to linux as i am just starting to get into it, i was at the last meeting though at the city gate pub
- i need to install my win modem 56k, i have the drivers, but i need to direct the make file to my kernel dir, i have done that run the make file and says that kernel dir dosent exist,
- any ideas, and anyone with suse what is the path to your kernel dir, mine is, lib/modules/-version-/kernel
cheers Mosez
Normal these drivers need to know the path to the kernel source, not the kernel itself, in order for the make to compile the code against your kernel. So first I would suggest you make sure you have the kernel source installed. Ian
On 2004-03-14 10:26:16 +0000 Daniel Mowday <elitemenace@hotmail.com> wrote:
- i am a complete n00b to linux as i am just starting to get into it, i was at the last meeting though at the city gate pub [...]
Congratulations!
- any ideas, and anyone with suse what is the path to your kernel dir, mine is, lib/modules/-version-/kernel
I think most packages will install it under /usr/src/linux, but I don't know SuSE very well (ask me why at a meeting ;-) ). -- MJR/slef My Opinion Only and possibly not of any group I know. Please http://remember.to/edit_messages on lists to be sure I read http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef@jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/
On 2004-03-13 22:11:17 +0000 IanBell <ian@redtommo.com> wrote:
Apologies if this has already been said, but most source packages adhere to the following installation procedure.
Things with configure normally have an INSTALL starting "These are generic installation instructions" or similar.
1. cd to the directory where you have unpacked the source 2. type ./configure [...]
"./configure --help" will tell you what options are possible. -- MJR/slef My Opinion Only and possibly not of any group I know. Please http://remember.to/edit_messages on lists to be sure I read http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef@jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/
participants (5)
-
Daniel Mowday -
Graham Trott -
IanBell -
id＠nooped.com -
MJ Ray