\n"; // Echo "RootDir: ".$RootDir."
\n"; // We'll need access to the Global Variables: // include_once("$DOCUMENT_ROOT/include/GlobalVars.php"); // To get rid of: Warning: include_once() [function.include-once]: Unable to access /include/GlobalVars.php in include_once("$RootDir/include/GlobalVars.php"); // We will be accessing all sorts of functions: //include_once("$DOCUMENT_ROOT/include/Functs.php"); include_once("$RootDir/include/Functs.php"); // Check to see if the visitor (USER_AGENT) is a spider. If not: // then do a "session_start"... // Creates a session or resumes the current one // based on the current session id that's being passed via a // request, such as GET, POST, or a COOKIE. // It's necessary that this be the first PHP command in the file. If (!ItsASpider()) { session_start(); // Sets various session variables like ReferringURL and EntryURL // if they haven't already been set // include_once("$DOCUMENT_ROOT/include/SetSessionVars.php"); include_once("$RootDir/include/SetSessionVars.php"); } // This turns on Output Buffering. This seems to be // necessary because we may be redirecting to a "Thank You" page // after they submit the form. Speeds things up because // browser doesn't reload when hitting BACK button. ob_start(); // PageNameStr - This is the dominant keyword phrase for the page. // Goes in comments, header bars, IMAGE ALT tags, etc. Only about 10 words! $PageNameStr="'make install' fails, dies, quits on FreeBSD"; // This is the first line string. It goes at the very top of the page. // If this is NOT a doorway page, then set the $PageFirstLineStr: // Notice: Undefined variable: ThisIsDoorway // IF (!($ThisIsDoorway)) // If not set, then set it to get rid of error message: If (!IsSet($ThisIsDoorway)) {$ThisIsDoorway=0;} If ($ThisIsDoorway<>1) {$PageFirstLineStr="FreeBSD 'make install' Fails - Installing Programs Apps - Dies, Fails, Quits, Error Code - Tutorial, Howto, Newbie, Beginner, Tips, Tricks, Hints";} // This is the first text after the first line, // that usually shows up in the upper left corner $PageFirstTextStr="${CompanyStr}

FreeBSD make install dies"; // This is the second text after the first line, // that usually shows up in the upper right corner $PageSecondTextStr="${CompanyDomain}

'make install on FreeBSD fails"; $PageTitleStr=$PageFirstLineStr; $PageKeywordStr=$PageNameStr; $PageCommentStr="'make install' on FreeBSD quits. Dies, crashes, fails, Error Code 1. Configuration, Linux, Unix, Nix, Cheat Sheet for FreeBSD Installation. Configure, Options, Configuration, Howto, How To, FreeBSD."; // $PageDescriptionStr=""; // $PageRobotsStr=""; // If this is NOT a doorway page, then include header.php: IF (!($ThisIsDoorway)) { include_once("$RootDir/include/header-brief.php"); } ?>

MAKE INSTALL DIES ON FREEBSD


    ASSUMPTIONS:

  1. You have already installed FreeBSD.  If not, then click here: How to Install FreeBSD

  2. You have configured the FreeBSD shell.  If not, then click here: How to Configure the FreeBSD Shell

  3. Your 'ports tree' is up to date.  If you don't know, then it probably isn't current.  Update the ports tree by issuing one of these commands: Update the Ports Tree Using CVSup

  4. Here is how to configure your computer so that CVSup is run on a regular basis


    COMMENTS:

    FreeBSD has advantages over other operating systems, one of which is the built-in dependency tracking of the 'ports system'.  What this means is that when you install a port:

    cd /usr/ports/SomeCategory/SomePort/
    make install
    while constructing and installing the 'SomePort' program, FreeBSD automatically also makes and installs any and all programs that 'SomePort' depends on for its operation.  At least that's the way that it is supposed to work.


    PROBLEMS WITH 'MAKE INSTALL'

    When it doesn't, you will usually see a number of errors output to the screen.  The most important one is the FIRST instance of:

    *** Error code 1
  5. Look just before this FIRST instance, and you will see some sort of reference to a program.  (By the way, if the 'Error code' number is something other than '1', it is likely that there is a problem inside the code, rather than it being a simple problem that is easy to fix.  Try the following steps in any case.)  Odds are this program has one of these problems:

    A. Isn't installed
    B. Older (or newer) version than is required.
    C. Installed incorrectly

    IS DEPENDENT PROGRAM INSTALLED?

  6. First, determine if the program is installed. To do this enter:

    pkg_info  |  more
    (The pipe character '|' is probably located on your keyboard as the shifted version of the '\' key).

    (The 'more' command after the pipe character tells the computer to only show a page of data at a time.  In order to see other pages, use the 'Pg Dn', 'Pg Up', 'Enter' keys, space bar, or arrow keys.)

  7. Look closely at all of the listings to find your 'SomePort'.  You should notice that the programs will be listed with their version numbers like so:

    ispell-3.2.06_11

  8. If you do NOT see the dependent program listed, it is probably not installed.  In this case, try to install it.  (If the program IS installed, CLICK HERE to jump past the install steps.)

  9. Before you can install it, you need to find out where it resides.  The 'locate' program is good for that.  Enter something similar to:

    locate someprogram | more
  10. If that doesn't work, perhaps try the whereis or find commands:

    whereis someprogram | more

    find / -name "someprogram*"
  11. Look for the location of the appropriate file.  It will start with /usr/ports/.  You may need to reissue the 'locate' command if there are a number of listings and you can't find it on the first pass through.

  12. Next, as appropriate, change to the directory and install:

    cd /usr/ports/SomeCategory/SomeDependentPort/
    make install
  13. If everything goes OK, you should see a notice that the program has been installed.  You should NOT see any error messages.  Click here to jump past the next section since everything went OK.

    If there are errors, then you will need to 'deinstall', then 'reinstall'.  These steps are next:


    DEPENDENT PROGRAM IS INSTALLED: DEINSTALL, REINSTALL

    If the program is installed, but it isn't working, we will need to deinstall it, then reinstall it.  First, travel to its directory:

    cd /usr/ports/SomeCategory/SomeDependentPort/
  14. Next, enter:

    make deinstall
    Wait until it finishes.

  15. Now enter:

    make reinstall
    Once it has finished, it should give you some sort of message that it reinstalled properly.

  16. At this point, either we have either installed or reinstalled the dependent port.  So, let's go back and try again to install the original program:

    cd /usr/ports/SomeCategory/SomePort/
    make install


    CONSULT THE FREEBSD MAILING LIST

  17. If this procedure of manually installing programs doesn't seem to work, it's time to ask the experts.  There is a mailing list set up for just these types of problems.  It's called 'FreeBSD-Questions'.  By searching this list, you are likely to find an immediate answer to the problem you are having.  There are a number of sites that archive the FreeBSD-Questions mailing list, but Mail-Archive.com seems to be the most convenient, since it arranges the postings by subject.  Just type in your relevant search terms in the search box:

    Click here to visit the archive of FreeBSD-Questions at Mail-Archive.com.

  18. If a search of the archives doesn't give you the answer you need, you can contact FreeBSD-Questions directly.  There are two ways to subscribe to the mailing list.

    Firstly, you can subscribe via the Web:
    http://lists.FreeBSD.org/mailman/listinfo/freebsd-questions

    Or, you can subscribe using email:
    FreeBSD-Questions-Request@FreeBSD.org?subject=subscribe