Very newbie question
Narsil
packages, assuming I've got the source code.
It's just one of a long list of things I havent learned to do in
Slackware, but I'll ask about the rest once I get to them.
Lew Pitcher
>Can someone just run through the steps used to compile/install
>packages, assuming I've got the source code.
Typically, source packages come with a README or INSTALL text file describing
the steps necessary to compile and install the package. Read these /first/, then
follow their directions.
In general, most source packages follow the same steps for installation:
cd package-source-directory
./configure
make
make install
the "configure" script checks your system configuration for the required header
files, libraries, and stuff, and builds the appropriate Makefiles to build the
software on your system. You /may/ have to provide parameters to "configure" to
direct it to use your preferred directory structure (i.e. to install in
/usr/local rather than in /usr), but otherwise "configure" runs itself.
Once you've "configure"d the package, you
make
to build the binaries. Sometimes, you also
make test
to test that the built binaries work correctly with known good test cases.
Once you're ready to install, you typically
make install
to actually put the binaries and config files into their proper places.
On Slackware systems, you might want to substitute the "checkinstall" package
builder tool for this step, so that you can uninstall the package if/when you
want to.
Once all these are done, you get the fun of configuring and running the
installed package.
>It's just one of a long list of things I havent learned to do in
>Slackware, but I'll ask about the rest once I get to them.
--
Lew Pitcher
IT Consultant, Enterprise Technology Solutions
Toronto Dominion Bank Financial Group
(Opinions expressed are my own, not my employers')
Two Ravens
Lew Pitcher gave you the definitive answer, however before you get to
installing the new sofware, have you installed checkinstall? Which
relaces the > make install < part of the process.
--
Two Ravens
"...hit the squirrel..."
notbob
> Can someone just run through the steps used to compile/install
> packages, assuming I've got the source code.
Here's the tutorial I learned from.
http://www.justlinux.com/nhf/Software/Compiling_Software.html
nb
MikeyD
Hash: SHA1
> Can someone just run through the steps used to compile/install
> packages, assuming I've got the source code.
>
Sure. The source package is normally a tgz file.
user@darkstar:~$tar xzf someprogram.tar.gz
cd to the folder
user@darkstar:cd someprogram
Check the installation instructions
user@darkstar:~$less INSTALL
Follow these, but generally the procedure will be
user@darkstar:~/someprogram$./configure
you'll see something like
Checking build system type...i686-linux-gnu
Checking for gcc...gcc
Checking for
and so on. Then
user@darkstar:~/someprogram$make
and you'll see a lot of text. It will take some time. Then
user@darkstar:~/someprogram$su
Password:
to become root, then
root@darkstar:/home/user/someprogram#make install
then you should
root@darkstar:/home/user/someprogram#exit
from root to avoid doing something you'll regret (like an rm -R * in /etc)
The program should now be compiled and installed, and you can usually then
delete its directory if you need the space (the important bits have moved
to /usr/local/)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAAu7KseVxKm0DPWERAn8NAJ0YIiGp+ZyWGfCrNR7gStI6koNW8gCg49RS
h6sFrWccR5YOnrD1BveOh+Q=
=Ht4g
-----END PGP SIGNATURE-----
SuperDaemon
MikeyD wrote:
> user@darkstar:~/someprogram$su
> Password:
> to become root, then
> root@darkstar:/home/user/someprogram# make install
It is possible to issue "*checkinstall*" instead of "make install" here. The
big advantage for doing so here is that:
a) You would be making a slackware package with *.tgz extension.
b) It would be much easier to uninstall/remvoe the package (if you don't
like it) for any reasons afterwards.
C) You also could also use kpackage (e.g. in kde) to view the files
associated files with the package.
d) Possibly use swaret to upgrade the package, etc.
Pretty convenient, neat,great deal.
However You'd have to have *checkinstall* installed beforhand; it is not a
Standard Slackware package yet and does not come with Slackware standard
install.
Jan Alboszta
SuperDaemon <Supre...@a.mean.lean.Slackware.box> Napisal:
> However You'd have to have *checkinstall* installed beforhand; it is not
> a Standard Slackware package yet and does not come with Slackware
> standard install.
Checkinstall package is in 'extra' directory on Your favorite
slackware mirror.
pozdr.
Janek
--
Q:Czemu informatycy mylą Boże Narodzenie z Haloween?
A:Ponieważ DEC 25 = OCT 31
anon
> It is possible to issue "*checkinstall*" instead of "make install" here. The
> big advantage for doing so here is that:
> a) You would be making a slackware package with *.tgz extension.
> b) It would be much easier to uninstall/remvoe the package (if you don't
> like it) for any reasons afterwards.
> C) You also could also use kpackage (e.g. in kde) to view the files
> associated files with the package.
> d) Possibly use swaret to upgrade the package, etc.
> Pretty convenient, neat,great deal.
> However You'd have to have *checkinstall* installed beforhand; it is not a
> Standard Slackware package yet and does not come with Slackware standard
> install.
Thanks for the tip, I'll definitely check it out. I could use a program or
six to clean up after my mess (besides rm -r <g>)
skippy1372
This is probably mentioned somewhere else, but usually you want to do
these steps as non-root (your usual account)
./configure
make
and then only do the following as root
make install
(or checkinstall, if you prefer).
It probably doesn't matter, though...
MikeyD
> these steps as non-root (your usual account)
> ./configure
> make
> and then only do the following as root
> make install
> (or checkinstall, if you prefer).
>
> It probably doesn't matter, though...
You'll notice that's what I said (showed user@darkstar for the first few
steps, and then told him to su to do make install)
Narsil
Thanks all. I'm off to start filling up my hard disk. :)
TomN
MikeyD <m_don...@hotmail.com> wrote in message news:<107401769...@echo.uk.clara.net>...
Narsil
The packages I have are tar.gz.tar, rather than just tgz or tar.gz.
Does this mean anything?
Also, I can't get them to unpack from the terminal. I managed to get
them to unpack by using the gui, so is that the same thing, or am I
doing it wrong?
Thirdly, once I have the package untarred(in the gui), I try to run a
file called configure.
I try to run it, by going to the directory, and typing
user@darkstar:./configure
I then get a message saying that I don't have permission to run that
file. So I log in as su, and try again. Still I don't have
permission. Is this something that I can solve with chmod or chown,
and can someone write out a sample of either/both of those, cos even
with the man pages I can't seem to get either to work. I keep getting
error messages, telling me that my syntax is bad.
Thanks again
TomN
Juergen Frieling
> The packages I have are tar.gz.tar, rather than just tgz or tar.gz.
> Does this mean anything?
my Mozilla-Firebird (here at work running on windows) wants to add the
extra '.tar'. Just remove it in the save dialog, or afterwards from the
filename.
> I then get a message saying that I don't have permission to run that
> file. So I log in as su, and try again. Still I don't have
> permission. Is this something that I can solve with chmod or chown,
Seems the script somehow isn't executable - 'chmod +x configure'.
Juergen
MikeyD
Hash: SHA1
> I've run into a problem.
>
> The packages I have are tar.gz.tar, rather than just tgz or tar.gz.
> Does this mean anything?
It most likely means your browser can't handle a mime type of application
tar correctly. Just rename to .tar.gz
>
> Also, I can't get them to unpack from the terminal. I managed to get
> them to unpack by using the gui, so is that the same thing, or am I
> doing it wrong?
Should work the same way, although your problem below suggests it hasn't
worked right. Try stripping the second tar extension and then tar xzf
package.tar.gz again.
>
> Thirdly, once I have the package untarred(in the gui), I try to run a
> file called configure.
>
> I try to run it, by going to the directory, and typing
>
> user@darkstar:./configure
>
> I then get a message saying that I don't have permission to run that
> file. So I log in as su, and try again. Still I don't have
> permission. Is this something that I can solve with chmod or chown,
user@darkstar:chmod 755 configure. Should run then.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFACDeMseVxKm0DPWERAqsdAKCu6HMKKoK9F6XyzgemF66AaTZW5gCfW4Hl
b9ui9tIIkRkrL3gD0jOoe3Y=
=q7ca
-----END PGP SIGNATURE-----
Narsil
ask for help for a while now.
Or at least I can hope....
TomN
MikeyD <m_don...@hotmail.com> wrote in message news:<10742804...@ersa.uk.clara.net>...
John
if you need to do anything specific?
JohnT
Narsil
place.
I had a thought. I remember seeing somewhere it saying that the files
I was looking at were in a read-only file system. Is there some way
of changing that? I think that might be the way forward.
Also, if I'm navigating my files using the gui, not in a terminal, can
I log into root?
John <jta...@ultimate-anonymity.com> wrote in message news:<hzfPb.9519$592....@newssvr22.news.prodigy.com>...
Lew Pitcher
>I can't seen to find any readmes. I may just be looking in the wrong
>place.
/usr/doc/<packagename> for the package-specific readmes
/usr/doc/Linux-HOWTOs for the HOWTO documentation
/usr/doc/Linux-mini-HOWTOs for the "mini" howtos
>I had a thought. I remember seeing somewhere it saying that the files
>I was looking at were in a read-only file system. Is there some way
>of changing that? I think that might be the way forward.
I missed the first part of this thread, so my answer might be a bit off base.
A 'read only' filesystem is one that's been mounted as read-only. For some
filesystems, you can remount the filesystem as read-write, if that's necessary,
but for others (i.e. anything on a read-only medium, like a CDROM) you can't
remount as read-write.
>Also, if I'm navigating my files using the gui, not in a terminal, can
>I log into root?
Yes, most certainly.
>
>
>John <jta...@ultimate-anonymity.com> wrote in message news:<hzfPb.9519$592....@newssvr22.news.prodigy.com>...
>> Narsil wrote:
>> > I've run into a problem.
>> >
>> > The packages I have are tar.gz.tar, rather than just tgz or tar.gz.
>> > Does this mean anything?
>> >
>> > Also, I can't get them to unpack from the terminal. I managed to get
>> > them to unpack by using the gui, so is that the same thing, or am I
>> > doing it wrong?
>> >
>> > Thirdly, once I have the package untarred(in the gui), I try to run a
>> > file called configure.
>> >
>> > I try to run it, by going to the directory, and typing
>> >
>> > user@darkstar:./configure
>> >
>> > I then get a message saying that I don't have permission to run that
>> > file. So I log in as su, and try again. Still I don't have
>> > permission. Is this something that I can solve with chmod or chown,
>> > and can someone write out a sample of either/both of those, cos even
>> > with the man pages I can't seem to get either to work. I keep getting
>> > error messages, telling me that my syntax is bad.
>> >
>> > Thanks again
>> >
>> > TomN
>> Have you read the "readme's" that came with the application to determine
>> if you need to do anything specific?
>>
>> JohnT
--
Narsil
These ideas sound good. How do I do em? Please bear in mind I'm a
real newbie, and so I havent got the first clue how to do pretty much
anything.
I've spent far too long trying to install this package.
Why can't it be simple?
(A frustrated) TomN
MikeyD
> Lew.P...@td.com (Lew Pitcher) wrote in message
> news:<40101f73...@news21.on.aibn.com>...
>
> These ideas sound good. How do I do em? Please bear in mind I'm a
> real newbie, and so I havent got the first clue how to do pretty much
> anything.
>
> I've spent far too long trying to install this package.
>
> Why can't it be simple?
>
It usually is. What's the software? I'll try it myself if it's a reasonably
small download, and tell you how I did it.
Lew Pitcher
> Lew.P...@td.com (Lew Pitcher) wrote in message news:<40101f73...@news21.on.aibn.com>...
>
> These ideas sound good. How do I do em? Please bear in mind I'm a
> real newbie, and so I havent got the first clue how to do pretty much
> anything.
To manually mount a filesystem as read-only, issue the command
mount -r /dev/device /mount/point
It's the -r that causes the filesystem to mount read-only.
Alternatly,
mount -o ro /dev/device /mount/point
It's the "-o ro" that causes the read-only mount here
To automatically mount a filesystem as read-only, update the /etc/fstab
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,user,ro 0 0
It's the "ro" option that causes the read-only mount
To remount a read-only mounted filesystem so that it is read-write, issue the
command
mount -o remount,rw /dev/device /mount/point
or
mount -w -o remount /dev/device /mount/point
> I've spent far too long trying to install this package.
>
> Why can't it be simple?
>
> (A frustrated) TomN
>
>
>
>
>>I missed the first part of this thread, so my answer might be a bit off base.
>>A 'read only' filesystem is one that's been mounted as read-only. For some
>>filesystems, you can remount the filesystem as read-write, if that's necessary,
>>but for others (i.e. anything on a read-only medium, like a CDROM) you can't
>>remount as read-write.
>>
>>
>>>Also, if I'm navigating my files using the gui, not in a terminal, can
>>>I log into root?
>>
>>Yes, most certainly.
>>
>>
>>>
--
Lew Pitcher
Master Codewright and JOAT-in-training
Registered Linux User #112576 (http://counter.li.org/)
Slackware - Because I know what I'm doing.
Narsil
same. I get to the point of running the configure file, usually
doinst.sh, and I find that I can't do it, because I don't have
permission.
So I su, but I still don't have permission....
Thats the main sticking point. I am going to try to remount my
pendrive (which is how I'm getting my files home, to make it
writeable.
Here's to hoping.
TomN
MikeyD <m_don...@hotmail.com> wrote in message news:<10750647...@lotis.uk.clara.net>...
Eef Hartman
> It's any version of mplayer I can find. The problem is always the
> same. I get to the point of running the configure file, usually
> doinst.sh, and I find that I can't do it, because I don't have
> permission.
>
> So I su, but I still don't have permission....
Is it a "user" mounted file system (stick, floppy, cdrom or such)?
If so, use the "-o exec" option in the mount command (as root!) to make
files on them executable (user implies noexec), or have the options in
the /etc/fstab as "user,exec" (in THAT order).
--
********************************************************************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M....@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
********************************************************************
Narsil
I have a new problem now that we've sorted the rights issue.
A friend of mine told me that I could get round the permissions issue
bu typing
sh /dir/file
This worked, but I'm now getting errors saying that the files are
missing.
soemthing like /opt/share/kde/blah/blah I cant remember exactly.
Which is annoying cos I have an /opt from the root directory, and I
have a /packages/opt from where I untarred the tar file. So which one
does it mean? If it's the one just off the root, I have tried to copy
a file t the root dir, but it wouldn't let me, so I can't untar it
there.
So should I put the tar files in a particular place to install stuff?
Or shouldn't it matter?
Mike
<snip>
>
> So should I put the tar files in a particular place to install stuff?
> Or shouldn't it matter?
I have a Download dir in my $HOME
Untar the downloaded tar and cd to the newmade dir and install
with ./configure, /make, su, checkinstall.
--
+++++++++++++++++++++++++++++++++
Mike Slack 9.1
email: micr at zeelandnet dot nl
MikeyD
>
> Which is annoying cos I have an /opt from the root directory, and I
> have a /packages/opt from where I untarred the tar file. So which one
> does it mean? If it's the one just off the root, I have tried to copy
> a file t the root dir, but it wouldn't let me, so I can't untar it
> there.
>
your installation's a bit of a mess really.