The time now is Tue 21 May 2013, 15:10
All times are UTC - 4 |
| Author |
Message |
oldyeller
Joined: 15 Nov 2011
Posts: 470
Location: Mishawaka IN
|
 Posted: Thu 11 Oct 2012, 19:39 Post subject:
 How to compile tmux? solved
Subject description: with libevent? solved |
|
Hello,
I would like to compile this, but not sure if this can be done on puppy.
To build tmux from a release tarball, do:
$ ./configure && make
$ sudo make install
Can this be done on puppy?
Last edited by oldyeller on Mon 22 Oct 2012, 11:26; edited 2 times in total
|
|
Back to top
|
|
 |
musher0
Joined: 04 Jan 2009
Posts: 2206
Location: Gatineau (Qc), Canada
|
| Posted: Thu 11 Oct 2012, 20:26 Post subject:
|
|
Hi, oldyeller.
You don't need to "sudo" on Puppy, since we're already "root".
The usual sequence under Puppy is:
| Code: | ./configure # also ok: sh configure
make
make install |
This installs the program in /usr/bin or in /usr/local/bin (the usual spot if you don't tweek the "configure" command).
Two refinements of the above line are possible, but mutually exclusive:
1)
| Code: | | make DESTDIR=/your/chosen/path install |
This installs the program in /your/chosen/path with all the necessary subdirs in it. You can then make a pet by issuing
| Code: | cd ProgramDir
cd .. |
# Because, to do this properly, you have to be one level above the directory that contains your program.
| Code: | | dir2pet ProgramDir-VersionNumber |
# the name of the top dir of the program + the v. number (if applicable)
2) Exclusive OR # If you use #1 above don't use this one, and vice versa.
The second refinement is to type
| Code: | | new2dir make install |
# Available only in Puppy.
I hope this helps.
_________________
 "...l'industrie de l'informatique n'aura besoin que de très peu de temps pour ramener l'humanité aux dessins rupestres." (M. Goebbel, Order of the Command Line; [ma trad.])
Last edited by musher0 on Fri 12 Oct 2012, 10:20; edited 1 time in total
|
|
Back to top
|
|
|
musher0
Joined: 04 Jan 2009
Posts: 2206
Location: Gatineau (Qc), Canada
|
| Posted: Thu 11 Oct 2012, 20:27 Post subject:
|
|
[Sorry, "IT" double-posted all by itself...]
_________________
"...l'industrie de l'informatique n'aura besoin que de très peu de temps pour ramener l'humanité aux dessins rupestres." (M. Goebbel, Order of the Command Line; [ma trad.])
|
|
Back to top
|
|
|
oldyeller
Joined: 15 Nov 2011
Posts: 470
Location: Mishawaka IN
|
| Posted: Thu 11 Oct 2012, 20:41 Post subject:
|
|
thanks musherO,
was not sure when I saw sudo, Should have figured that one out.
I will give it a go and see. It also needs another app so will have to download that one and compile that as well.
Learning new things is such FUN!!!
Cheers
|
|
Back to top
|
|
|
muggins
Joined: 20 Jan 2006
Posts: 6660
Location: lisbon
|
| Posted: Fri 12 Oct 2012, 03:40 Post subject:
|
|
Because the default library search path, in puppy, includes /usr/lib but not /usr/local/lib, it's best to run:
| Code: | ./configure --prefix=/usr
make
make DESTDIR=/your/chosen/path install |
|
|
Back to top
|
|
|
musher0
Joined: 04 Jan 2009
Posts: 2206
Location: Gatineau (Qc), Canada
|
| Posted: Fri 12 Oct 2012, 10:16 Post subject:
|
|
| muggins wrote: | Because the default library search path, in puppy, includes /usr/lib but not /usr/local/lib, it's best to run:
| Code: | ./configure --prefix=/usr
make
make DESTDIR=/your/chosen/path install |
|
True.
But if you so choose, you can make libraries in /usr/local/lib visible to your Puppy path by adding the reference to line 3 of file /etc/profile, like so:
| Code: | | LD_LIBRARY_PATH="/lib:/usr/lib:/usr/X11R7/lib:/usr/local/lib:/root/my-applications/lib" |
That way, the one time you forget to add "--prefix=/usr" to your configure line, you'll still have a workable compile of your program. Also, it may be generally handy if you occasionnally download and run *.deb's or *.rpm's that were not specifically compiled with Puppy as the distro.
Just my 2 cents. BFN.
_________________
"...l'industrie de l'informatique n'aura besoin que de très peu de temps pour ramener l'humanité aux dessins rupestres." (M. Goebbel, Order of the Command Line; [ma trad.])
|
|
Back to top
|
|
|
oldyeller
Joined: 15 Nov 2011
Posts: 470
Location: Mishawaka IN
|
| Posted: Fri 12 Oct 2012, 15:32 Post subject:
|
|
Hello,
I also had to download this libevent
These are my options I know that I don't have to do sudo since I am already running as root. It is what follows that I am not sure of. In (blue text)
$ ./configure
$ make
$ make verify # (optional)
$ sudo make install
1. BUILDING AND INSTALLATION (In Depth)
To build libevent, type
$ ./configure && make
(If you got libevent from the git repository, you will
first need to run the included "autogen.sh" script in order to
generate the configure script.)
You can run the regression tests by running
$ make verify
Install as root via
# make install
Before, reporting any problems, please run the regression tests.
To enable the low-level tracing build the library as:
CFLAGS=-DUSE_DEBUG ./configure [...]
Standard configure flags should work. In particular, see:
--disable-shared = Only build static libraries
--prefix = Install all files relative to this directory.
The configure script also supports the following flags:
--enable-gcc-warnings = Enable extra compiler checking with GCC.
--disable-malloc-replacement = Don't let applications replace our memory management functions
--disable-openssl = Disable support for OpenSSL encryption.
--disable-thread-support = Don't support multithreaded environments.
|
|
Back to top
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Compiling
