Compiling python from soruce vs RPM ?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • howa

    #1

    Compiling python from soruce vs RPM ?

    I have compiled python 2.5 from source

    i.e.

    ../configure
    make
    make install


    but when i try to install another package require python, seems it
    can't regonize python...

    e.g..


    /usr/bin/python is needed by xyz

  • hlubenow

    #2
    Re: Compiling python from soruce vs RPM ?

    howa wrote:
    I have compiled python 2.5 from source
    >
    i.e.
    >
    ./configure
    make
    make install
    >
    >
    but when i try to install another package require python, seems it
    can't regonize python...
    >
    e.g..
    >
    >
    /usr/bin/python is needed by xyz
    Does "/usr/bin/python" exist ?

    Why haven't you installed via rpm ?

    H.

    Comment

    • Paul Boddie

      #3
      Re: Compiling python from soruce vs RPM ?

      howa wrote:
      I have compiled python 2.5 from source
      >
      i.e.
      >
      ./configure
      make
      make install
      By default, configure uses /usr/local as the "prefix", not /usr...
      but when i try to install another package require python, seems it
      can't regonize python...
      >
      e.g..
      >
      >
      /usr/bin/python is needed by xyz
      Consequently, by default, Python will be found at /usr/local/bin/
      python, not /usr/bin/python as you seem to require. Try building from
      source again:

      make clean # probably needed if rebuilding in the same place
      ../configure --prefix=/usr
      make
      make install

      Since /usr/bin/python isn't found, it doesn't look like there's an
      existing version of Python that you might overwrite, but it's
      important to verify such things when installing software. That's where
      your distribution's packages have an advantage, and it's arguably a
      better idea to install such packages instead, possibly building them
      from source if no binary packages exist yet for Python 2.5. (If no
      source packages exist, you have a bit more work to do.)

      Paul

      Comment

      • howa

        #4
        Re: Compiling python from soruce vs RPM ?

        On Apr 19, 6:10 am, Paul Boddie <p...@boddie.or g.ukwrote:
        >
        Since /usr/bin/python isn't found, it doesn't look like there's an
        existing version of Python that you might overwrite, but it's
        important to verify such things when installing software. That's where
        your distribution's packages have an advantage, and it's arguably a
        better idea to install such packages instead, possibly building them
        from source if no binary packages exist yet for Python 2.5. (If no
        source packages exist, you have a bit more work to do.)
        >
        Paul

        Thanks.


        One more question:

        How to uninstall using the source package?

        the source package doesn't come with `make uninstall`?




        Comment

        • Paul Boddie

          #5
          Re: Compiling python from soruce vs RPM ?

          On 19 Apr, 04:39, howa <howac...@gmail .comwrote:
          >
          One more question:
          >
          How to uninstall using the source package?
          >
          the source package doesn't come with `make uninstall`?
          Right. That's another pitfall of most source distributions (ie. the
          Python sources from python.org) compared to system packages (ie. the
          package built from a source RPM or equivalent system source package).
          If you want a really quick solution to this which seems to work much
          of the time, look at checkinstall:



          This tool will make system packages by taking control of the usual
          build process, and you can then install and uninstall those system
          packages.

          Paul

          Comment

          • howa

            #6
            Re: Compiling python from soruce vs RPM ?

            On 4¤ë19¤é, ¤U¤È5®É49¤À, Paul Boddie <p...@boddie.or g..ukwrote:
            On 19 Apr, 04:39, howa <howac...@gmail .comwrote:
            >
            >
            >
            One more question:
            >
            How to uninstall using the source package?
            >
            the source package doesn't come with `make uninstall`?
            >
            Right. That's another pitfall of most source distributions (ie. the
            Python sources from python.org) compared to system packages (ie. the
            package built from a source RPM or equivalent system source package).
            If you want a really quick solution to this which seems to work much
            of the time, look at checkinstall:
            >

            >
            This tool will make system packages by taking control of the usual
            build process, and you can then install and uninstall those system
            packages.
            >
            Paul
            but i have the source package being installed...so any method/script
            to remove them?

            since finally i want to install via RPM ...

            thanks anyway

            Comment

            • Paul Boddie

              #7
              Re: Compiling python from soruce vs RPM ?

              On 19 Apr, 18:40, howa <howac...@gmail .comwrote:
              >
              but i have the source package being installed...so any method/script
              to remove them?
              >
              since finally i want to install via RPM ...
              You could use checkinstall to make a package, install it (forcibly if
              necessary), then remove it. That might wipe away the things installed
              when you did "make install" since checkinstall should note which files
              were to be installed, add them to its manifest, then construct the
              package such that those files will be removed when the package is
              uninstalled.

              No promises, though...

              Paul

              Comment

              Working...