Visit Our UNIX and Linux User Community

Recompiling and uninstalling existing applications

Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Recompiling and uninstalling existing applications
# 1  
Old 05-01-2012
Recompiling and uninstalling existing applications

Hi everyone,

I'm new-ish to Unix outside of being a basic user in the past. So some background on my experience level when asking this question.

My current laptop, running OS X 10.5, had Apache and PHP installed when I bought it. However I need to recompile these now to add features which weren't included 'out of the box'.

- Do I need to do anything to 'uninstall' these existing versions of the software before the recompile?
- Do I need to delete the binaries/libraries/other directories/etc of a program I am going to be recompiling (if this isn't answered by the above question) or will this automatically be taken care of?
- How can I make sure I don't leave anything 'hanging around' when I do uninstall a program? Or recompile?
- What resources can I read to learn more about all of this and related?


Previous Thread | Next Thread
Test Your Knowledge in Computers #477
Difficulty: Medium
The first hard disk (IBM 350) was developed in 1956 by IBM and had a capacity of 3.75MB.
True or False?

10 More Discussions You Might Find Interesting

1. AIX

Relink without recompiling

Hello, There is a need to link a new dynamic library to a big number of exes. Unfortunately, I cannot recompile/link all these exes against the new library. Is there any way to link an existing executable with the new library? (everything has been compiled using the xlc tool) Thanks (1 Reply)
Discussion started by: geodimo
1 Replies

2. Shell Programming and Scripting

insert pipes for existing and non-existing records

I have a source file like this, L4058S462 34329094 F51010141TK1070000483L4058S462 34329094 0232384840 381892 182 5690 L4058S462 34329094 F51020141FIRST CLEARING, LLC A/C 3432-9094 L4058S462 34329094 F51030141JOHAN HOLMQVIST ... (1 Reply)
Discussion started by: saravanamr
1 Replies

3. Solaris

Add existing user into an existing group

Pre: no gpasswd/adduser there is just usermod can be used, also there is no -a option for usermod. How should I add a user into a group? (4 Replies)
Discussion started by: a2156z
4 Replies

4. Shell Programming and Scripting

folder existing and file existing

I want to look into a folder to see if there are any folders within it. If there are, I need to check inside each folder to see if it contains a .pdf file So If /myserver/myfolder/ contains a folder AND that folder conatins a .pdf file do X Else do Z I may have multiple folders and... (4 Replies)
Discussion started by: crowman
4 Replies

5. Cybersecurity

Uninstalling OpenSSH on Tru64

Hi Can anyone point me to any documentation or can provide instructions on uninstalling OpenSSH (4.7p1) on Tru64 UNIX 5.1a? Thanks (0 Replies)
Discussion started by: sgajraj
0 Replies

6. Solaris

Uninstalling Vendor Software

Hi admins, thanks for community i have installed a software ( it's a specific soft from a specific vendor : i mean it is not a SUN product ). the install was trough a .tar.gz file and with an "install" executable ( so the command was simply #./install ) my pain now is how to uninstall it... (10 Replies)
Discussion started by: hmaiida
10 Replies

7. Debian

Uninstalling programs?

How can I uninstall a program the most efficient way? So that I get rid of all the man pages etc. too? I'm running debian. /Richard (1 Reply)
Discussion started by: riwa
1 Replies

8. UNIX for Advanced & Expert Users

Perl Installing, Uninstalling

I have some problems with mysql, and maybe perl installation faults. I have installed perl by source. I followed default configuration (e.g. ./configure, make, make install). I have installed perl just because it was required for mysql's installation. But now I have some problems. If I will... (8 Replies)
Discussion started by: kisoun
8 Replies

9. AIX

overriding function calls without recompiling

i want to replace the *alloc and free function calls in an existing project with my own functions, to be able to log the adresses etc in a text file. (memoryleak debugging) I think LD_PRELOAD is what i am looking for. That way i could create a Library with my own malloc functions and link them... (1 Reply)
Discussion started by: Lazzar
1 Replies

10. UNIX for Dummies Questions & Answers

Help Uninstalling Linux!

Hello, I have a laptop running Fedora Core 2, and I am trying to wipe it to put on Windows. Even though the CD is listed first in the boot order, it will not boot to the Solaris system disk. How else could I format this laptop? -skeet (4 Replies)
Discussion started by: skeet23
4 Replies
LOG(1)							User Contributed Perl Documentation						    LOG(1)

Apache::Log -- Perl API for Apache Logging Methods Synopsis #in #------------- use Apache::Log; my $s = Apache->server; $s->log_error("server: log_error"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_ERR, 0, "log_serror logging at err level"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_DEBUG, APR::ENOTIME, "debug print"); Apache::Server->log_error("routine warning"); Apache->warn("routine warning"); Apache::warn("routine warning"); Apache::Server->warn("routine warning"); #in a handler #------------ use Apache::Log; sub handler{ my $r = shift; $r->log_error("request: log_error"); $r->warn("whoah!"); my $rlog = $r->log; for my $level qw(emerg alert crit error warn notice info debug) { no strict 'refs'; $rlog->$level($package, "request: $level log level"); } # can use server methods as well my $s = $r->server; $s->log_error("server: log_error"); $r->log_rerror(Apache::LOG_MARK, Apache::LOG_DEBUG, APR::ENOTIME, "in debug"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_INFO, 0, "server info"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_ERR, APR::ENOTIME, "fatal error"); $s->warn('routine server warning'); } Description "Apache::Log" provides the Perl API for Apache logging methods. Constants The following constants (sorted from the most severe level to the least severe) are used in logging methods to specify the log level at which the message should be logged: o "Apache::LOG_EMERG" o "Apache::LOG_ALERT" o "Apache::LOG_CRIT" o "Apache::LOG_ERR" o "Apache::LOG_WARNING" o "Apache::LOG_NOTICE" o "Apache::LOG_INFO" o "Apache::LOG_DEBUG" For example if the current "LogLevel" is set to warning, only messages with log level of the level warning or higher (err, crit, elert and emerg) will be logged. Therefore this: $r->log_rerror(Apache::LOG_MARK, Apache::LOG_WARNING, APR::ENOTIME, "warning!"); will log the message, but this one won't: $r->log_rerror(Apache::LOG_MARK, Apache::LOG_INFO, APR::ENOTIME, "just an info"); It will be logged only if the server log level is set to info or debug. (either in the configuration file or using the "$s->loglevel()" method.) Other constants: o "Apache::LOG_LEVELMASK" used to mask off the level value, to make sure that the log level's value is within the proper bits range. e.g.: $loglevel &= LOG_LEVELMASK; o "Apache::LOG_TOCLIENT" used to give content handlers the option of including the error text in the "ErrorDocument" sent back to the client. When "Apache::LOG_TOCLIENT" is passed to "log_rerror()" the error message will be saved in the $r's notes table, keyed to the string "error-notes", if and only if the severity level of the message is "Apache::LOG_WARNING" or greater and there are no other "error-notes" entry already set in the request record's notes table. Once the "error-notes" entry is set, it is up to the error handler to determine whether this text should be sent back to the client. For example: $r->log_rerror(Apache::LOG_MARK, Apache::LOG_ERR|Apache::LOG_TOCLIENT, APR::ENOTIME, "request log_rerror"); now the log message can be retrieved via: $r->notes->get("error-notes"); Remember that client generated text streams sent back to the client MUST be escaped to prevent CSS attacks. o "Apache::LOG_STARTUP" is set only during the startup. Server Logging Methods "$s->log_error()" $s->log_error(@message); just logs the supplied message. For example: $s->log_error("running low on memory"); "$s->log_serror()" log_serror($file, $line, $level, $status, @message); where: * $file The file in which this function is called * $line The line number on which this function is called * $level The level of this error message * $status The status code from the previous command * @message The log message This function provides a fine control of when the message is logged, gives an access to built-in status codes. For example: $s->log_serror(Apache::LOG_MARK, Apache::LOG_ERR, 0, "log_serror logging at err level"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_DEBUG, APR::ENOTIME, "debug print"); "$s->log()" my $slog = $s->log; returns a handle which can be used to log messages of different level. See the next entry. emerg(), alert(), crit(), error(), warn(), notice(), info(), debug() $s->log->emerg(@message); after getting the log handle with "$s->log", use these methods to control when messages should be logged. For example: my $slog = $s->log; $slog->debug("just ", "some debug info"); $slog->warn(@warnings); $slog->crit("dying"); Request Logging Methods "$r->log_error()" $r->log_error(@message); logs the supplied message (similar to "$s->log_error"). For example: $r->log_error("the request is about to end"); the same as "$s->log_error". "$r->log_rerror()" log_rerror($file, $line, $level, $status, @message); same as "$s->log_rerror". For example: $s->log_rerror(Apache::LOG_MARK, Apache::LOG_ERR, 0, "log_rerror logging at err level"); $s->log_rerror(Apache::LOG_MARK, Apache::LOG_DEBUG, APR::ENOTIME, "debug print"); "$r->log()" my $rlog = $r->log; Similar to "$s->log()" the emerg(), alert(), crit(), error(), warn(), notice(), info(), debug() methods Similar to the server's log functions with the same names. For example: $rlog->debug("just ", "some debug info"); $rlog->warn(@req_warnings); $rlog->crit("dying"); General Functions "Apache::LOG_MARK()" my($file, $line) = Apache::LOG_MARK(); Though looking like a constant, this is a function, which returns a list of two items: "(__FILE__, __LINE__)", i.e. the file and the line where the function was called from. Aliases "$s->warn()" $s->warn(@warnings); is the same as: $s->log_error(Apache::LOG_MARK, Apache::LOG_WARNING, 0, @warnings) For example: $s->warn('routine server warning'); "Apache->warn()" "Apache::warn()" Apache->warn(@warnings); perl v5.8.0 2002-08-14 LOG(1)

Featured Tech Videos