Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Getting it to work...' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Getting it to work...
Authored by: Supernova on Apr 02, '02 02:55:54AM
Ummm... I ran ./configure and make , but I didn't get it installed. Help?

( make install returned errors, but I don't know if I was actually supposed to run this - it listed it in the readme, but it was talking about straight linux).

Thanks

[ Reply to This | # ]
no man page
Authored by: macubergeek on Apr 02, '02 05:40:16AM

installed just fine but no man page installed though.
I have both Dev tools and Darwin tools installed though. Darwin tools gives you additional header files. Using both really helps compiling.



[ Reply to This | # ]
Getting it to work...
Authored by: sekalreed on Apr 02, '02 09:27:11AM

Try this:
./configure
make
sudo make install

You need the sudo because it has to install the binary in /usr/local/bin/ and the man page in /usr/local/man/man8/ which should be only accessible if you're an admin. It compiled and ran fine on 10.1.3 with the December Dev Tools.



[ Reply to This | # ]
Getting it to work...
Authored by: babbage on Apr 02, '02 10:11:39AM
The standard build-from-source procedure for most Free/Open software is, once you've downloaded & unzipped/unpacked the source:
./configure
make
make test
sudo make install

There are often parameters you can feed to the configure script -- try adding a "--help" to see what ones are available, then substitute the first line with the customized version like, say (making this up)

./configure --help
./configure --prefix=/usr/local --datadir=/var/dat/pkg --with-x
make
make test
sudo make install

Flags like the above would tell the system where to place the program, where it's datafiles should go, and should enable X-Windows support. Once configure finishes, it creates some customized scripts that drive the rest of the process, and that process is begun with the 'make' command. Once that finishes -- and it can take a while -- then run 'make test' to verify that no errors came up (not all packages include tests, but it's good to run this if you can). If the test step goes well, then apply the package to your system, using superuser privileges, with "sudo make install". Once that finishes, the software is added to your system, and can be used when you open a new terminal (or update your path with the "rehash" command).

[ Reply to This | # ]

Getting it to work...
Authored by: sevenov9 on Apr 04, '02 11:35:09AM

How come when ever I try the make command, it always says "make: *** No targets. Stop."..?



[ Reply to This | # ]