3 Replies Latest reply: Feb 12, 2013 6:32 AM by BobHarris
Tundo Level 1 Level 1 (0 points)

hi there!

when i comiple tar.gz packages i usally install it by this way:

 

  cd smartmontools-6.0
  ./configure
  make
  sudo make install

 

everythink ok but when i prompt:

 

smartctl /dev/disk1s2

 

i see the error: command not found

whats wrong? i googled it up and it seems that the command isnt in the system path but cant find to fix it!

 

is a smartctl specific problem or after compiling/install am i missing something?

 

thanks

Enrico

 

(osx: 10.8.2)


iMac 27" i5 quad 2010, Mac OS X (10.6.7), 4gb ram, 1Tb hdd
  • 1. Re: compile smartmontools pkg from terminal: command not found
    g_wolfman Level 4 Level 4 (1,120 points)

    Where does "make install" install the binary to, exactly, and is that directory in your path?  /usr/local/bin is usually the default location for third-party CLI utilities, and it is often not in the default path.

  • 2. Re: compile smartmontools pkg from terminal: command not found
    Tundo Level 1 Level 1 (0 points)

    hi thakns for reply,

    binaries are in "/usr/local/sbin"

    so i added it to the default path folloing this:

    http://www.tech-recipes.com/rx/2621/os_x_change_path_environment_variable/

     

    ....i thougth make install could do itself

  • 3. Re: compile smartmontools pkg from terminal: command not found
    BobHarris Level 6 Level 6 (13,120 points)

    Open Source installers DO NOT mess with individual user shell initialization scripts.  Open Source project may be installed on single user systems, or multi-user systems so to update every possible user's shell initialization files becomes a nightmare.   For example which accounts should be updated, and which are daemon accounts that should be left along.  Which shell does the user of each account prefer to use?  And for some shells, there are multiple different shell initialzation files, so which one does the shell initialzation file select.  And if the user already has a PATH environment variable in a shell initializaton file that gets executed AFTER the file the installer choose (.bash_profile vs .bashrc), then all the installers work would be for nothing, and worse confuse the user. And the user already has the directory in PATH, but they are not logged in, does the installer parse all the other user's shell initialzation files to figure out if that user does not need an update PATH, or does it blindly add yet another export PATH to one of the shell initialization files?

     

    Open Source installers worry about the getting the app built and installed.  It leaves the user's personal files alone, for very good reasons :-)