SourceForge has been redesigned. Learn more.
Close

Problem with ubantu, make install,

Help
stratos13
2008-04-21
2013-05-23
  • stratos13

    stratos13 - 2008-04-21

    Hello, Please help. I am new user to linux.

    i run the ./configure   -all are ok
    i run make              -all are ok

    but when i run   make install it shows me this

    oem@ubuntu:~/Desktop/bristol-0.20.1$ make install
    Making install in libbrightonX11
    make[1]: Entering directory `/home/oem/Desktop/bristol-0.20.1/libbrightonX11'
    make[2]: Entering directory `/home/oem/Desktop/bristol-0.20.1/libbrightonX11'
    test -z "/usr/local/lib" || /bin/mkdir -p "/usr/local/lib"
    /bin/bash ../libtool --mode=install /usr/bin/install -c  'libB11.la' '/usr/local/lib/libB11.la'
    /usr/bin/install -c .libs/libB11.so.0.0.20 /usr/local/lib/libB11.so.0.0.20
    /usr/bin/install: cannot create regular file `/usr/local/lib/libB11.so.0.0.20': Permission denied
    make[2]: *** [install-libLTLIBRARIES] Error 1
    make[2]: Leaving directory `/home/oem/Desktop/bristol-0.20.1/libbrightonX11'
    make[1]: *** [install-am] Error 2
    make[1]: Leaving directory `/home/oem/Desktop/bristol-0.20.1/libbrightonX11'
    make: *** [install-recursive] Error 1
    oem@ubuntu:~/Desktop/bristol-0.20.1$

     
    • Nick Copeland

      Nick Copeland - 2008-04-21

      Hi There,

      There are a few possible solutions to this none of which is 'correct' or 'better' than any other. When you  use the 'make' commands they are executed with your read/write permissions and you probably have the ability to write the new binaries. When you do the install then there are lots of files that need to be moved to /usr/local and normally a user does not have permissions to write into these locations. The easiest method is probably:

      $  sudo make install

      This will execute the install command as root and this should be able to write all the data to /usr/local, after that you can use startBristol or perhaps /usr/local/bin/startBristol depending on whether /usr/local/bin is in your path.

      Alternatively you could try to install in your home directly with options to the "./configure", something like -prefix $HOME/local - that is probably not the best option but it can work and keeps /usr a little cleaner.

      The last option (and I use this on my development system) is to give yourself write permissions on /usr/local/bin, /usr/local/lib and /usr/local/share/bristol - this is useful for me as I execute make install several times a day. On a user system you probably only need to do a make install once per release and as such this is a little excessive.

      Kind regards,
      Nick.

       
    • stratos13

      stratos13 - 2008-04-21

      i run the program

      oem@ubuntu:/usr/local/bin$ startBristol mini

      and this is what it does (what i dont do well, please help me)

      spawning midi thread
      parent going into idle loop
      connected to :0.0
      display is 1280 by 1024 pixels
      Window is w 1280, h 1024, d 24, 0 0 0
      midi sequencer
      Opened listening control socket: 5028
      Error opening midi device bristol, exiting midi thread
      Using DirectColor display
      alloc color by name Blue
      Initialise the hammondB3 link to bristol: 811bfd0
      hostname is localhost, bristol
      TCP port: 5028
      Connected to the bristol control socket: 5
      bristolengine already active
      parent exiting
      return - no data in buffer
      cleanupBrighton(0)
      cleared sigpipe handler
      cleanupBrighton(0)
      midi write error, fd 5, size 1
      midi write error, fd 5, size 12
      midi write error, fd 5, size 1
      return - no data in buffer
      socket closed
      request acked: -1
      oem@ubuntu:/usr/local/bin$ startBristol mini
      spawning midi thread
      parent going into idle loop
      connected to :0.0
      display is 1280 by 1024 pixels
      Window is w 1280, h 1024, d 24, 0 0 0
      Using DirectColor display
      alloc color by name Blue
      midi sequencer
      Opened listening control socket: 5028
      Error opening midi device bristol, exiting midi thread
      Initialise the hammondB3 link to bristol: 811bfd0
      hostname is localhost, bristol
      TCP port: 5028
      Connected to the bristol control socket: 5
      bristolengine already active
      parent exiting
      return - no data in buffer
      cleanupBrighton(0)
      cleared sigpipe handler
      cleanupBrighton(0)
      midi write error, fd 5, size 1
      midi write error, fd 5, size 12
      midi write error, fd 5, size 1
      return - no data in buffer
      socket closed
      request acked: -1
      oem@ubuntu:/usr/local/bin$

       
    • Nick Copeland

      Nick Copeland - 2008-04-21

      Can you try the following:

      ps ax | egrep '(bristol|brighton|jack)'

      If you see either bristol or brighton then kill it with 'kill -TERM pid' where pid is the process id given in the 'ps' command. If bristol is already active then you sometimes get this. After that try the following:

      startBristol -alsa -mini

      You seem to have quite an old version of bristol, not that it should matter too much. You may also want to try "startBristol -oss -mini" as well, or look to make sure the ALSA drivers are working:

      cat /proc/asound/devices

      Regards,

      Nick.

       

Log in to post a comment.