LinuxSA Mailing list archives

  From: Andreja Zivkovic <andy@zt.zivkotech.net.au>
  To  : Andrew O'Callaghan" <androc@box.net.au>, "Craig Mann <androc@box.net.au>
  Date: Mon, 7 Feb 2000 08:05:44 +1030

RE: Aureal Drivers, Make command.

Actually, I beleive he ment you have to be root to do 'make install',
because it writes to directories that only root has write access to. make
should be available to all users, so they can write their own programs, so
executing make should not be a problem, since /usr/bin is normally in the
path on most systems.

Anyway, to Craig Mann, who was the person who posted the first message:
try doing a "make" or "make all" before trying "make install". I looked at
the readme file in the driver tar.gz, and it's hopeless. It says to install
the driver, do a "make install", but it forgets to tell you that the driver
must exist before you can install it! To build the driver, you should need
to only do a "make", but that depends on how they made the Makefile.

If the help you have received is not enough to help you, may I ask you to
tell us what commands you entered and what error messages you get, so we can
be more certain to what the problem is.

Good luck,
Andy

> -----Original Message-----
> From: Andrew O'Callaghan [mailto:androc@box.net.au]
> Sent: Monday, 7 February 2000 1:15 AM
> To: Craig Mann
> Cc: linuxsa@linuxsa.org.au
> Subject: Re: Aureal Drivers, Make command.
>
>
> Hi Craig,
> as Damien also replied, if you are root, then you will be able to
> run the make
> program. However, you do not HAVE to be root to run it. It
> depends on where you
> are doing the installing and compiling.
>
> The way it boils down is this:
> - when a user logs in, they open a shell which communicates with
> the operating
> system kernel.
>
> - depending on the shell the user is running, a hidden 'rc' file
> will be run when the
> shell is initiated. If the user is running bash, this file will
> be called .bashrc and
> should be located in the user's home directory. If the file
> doesn't exist, you can
> create it with your favourite editor.
>
> - a user can run more than one shell that connects with the
> kernel, ie. each xterm
> that is opened is running a shell that is connected to the
> kernel. Each shell has
> a range of environment variables, that can be viewed by typing
> 'env' at the command prompt
> of that shell. One of the variables is called PATH, and looks
> something like this:
>
> PATH=/usr/bin:/bin:/usr/X11R6/bin:/usr/local/bin:/opt/bin:/usr/X11R6/bin
>
> - the PATH environment variable is used by the kernel to look in
> the directories specified
> in the PATH variable (separated by colons ':') for any of the
> commands you type at the command
> prompt.
>
> - you can add directories to your PATH variable by specifying
> them in the .bashrc file (if
> using bash), ie. you would have a line like the following:
>
> export PATH=$PATH:/usr/bin
>
> - this line means  you wish to add the path '/usr/bin' to
> whatever is already specified by
> the PATH variable.
>
> As Damien said, if you type whereis make, the whereis command
> will find the location that
> the make command is located in. Another command you could type is
> which make, which would
> try and find the make command in the paths specified in your
> shell's PATH env variable.
>
>
> Your problem depends on what error messages you get back after
> typing make install. If
> you get something along the lines of:
> unable to install in drectory xxx
>
> then the problem is probably that you should be doing the install
> as root, as only root has
> access to some of the directories (like /usr/bin). If you get
> something like:
> command not found
>
> then the problem is probably one to do with the PATH variable.
>
> Hope this helps, and apologies for the verbosity,
>
> regards,
> Andrew O'C