Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: Back to Slack...

  1. #11

    Re:Back to Slack...

    Cool... and it really makes sense, I suppose. I will cross my fingers on this one... OH... to see a log of what happened with the conf/make/makeinstall, would I just need to reference the system log, or...? Could I do that, or would I need to add some redirection to the command line, to redirect errors to a file?
    Asus A8V Deluxe Mobo
    AMD Athlon64 X2 4400 -939
    2GB Crucial DDR3200 Dual-Channel
    ATi AiW 9800 Pro 128DDR
    Audigy2 ZS
    Sony DRU-810 DVD+RW DL
    3 x Maxtor MaxLine SATA 160Gb 16Mb Cache
    1 x Maxtor MaxLine SATA 300Gb 16Mb Cache
    1 x Maxtor MaxLine SATA 120Gb 16Mb Cache

  2. #12
    Senior Member
    Join Date
    Nov 2001
    Posts
    304

    Re:Back to Slack...

    Quote Originally Posted by vwgtiturbo
    One more question... if you are running configure/make/makeinstall, and there are errors, does it dump alot of garbage files in the directory (that you need to get rid of before trying again)?
    usually this is the scenario:
    if ./configure breaks, it will tell you what file was missing to make it break, and may include information in a "config.log" file as well.

    if make breaks, it will tell you what file it was compiling when it broke, and tell you what line and what reason... you can try to figure it out from there.

    if make install breaks, most of the time, it's because you need root privs to install it to the given directory... so do a "sudo make install" instead (assuming you use sudo) OR "su" to root, then "make install"

  3. #13

    Re:Back to Slack...

    What dictates where a program is installed, via make install? I am just curious because let's say I install something as root, but want to make it available to other users. I am guessing that the install directory would need to allow other users, and I could just link to that directory...

    Sorry for the flood of questions, but I have only used RPM so I have a little bit of a learning curve...
    Asus A8V Deluxe Mobo
    AMD Athlon64 X2 4400 -939
    2GB Crucial DDR3200 Dual-Channel
    ATi AiW 9800 Pro 128DDR
    Audigy2 ZS
    Sony DRU-810 DVD+RW DL
    3 x Maxtor MaxLine SATA 160Gb 16Mb Cache
    1 x Maxtor MaxLine SATA 300Gb 16Mb Cache
    1 x Maxtor MaxLine SATA 120Gb 16Mb Cache

  4. #14
    Senior Member
    Join Date
    Nov 2001
    Posts
    304

    Re:Back to Slack...

    Ok, usually things get installed into your /usr/local prefix... for instance, the man pages would be in /usr/local/man/ the binaries in /usr/local/bin/ and/or /usr/local/sbin/ so on

    With most programs, you can pass a parameter to "./configure" to make it install into "/usr" as the prefix instead of "/usr/local"

    ./configure --prefix=/usr

  5. #15

    Re:Back to Slack...

    You are awesome... thanks alot for the help!
    Asus A8V Deluxe Mobo
    AMD Athlon64 X2 4400 -939
    2GB Crucial DDR3200 Dual-Channel
    ATi AiW 9800 Pro 128DDR
    Audigy2 ZS
    Sony DRU-810 DVD+RW DL
    3 x Maxtor MaxLine SATA 160Gb 16Mb Cache
    1 x Maxtor MaxLine SATA 300Gb 16Mb Cache
    1 x Maxtor MaxLine SATA 120Gb 16Mb Cache

  6. #16
    kfx
    Guest

    Re: Back to Slack...

    You dig slack? I dig slack too.

    Don't use make install, though. Use checkinstall.

    http://asic-linux.com.mx/~izto/checkinstall/

    It's simple. Checkinstall is the last program you'll ever have to make install on. Instead, you do ./configure; make; checkinstall and it asks you a few questions, and spits out a slack package that you can install with either pkgtool or installpkg! It also generates .rpm and .deb packages, but why you'd want to sleep on that bed of nails is beyond me.

    Short story: checkinstall makes packages easily so you only ever have to compile once.

  7. #17
    Senior Member
    Join Date
    Nov 2001
    Posts
    304

    Re: Back to Slack...

    Quote Originally Posted by kfx
    Short story:* checkinstall makes packages easily so you only ever have to compile once.
    Not exactly. checkinstall creates slackware packages, but that doesn't mean you won't ever have to install again, it only makes it easier to compile on one machine so you can install via packages on multiple slackware machines via the created package. If you need to change any ./configure options and recompile, or upgrade the program with a newer version, then you will have to do another compile.

  8. #18

    Re: Back to Slack...

    I hope the next Slackware release comes out before I get my HDD cleaned up, because I'm so moving back over.
    AMD Athlon 2200+ 1.8Ghz
    1280MB PC-3200 CAS2.5 RAM
    ATI Radeon 9600 Pro 128MB AGP
    Western Digital WDC WD2500JB-00FUA0 250GB 7200 rpm ATA/133
    Seagate ST3200822A 200GB 7200 rpm ATA/133
    Western Digital WDC WD1200BB-00CAA1 120GB 7200 rpm ATA/133
    Western Digital WDC WD800BB-00CAA1 80GB 7200 rpm ATA/133
    Maxtor OneTouch 2HA43R32 1TB 7200 rpm USB 2.0
    D-Link DFE-530TX+ 10/100 NIC
    D-Link DWL-G520 Rev.A
    Debian 5.0r1 Lenny

  9. #19

    Re: Back to Slack...

    yea i moved to slack after redhat - thourght about fedora but find i really enjoy using slack more, so slack it remains
    Its better to regret something you have done than to regret something you havent done :P

Similar Threads

  1. Guess who's back.. Shady.. oh wait Lovechild' back!
    By Lovechild in forum General Chat
    Replies: 13
    Last Post: 10-25-2006, 06:30 AM
  2. Slack 10 RC1
    By CP in forum Linux - General Topics
    Replies: 19
    Last Post: 06-21-2004, 07:40 PM
  3. back to slack
    By jbstew32 in forum Linux - General Topics
    Replies: 6
    Last Post: 04-10-2003, 03:56 AM
  4. What I think about Slack....
    By paradox in forum Linux Distros
    Replies: 13
    Last Post: 02-27-2002, 03:51 AM
  5. Next Slack due when?
    By johnqpublic in forum Linux Distros
    Replies: 2
    Last Post: 10-26-2001, 11:52 PM

Bookmarks

Posting Permissions

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