Installing with Linux

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • PaulBlay
    Knight
    • Jan 2009
    • 657

    Installing with Linux

    A day or two I was trying to install in Linux I consulted http://rephial.org/wiki/Compiling#s2_2 and used ...

    Code:
    ./configure --with-noinstall
    make
    It didn't work.

    After some fiddling around I found that
    a) Changing to root
    b) Using
    Code:
    autogen
    ./configure --with-noinstall
    make
    Did work.

    However today I'm stuck with autogen not working again.

    I'm using a variety of slackware Linux and I'm a complete novice with it. Any clues, hints, etc.?
    Currently turning (Angband) Japanese.
  • PowerDiver
    Prophet
    • Mar 2008
    • 2820

    #2
    I reported some really really strange problems, maybe within the last week, in some other thread, trying to compile the dev code. My ./configure was unable to correctly process noinstall or no-install or whatever it is.

    My suggestion is that you throw away what you have, since there are probably a bunch of invisible files owned by root that you have generated, and start over with a fresh unzipped directory. Hopefully you do not need to do anything as root.

    I hope I remember the names correctly.
    Try ./autogen.sh followed by a simple ./configure
    Then cd into src and make -f Makefile.std
    Then copy the executable up, i.e. cp angband ..
    Then write yourself a little script that cds to the directory with the copied executable and runs from there and put the script in some directory in your path.

    This might work. I have not tried it since I needed a multiuser system.

    If you want an install shared by multiple users, things get a little more complicated. I used make install, but if you have both 3.0 and 3.1 fighting over /usr/local/share there will be conflicts for sure.

    Comment

    • takkaria
      Veteran
      • Apr 2007
      • 1951

      #3
      Originally posted by PowerDiver
      I reported some really really strange problems, maybe within the last week, in some other thread, trying to compile the dev code. My ./configure was unable to correctly process noinstall or no-install or whatever it is.

      My suggestion is that you throw away what you have, since there are probably a bunch of invisible files owned by root that you have generated, and start over with a fresh unzipped directory. Hopefully you do not need to do anything as root.

      I hope I remember the names correctly.
      Try ./autogen.sh followed by a simple ./configure
      Then cd into src and make -f Makefile.std
      Then copy the executable up, i.e. cp angband ..
      Then write yourself a little script that cds to the directory with the copied executable and runs from there and put the script in some directory in your path.
      The only steps you need from there are actually "make -f Makefile.std" and the last step. configure has no effect with makefile.std, and it automatically does the cp angband .. bit.
      takkaria whispers something about options. -more-

      Comment

      • takkaria
        Veteran
        • Apr 2007
        • 1951

        #4
        Originally posted by PaulBlay
        A day or two I was trying to install in Linux I consulted http://rephial.org/wiki/Compiling#s2_2 and used ...

        Code:
        ./configure --with-noinstall
        make
        It didn't work.
        In what sense, 'didn't work'?

        After some fiddling around I found that
        a) Changing to root
        b) Using
        Code:
        autogen
        ./configure --with-noinstall
        make
        Did work.

        However today I'm stuck with autogen not working again.

        I'm using a variety of slackware Linux and I'm a complete novice with it. Any clues, hints, etc.?
        If you provide details of error messages or specific problems aside from "it's not working" it's much easier to diagnose things.
        takkaria whispers something about options. -more-

        Comment

        • PowerDiver
          Prophet
          • Mar 2008
          • 2820

          #5
          Originally posted by takkaria
          The only steps you need from there are actually "make -f Makefile.std" and the last step. configure has no effect with makefile.std, and it automatically does the cp angband .. bit.
          I thought there was something about some include file that needed to be generated in src, maybe autoconf.in?, but clearly if we are disagreeing I was confused.

          Comment

          • PaulBlay
            Knight
            • Jan 2009
            • 657

            #6
            Originally posted by takkaria
            In what sense, 'didn't work'?
            Froze, no error message (or any other sort of message).

            I've just figured out that it apparently needs to be "autogen.sh" not "autogen" typed in the terminal. This time around it worked without going to root first (although I'm not sure what, if anything, I did differently).
            Currently turning (Angband) Japanese.

            Comment

            Working...
            😀
            😂
            🥰
            😘
            🤢
            😎
            😞
            😡
            👍
            👎