Find the answer to your Linux question:
Results 1 to 9 of 9
Hi there, I just installed SuSe on a laptop and this is the first time for me that I finally start to work with Linux, due to the fact I ...
  1. #1
    Just Joined!
    Join Date
    Nov 2008
    Posts
    5

    Muse 0.9 on SuSe 11.01

    Hi there,

    I just installed SuSe on a laptop and this is the first time for me that I finally start to work with Linux, due to the fact I tried to work with it on VMWare but never came far.
    So I'm a newbie to Linux.
    I'm trying to install Muse 0.9, but first I had a qt3 error, which I fixed by setting the env. var. but now I have a new one.
    configure: error: latest alsa (0.9.x) is required
    I have a higher version on there and I installed 0.9 as well now just to fix the problem, but it keeps coming back to me.

    Any suggestions?
    Thanks in advance

    Greetzzz,

    CornElvis

    Edit:
    I worked around the ALSA problem, somehow I forgot to install some stuff for it.
    But....
    I have a new one when running Make All or Make install
    I run it as SU, so that shouldn't be a problem.

    here is the compile output:
    Code:
    >  make install
    make  install-recursive
    make[1]: Entering directory `/home/cornelis/muse-0.9'
    Making install in m4
    make[2]: Entering directory `/home/cornelis/muse-0.9/m4'
    make[3]: Entering directory `/home/cornelis/muse-0.9/m4'
    make[3]: Nothing to be done for `install-exec-am'.
    make[3]: Nothing to be done for `install-data-am'.
    make[3]: Leaving directory `/home/cornelis/muse-0.9/m4'
    make[2]: Leaving directory `/home/cornelis/muse-0.9/m4'
    Making install in synti
    make[2]: Entering directory `/home/cornelis/muse-0.9/synti'
    make  install-recursive
    make[3]: Entering directory `/home/cornelis/muse-0.9/synti'
    Making install in libsynti
    make[4]: Entering directory `/home/cornelis/muse-0.9/synti/libsynti'
    make  install-am
    make[5]: Entering directory `/home/cornelis/muse-0.9/synti/libsynti'
    make[6]: Entering directory `/home/cornelis/muse-0.9/synti/libsynti'
    make[6]: Nothing to be done for `install-exec-am'.
    make[6]: Nothing to be done for `install-data-am'.
    make[6]: Leaving directory `/home/cornelis/muse-0.9/synti/libsynti'
    make[5]: Leaving directory `/home/cornelis/muse-0.9/synti/libsynti'
    make[4]: Leaving directory `/home/cornelis/muse-0.9/synti/libsynti'
    Making install in s1
    make[4]: Entering directory `/home/cornelis/muse-0.9/synti/s1'
    make  install-am
    make[5]: Entering directory `/home/cornelis/muse-0.9/synti/s1'
    make[6]: Entering directory `/home/cornelis/muse-0.9/synti/s1'
    make[6]: Nothing to be done for `install-exec-am'.
    test -z "/usr/local/lib/muse/synthi" || mkdir -p -- "/usr/local/lib/muse/synthi"
     /bin/sh ../../libtool --mode=install /usr/bin/install -c  's1.la' '/usr/local/lib/muse/synthi/s1.la'
    /usr/bin/install -c .libs/s1.so /usr/local/lib/muse/synthi/s1.so
    /usr/bin/install -c .libs/s1.lai /usr/local/lib/muse/synthi/s1.la
    /usr/bin/install -c .libs/s1.a /usr/local/lib/muse/synthi/s1.a
    chmod 644 /usr/local/lib/muse/synthi/s1.a
    ranlib /usr/local/lib/muse/synthi/s1.a
    PATH="$PATH:/sbin" ldconfig -n /usr/local/lib/muse/synthi
    ----------------------------------------------------------------------
    Libraries have been installed in:
       /usr/local/lib/muse/synthi
    
    If you ever happen to want to link against installed libraries
    in a given directory, LIBDIR, you must either use libtool, and
    specify the full pathname of the library, or use the `-LLIBDIR'
    flag during linking and do at least one of the following:
       - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
         during execution
       - add LIBDIR to the `LD_RUN_PATH' environment variable
         during linking
       - use the `-Wl,--rpath -Wl,LIBDIR' linker flag
       - have your system administrator add LIBDIR to `/etc/ld.so.conf'
    
    See any operating system documentation about shared libraries for
    more information, such as the ld(1) and ld.so(8) manual pages.
    ----------------------------------------------------------------------
    make[6]: Leaving directory `/home/cornelis/muse-0.9/synti/s1'
    make[5]: Leaving directory `/home/cornelis/muse-0.9/synti/s1'
    make[4]: Leaving directory `/home/cornelis/muse-0.9/synti/s1'
    Making install in organ
    make[4]: Entering directory `/home/cornelis/muse-0.9/synti/organ'
    make  install-am
    make[5]: Entering directory `/home/cornelis/muse-0.9/synti/organ'
    make[6]: Entering directory `/home/cornelis/muse-0.9/synti/organ'
    make[6]: Nothing to be done for `install-exec-am'.
    test -z "/usr/local/lib/muse/synthi" || mkdir -p -- "/usr/local/lib/muse/synthi"
     /bin/sh ../../libtool --mode=install /usr/bin/install -c  'organ.la' '/usr/local/lib/muse/synthi/organ.la'
    /usr/bin/install -c .libs/organ.so /usr/local/lib/muse/synthi/organ.so
    /usr/bin/install -c .libs/organ.lai /usr/local/lib/muse/synthi/organ.la
    /usr/bin/install -c .libs/organ.a /usr/local/lib/muse/synthi/organ.a
    chmod 644 /usr/local/lib/muse/synthi/organ.a
    ranlib /usr/local/lib/muse/synthi/organ.a
    PATH="$PATH:/sbin" ldconfig -n /usr/local/lib/muse/synthi
    ----------------------------------------------------------------------
    Libraries have been installed in:
       /usr/local/lib/muse/synthi
    
    If you ever happen to want to link against installed libraries
    in a given directory, LIBDIR, you must either use libtool, and
    specify the full pathname of the library, or use the `-LLIBDIR'
    flag during linking and do at least one of the following:
       - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
         during execution
       - add LIBDIR to the `LD_RUN_PATH' environment variable
         during linking
       - use the `-Wl,--rpath -Wl,LIBDIR' linker flag
       - have your system administrator add LIBDIR to `/etc/ld.so.conf'
    
    See any operating system documentation about shared libraries for
    more information, such as the ld(1) and ld.so(8) manual pages.
    ----------------------------------------------------------------------
    make[6]: Leaving directory `/home/cornelis/muse-0.9/synti/organ'
    make[5]: Leaving directory `/home/cornelis/muse-0.9/synti/organ'
    make[4]: Leaving directory `/home/cornelis/muse-0.9/synti/organ'
    Making install in vam
    make[4]: Entering directory `/home/cornelis/muse-0.9/synti/vam'
    make  install-am
    make[5]: Entering directory `/home/cornelis/muse-0.9/synti/vam'
    make[6]: Entering directory `/home/cornelis/muse-0.9/synti/vam'
    make[6]: Nothing to be done for `install-exec-am'.
    test -z "/usr/local/lib/muse/synthi" || mkdir -p -- "/usr/local/lib/muse/synthi"
     /bin/sh ../../libtool --mode=install /usr/bin/install -c  'vam.la' '/usr/local/lib/muse/synthi/vam.la'
    /usr/bin/install -c .libs/vam.so /usr/local/lib/muse/synthi/vam.so
    /usr/bin/install -c .libs/vam.lai /usr/local/lib/muse/synthi/vam.la
    /usr/bin/install -c .libs/vam.a /usr/local/lib/muse/synthi/vam.a
    chmod 644 /usr/local/lib/muse/synthi/vam.a
    ranlib /usr/local/lib/muse/synthi/vam.a
    PATH="$PATH:/sbin" ldconfig -n /usr/local/lib/muse/synthi
    ----------------------------------------------------------------------
    Libraries have been installed in:
       /usr/local/lib/muse/synthi
    
    If you ever happen to want to link against installed libraries
    in a given directory, LIBDIR, you must either use libtool, and
    specify the full pathname of the library, or use the `-LLIBDIR'
    flag during linking and do at least one of the following:
       - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
         during execution
       - add LIBDIR to the `LD_RUN_PATH' environment variable
         during linking
       - use the `-Wl,--rpath -Wl,LIBDIR' linker flag
       - have your system administrator add LIBDIR to `/etc/ld.so.conf'
    
    See any operating system documentation about shared libraries for
    more information, such as the ld(1) and ld.so(8) manual pages.
    ----------------------------------------------------------------------
    make[6]: Leaving directory `/home/cornelis/muse-0.9/synti/vam'
    make[5]: Leaving directory `/home/cornelis/muse-0.9/synti/vam'
    make[4]: Leaving directory `/home/cornelis/muse-0.9/synti/vam'
    Making install in deicsonze
    make[4]: Entering directory `/home/cornelis/muse-0.9/synti/deicsonze'
    make  install-am
    make[5]: Entering directory `/home/cornelis/muse-0.9/synti/deicsonze'
    if /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../..    -g -fno-exceptions -Wall -W -D_GNU_SOURCE -D_REENTRANT   -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT   -I../.. -I../../muse/widgets -I/usr/lib/qt3/include -I.. -I../../synti -I../../muse/widgets -DQT_SHARED -DQT_THREAD_SUPPORT -DQT_PLUGIN  -DINSTPREFIX=\"/usr/local\" -g -O2 -MT deicsonze.lo -MD -MP -MF ".deps/deicsonze.Tpo" -c -o deicsonze.lo deicsonze.cpp; \
    	then mv -f ".deps/deicsonze.Tpo" ".deps/deicsonze.Plo"; else rm -f ".deps/deicsonze.Tpo"; exit 1; fi
     g++ -DHAVE_CONFIG_H -I. -I. -I../.. -g -fno-exceptions -Wall -W -D_GNU_SOURCE -D_REENTRANT -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT -I../.. -I../../muse/widgets -I/usr/lib/qt3/include -I.. -I../../synti -I../../muse/widgets -DQT_SHARED -DQT_THREAD_SUPPORT -DQT_PLUGIN -DINSTPREFIX=\"/usr/local\" -g -O2 -MT deicsonze.lo -MD -MP -MF .deps/deicsonze.Tpo -c deicsonze.cpp  -fPIC -DPIC -o .libs/deicsonze.o
    deicsonze.cpp: In constructor 'DeicsOnze::DeicsOnze()':
    deicsonze.cpp:90: error: 'srand' was not declared in this scope
    deicsonze.cpp: In function 'void lfoUpdate(Preset*, Global*, float*)':
    deicsonze.cpp:991: error: 'rand' was not declared in this scope
    deicsonze.cpp:991: error: 'RAND_MAX' was not declared in this scope
    deicsonze.cpp: In member function 'virtual const char* DeicsOnze::getPatchName(int, int, int) const':
    deicsonze.cpp:1250: warning: deprecated conversion from string constant to 'char*'
    make[5]: *** [deicsonze.lo] Error 1
    make[5]: Leaving directory `/home/cornelis/muse-0.9/synti/deicsonze'
    make[4]: *** [install] Error 2
    make[4]: Leaving directory `/home/cornelis/muse-0.9/synti/deicsonze'
    make[3]: *** [install-recursive] Error 1
    make[3]: Leaving directory `/home/cornelis/muse-0.9/synti'
    make[2]: *** [install] Error 2
    make[2]: Leaving directory `/home/cornelis/muse-0.9/synti'
    make[1]: *** [install-recursive] Error 1
    make[1]: Leaving directory `/home/cornelis/muse-0.9'
    make: *** [install] Error 2
    Last edited by cornelvis; 11-09-2008 at 05:08 PM.

  2. #2
    Linux Engineer scrarfussi's Avatar
    Join Date
    Aug 2006
    Posts
    1,029
    hi and welcome to the forums and too opensuse since you are new i will make a simple suggestion its always advisable too install all software through the package manager unless you really have too manually install but these cases are now very rare you can install muse from yast that is administrator settings yast -> software management and install muse from there

    you can add more repositries from here Additional YaST Package Repositories - openSUSE this allows you to get more software also fixing your dependency issues

  3. #3
    Just Joined!
    Join Date
    Nov 2008
    Posts
    5
    Thanks scrarfussi.
    But to install via Yast it needs to be a rpm file right?
    I only have tar.gz and tried to follow instructions from their website.
    To use the install manager to install something additional, how do I do that, because I can only select and install what is already there and can not browse to a package or so.
    I tried with right clicking as well and then it says it needs to be a rpm file.

    Thanks for the warm welcome and responses

  4. #4
    Linux Engineer scrarfussi's Avatar
    Join Date
    Aug 2006
    Posts
    1,029
    To install via yast you do not need the rpm file yast wil find the package from the online repositries and install it for you as Well as fix your dependency issues give it a try

  5. #5
    Just Joined!
    Join Date
    Nov 2008
    Posts
    5
    Quote Originally Posted by scrarfussi View Post
    To install via yast you do not need the rpm file yast wil find the package from the online repositries and install it for you as Well as fix your dependency issues give it a try
    Thanks for that.
    It was sitting there all the time for me to install.

    Great thanks.

    Greetzzz,

    CornElvis

  6. #6
    Linux Engineer scrarfussi's Avatar
    Join Date
    Aug 2006
    Posts
    1,029
    Glad i could help alway's try and use yast unless its something you can't get from yast then you can brave the manual install

  7. #7
    Just Joined!
    Join Date
    Nov 2008
    Posts
    5
    I have installed it now, but it doesn't run very properly.
    I have two options Muse and Muse2, they can't dow ithout eachother, but when I install the Muse2 it doesn't come further than the select project and then shows very short a window and then does nothing anymore
    Any ideas?

  8. #8
    Just Joined!
    Join Date
    Nov 2008
    Posts
    5
    Quote Originally Posted by cornelvis View Post
    I have installed it now, but it doesn't run very properly.
    I have two options Muse and Muse2, they can't dow ithout eachother, but when I install the Muse2 it doesn't come further than the select project and then shows very short a window and then does nothing anymore
    Any ideas?
    I installed JAD on openSuSe Linux and all is running very smooth now with Ardour and more.
    Thanks for the patience.

  9. #9
    Linux Engineer scrarfussi's Avatar
    Join Date
    Aug 2006
    Posts
    1,029
    Good for you glad it worked

Posting Permissions

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