Find the answer to your Linux question:
Page 3 of 3 FirstFirst 1 2 3
Results 21 to 25 of 25
Morning Kern, Thanks for getting back to me. I rebuilt the box this morning, and installed the latest 2.6.16.16 kernel stuff using your method that was described above, although i ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #21
    Just Joined!
    Join Date
    Jun 2006
    Posts
    49

    Morning Kern,

    Thanks for getting back to me.

    I rebuilt the box this morning, and installed the latest 2.6.16.16 kernel stuff using your method that was described above, although i noticed we hadn't added the 2.6 Headers in last time, so i installed the header package.

    Everything now appears to be working without fault.

    Thanks again for all your help.

    Rob

  2. #22
    Linux Enthusiast
    Join Date
    Jun 2005
    Posts
    668
    You rebuilt it again? why?

    anyway

    you need the kernel headers your GLIBC was compiled _for_

    and that is the 2.4 headers package, not the 2.6


  3. #23
    Just Joined!
    Join Date
    Jun 2006
    Posts
    49
    Oh really?

    I've been complining packages all afternoon with the 2.6 headers installed and its been as good as gold, everything is running super fast and not had a single glitch all day, strange.

    I did decide to rebuild again, after spending some time fiddling yesterday I had half complied packages all over the shop so decided to do a clean build so i could be sure there wasnt anything conflicting.

    Rob

  4. #24
    Linux Enthusiast
    Join Date
    Jun 2005
    Posts
    668
    When you compile programs, never use the 'make install' target

    install the 'checkinstall' application, you can find the package in extra/

    configure your new program as so
    Code:
    ./configure --prefix=/usr/local --localstatedir=/var 
    make
    checkinstall -ss
    notice you do not do make install, checkinstall will build a package for you, it'll install it too, and leave a package you can copy to a packages dir which you can use again, you can then use installpkg to install the package, or removepkg to remove the package

    build the libraries the app depends on , make them into packages, install the packages, then build the app, and install that as a package too, this makes it very easy to remove the software afterwards.

    if you use make install all the time it is impossible to pry the software out afterwards, and you'll find yourself rebuilding the box all the time just to keep it fresh.

    may I recommend this too?

    www.slackbook.org , a great resource

  5. #25
    Just Joined!
    Join Date
    Jun 2006
    Posts
    49
    You may indeed reccomend the slack book, thanks Kern.

    I've been making a habbit of creating all my own packages and then installing those rather that actualy installing the programs from binary's.

    Luckily i've found the larger majority of what i require allready compiled on www.linuxpackages.net which has also been very helpfull to me.

    Thanks again for all your help Kern, i couldnt have managed it without your advice.

    Rob

Page 3 of 3 FirstFirst 1 2 3

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •