Two questions for Suse 10.2

1. How can I make my creative sound blaster live work( as in to make it produce sounds, need drivers, and to make it work like if it was on windows Xp)?

2. Where can I find a program that is equivalent to Alcohol 120%, because I need to burn a img, ccd, and a sub file for a friend of my.
55 answers Last reply
More about questions suse
  1. Quote:
    1. How can I make my creative sound blaster live work( as in to make it produce sounds, need drivers, and to make it work like if it was on windows Xp)?

    2. Where can I find a program that is equivalent to Alcohol 120%, because I need to burn a img, ccd, and a sub file for a friend of my.



    Hi :-D

    You shouldn't need a driver, SuSE should already have the SB driver built-in.

    I believe the snd_emu10k1 kernel module should handle everything it might be called something else on SuSE.



    lsmod # lists your loaded kernel modules

    lsmod |grep -i snd # lists loaded kernel modules which match [b]snd[/b] case insensitive

    lsmod |grep -i emu # lists loaded kernel modules which match [b]emu[/b] case insensitive

    dmesg |grep -i emu # shows kernel messages containing emu

    lspci

    lspci -v

    lspci -vv

    # will list your hardware devices with increasing detail.

    procinfo # will show your devices and their interrupts

    [/code:1:af6ae9003c]


    Regarding Alcohol 120%.... Linux uses ISOs which are an international standard. Some windows programs use proprietary image formats however you can sometimes convert them from the proprietary format to the ISO standard format.

    For example you can convert Nero .nrg files into ISOs

    http://www.weethet.nl/english/cdrw_nrgtoiso.php

    You may be able to convert the .img files to ISOs with the right converter however you need to know what program created the .img

    .img is a common extension so it's hard to tell what kind of format it actually is.

    [code:1:af6ae9003c]
    file filename.img # will try to identify the type of file
    [/code:1:af6ae9003c]

    This may help but you will probably need to be more specific:

    http://www.google.com/search?hl=en&q=img+to+ISO&btnG=Google+Search
  2. I think the program that made the img for virtual drivers is something with ghost.
  3. Quote:
    I think the program that made the img for virtual drivers is something with ghost.



    What's the output of this?


    file your_filename_here.img
    [/code:1:924be29050]


    ghost is a hard drive imaging utility, are you sure that's what created it?
  4. Quote:
    I think the program that made the img for virtual drivers is something with ghost.



    What's the output of this?


    file your_filename_here.img
    [/code:1:519ff7e44b]


    ghost is a hard drive imaging utility, are you sure that's what created it?

    Well, I think it could be ghost disk, but the sourse is unknown. The output I think is GHOST_001.img
  5. Quote:
    I think the program that made the img for virtual drivers is something with ghost.



    What's the output of this?


    file your_filename_here.img
    [/code:1:efddf0ee8f]


    ghost is a hard drive imaging utility, are you sure that's what created it?

    Well, I think it could be ghost disk, but the sourse is unknown. The output I think is GHOST_001.img


  6. CCD + IMG +SUB is a CloneCD trio. Use ccd2iso to convert. And stop pirating :)!
  7. Quote:
    CCD + IMG +SUB is a CloneCD trio. Use ccd2iso to convert. And stop pirating :)!



    Hehe, great find!!! :-D
  8. Quote:
    CCD + IMG +SUB is a CloneCD trio. Use ccd2iso to convert. And stop pirating :)!



    Hehe, great find!!! :-D

    How do you install tar.gz? Because I'm a newbie, and I haven't dealt with these file format.
  9. Enter the consel and log in as root

    tar -zxvf YourFile.tar.gz

    Then navagate to the folder that was created (it will be the same as the name of the package)

    ./configure
    make
    make install

    You are usually dealing with files that have long names. One way to speed things up is to type the first couple of letters of the package name and the press tab. It will fill in the name for you.
  10. Quote:
    Enter the consel and log in as root

    tar -zxvf YourFile.tar.gz

    Then navagate to the folder that was created (it will be the same as the name of the package)

    ./configure
    make
    make install

    You are usually dealing with files that have long names. One way to speed things up is to type the first couple of letters of the package name and the press tab. It will fill in the name for you.


    Is su root, or is something else?
  11. Your right, su logs you in as root
  12. Quote:
    Your right, su logs you in as root



    It certainly does :-D




    su # become root

    su - # become root and read init scripts in /root

    [/code:1:9a9f829c1d]

    Here's some useful info:

    http://en.wikibooks.org/wiki/Linux_For_Newbies

    http://en.wikibooks.org/wiki/Linux_software_howtos

    http://en.wikibooks.org/wiki/Linux_Guide


    Enjoy :-D
  13. I used the tar -zxvf ccd2iso-0.2.tar.gz, but it said tar: ccd2iso-0.2.tar.gz: Cannot open: No such file or directory
    tar: Error is not recoverable: exiting now
    tar: Child returned status 2
    tar: Error exit delayed from previous errors ,and I dunno what's wrong with the tar thing. Also, the file is on my desktop, so do I move it to some other place?
  14. Quote:
    I used the tar -zxvf ccd2iso-0.2.tar.gz, but it said tar: ccd2iso-0.2.tar.gz: Cannot open: No such file or directory
    tar: Error is not recoverable: exiting now
    tar: Child returned status 2
    tar: Error exit delayed from previous errors ,and I dunno what's wrong with the tar thing. Also, the file is on my desktop, so do I move it to some other place?



    You have to be in the same directory as the tar file to run that command that way.




    # assuming the tgz is in your home directory

    cd $HOME

    tar xzvf ccd2iso-0.2.tar.gz

    # you can also run it like this: tar xzvf /home/your_username/some_directory/ccd2iso-0.2.tar.gz

    cd ccd2iso-0.2

    ./configure --prefix=/usr/local # if it works proceed to the next step

    make # if it works proceed to the next step
    make install # if it works proceed to the next step

    /usr/local/bin/ccd2iso --help # this doesn't work for every program

    [/code:1:f2a78440db]
  15. Great advice as always, just adding (since it's on the desktop aparently)
    mv ~/Desktop/ccd2iso-0.2.tar.gz ~

    //then linux_0's stuff//
    # assuming the tgz is in your home directory

    cd $HOME

    tar xzvf ccd2iso-0.2.tar.gz
    ...[/code:1:dcdc3fc80d]

    Good luck
  16. what do you do after you do this?
    ccd2iso/
    ccd2iso/acconfig.h
    ccd2iso/config.h
    ccd2iso/src/
    ccd2iso/src/ccd2iso.c
    ccd2iso/src/clonecd.h
    ccd2iso/src/Makefile.am
    ccd2iso/src/Makefile.in
    ccd2iso/AUTHORS
    ccd2iso/ChangeLog
    ccd2iso/configure
    ccd2iso/configure.in
    ccd2iso/COPYING
    ccd2iso/INSTALL
    ccd2iso/Makefile.am
    ccd2iso/Makefile.cvs
    ccd2iso/NEWS
    ccd2iso/README
    ccd2iso/TODO
    ccd2iso/install-sh
    ccd2iso/config.sub
    ccd2iso/config.guess
    ccd2iso/Makefile.in
    ccd2iso/config.h.in
    ccd2iso/ltmain.sh
    ccd2iso/mkinstalldirs
    ccd2iso/missing
    ccd2iso/libtool
    ccd2iso/depcomp
    I dunno what else to do. BTW, is there books that is short enough to understand how to use Suse 10?
  17. Quote:
    what do you do after you do this?
    ccd2iso/
    ccd2iso/acconfig.h
    ccd2iso/config.h
    ccd2iso/src/
    ccd2iso/src/ccd2iso.c
    ccd2iso/src/clonecd.h
    ccd2iso/src/Makefile.am
    ccd2iso/src/Makefile.in
    ccd2iso/AUTHORS
    ccd2iso/ChangeLog
    ccd2iso/configure
    ccd2iso/configure.in
    ccd2iso/COPYING
    ccd2iso/INSTALL
    ccd2iso/Makefile.am
    ccd2iso/Makefile.cvs
    ccd2iso/NEWS
    ccd2iso/README
    ccd2iso/TODO
    ccd2iso/install-sh
    ccd2iso/config.sub
    ccd2iso/config.guess
    ccd2iso/Makefile.in
    ccd2iso/config.h.in
    ccd2iso/ltmain.sh
    ccd2iso/mkinstalldirs
    ccd2iso/missing
    ccd2iso/libtool
    ccd2iso/depcomp
    I dunno what else to do. BTW, is there books that is short enough to understand how to use Suse 10?





    cd ccd2iso # change directory to ccd2iso

    ./configure --prefix=/usr/local # configure it and have it install to /usr/local

    make # compile it

    su - # become root / superuser

    make install # install it

    [/code:1:3e13d3a0cb]
  18. I'm missing aclocal -1.6, and does anyone know how to find the file, because the google site gives acmake or something like that.
  19. Quote:
    I'm missing aclocal -1.6, and does anyone know how to find the file, because the google site gives acmake or something like that.



    You need to install automake with YaST or by hand.
  20. In this case, I think going with YaST is the way to go :)

    Open up YaST and install the Developer Tools. Will double-check the process when I get home and have access to my machine.
  21. Quote:
    In this case, I think going with YaST is the way to go :)

    Open up YaST and install the Developer Tools. Will double-check the process when I get home and have access to my machine.



    Indeed :-D

    YaST is a lot easier.
  22. Do I use the latest ones, or orders ones, because I have no clue. I guess I'll try and see with the newest one, or close to the newest.

    Ok, after getting automake, do I combine the file and the ccd2iso files, or do I have to do something else with it?
  23. Quote:
    Do I use the latest ones, or orders ones, because I have no clue. I guess I'll try and see with the newest one, or close to the newest.

    Ok, after getting automake, do I combine the file and the ccd2iso files, or do I have to do something else with it?



    Grab automake, gcc, make etc

    Then try again.
  24. Is there a way I can make a makefile?
  25. Quote:
    Is there a way I can make a makefile?



    There certainly is, but what for?
  26. you mention make, but I don't know what you mean, so I'm having a hard time finding it.
  27. Quote:
    you mention make, but I don't know what you mean, so I'm having a hard time finding it.



    As long as the make package is installed you're fine.

    The configure script will make the makefile for you so you don't have to worry about it.

    Just make sure gcc, automake, and accompanying libraries are installed.
  28. Do you do anything else after this?
    linux-p8wc:/home/jim/automake-1.9.6 # ./configure --prefix=/usr/local # configure it and have it install to /usr/local
    checking build system type... x86_64-unknown-linux-gnu
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking for perl... /usr/bin/perl
    checking for tex... tex
    checking whether autoconf is installed... yes
    checking whether autoconf works... yes
    checking whether autoconf is recent enough... yes
    checking whether ln works... yes
    checking for grep that handles long lines and -e... /usr/bin/grep
    checking for egrep... /usr/bin/grep -E
    checking for fgrep... /usr/bin/grep -F
    configure: creating ./config.status
    config.status: creating Makefile
    config.status: creating doc/Makefile
    config.status: creating lib/Automake/Makefile
    config.status: creating lib/Automake/tests/Makefile
    config.status: creating lib/Makefile
    config.status: creating lib/am/Makefile
    config.status: creating m4/Makefile
    config.status: creating tests/Makefile
    config.status: creating tests/defs
    config.status: creating tests/aclocal-1.9
    config.status: creating tests/automake-1.9
    linux-p8wc:/home/jim/automake-1.9.6 # Do I use make install, or did I have to do something else? I did make install and it got me this.
    linux-p8wc:/home/jim/automake-1.9.6 # make install
    Making install in .
    make[1]: Entering directory `/home/jim/automake-1.9.6'
    rm -f automake automake.tmp
    sed -e 's,[@]APIVERSION[@],1.9,g' -e 's,[@]PACKAGE[@],automake,g' -e 's,[@]PATH_SEPARATOR[@],:,g' -e 's,[@]PERL[@],/usr/bin/perl,g' -e 's,[@]SHELL[@],/bin/sh,g' -e 's,[@]VERSION[@],1.9.6,g' -e 's,[@]configure_input[@],Generated from automake.in; do not edit by hand.,g' -e 's,[@]datadir[@],/usr/local/share,g' ./automake.in >automake.tmp
    chmod +x automake.tmp
    chmod a-w automake.tmp
    mv -f automake.tmp automake
    rm -f aclocal aclocal.tmp
    sed -e 's,[@]APIVERSION[@],1.9,g' -e 's,[@]PACKAGE[@],automake,g' -e 's,[@]PATH_SEPARATOR[@],:,g' -e 's,[@]PERL[@],/usr/bin/perl,g' -e 's,[@]SHELL[@],/bin/sh,g' -e 's,[@]VERSION[@],1.9.6,g' -e 's,[@]configure_input[@],Generated from aclocal.in; do not edit by hand.,g' -e 's,[@]datadir[@],/usr/local/share,g' ./aclocal.in >aclocal.tmp
    chmod +x aclocal.tmp
    chmod a-w aclocal.tmp
    mv -f aclocal.tmp aclocal
    make[2]: Entering directory `/home/jim/automake-1.9.6'
    test -z "/usr/local/bin" || mkdir -p -- "/usr/local/bin"
    /usr/bin/install -c 'automake' '/usr/local/bin/automake'
    /usr/bin/install -c 'aclocal' '/usr/local/bin/aclocal'
    make install-exec-hook
    make[3]: Entering directory `/home/jim/automake-1.9.6'
    ln /usr/local/bin/automake /usr/local/bin/automake-1.9
    ln /usr/local/bin/aclocal /usr/local/bin/aclocal-1.9
    make[3]: Leaving directory `/home/jim/automake-1.9.6'
    make[2]: Nothing to be done for `install-data-am'.
    make[2]: Leaving directory `/home/jim/automake-1.9.6'
    make[1]: Leaving directory `/home/jim/automake-1.9.6'
    Making install in doc
    make[1]: Entering directory `/home/jim/automake-1.9.6/doc'
    make[2]: Entering directory `/home/jim/automake-1.9.6/doc'
    make[2]: Nothing to be done for `install-exec-am'.
    test -z "/usr/local/share/info" || mkdir -p -- "/usr/local/share/info"
    /usr/bin/install -c -m 644 './automake.info' '/usr/local/share/info/automake.info'
    /usr/bin/install -c -m 644 './automake.info-1' '/usr/local/share/info/automake.info-1'
    /usr/bin/install -c -m 644 './automake.info-2' '/usr/local/share/info/automake.info-2'
    install-info --info-dir='/usr/local/share/info' '/usr/local/share/info/automake.info'
    make[2]: Leaving directory `/home/jim/automake-1.9.6/doc'
    make[1]: Leaving directory `/home/jim/automake-1.9.6/doc'
    Making install in m4
    make[1]: Entering directory `/home/jim/automake-1.9.6/m4'
    make[2]: Entering directory `/home/jim/automake-1.9.6/m4'
    make[2]: Nothing to be done for `install-exec-am'.
    test -z "/usr/local/share/aclocal-1.9" || mkdir -p -- "/usr/local/share/aclocal-1.9"
    /usr/bin/install -c -m 644 '../m4/amversion.m4' '/usr/local/share/aclocal-1.9/amversion.m4'
    /usr/bin/install -c -m 644 'as.m4' '/usr/local/share/aclocal-1.9/as.m4'
    /usr/bin/install -c -m 644 'auxdir.m4' '/usr/local/share/aclocal-1.9/auxdir.m4'
    /usr/bin/install -c -m 644 'ccstdc.m4' '/usr/local/share/aclocal-1.9/ccstdc.m4'
    /usr/bin/install -c -m 644 'cond.m4' '/usr/local/share/aclocal-1.9/cond.m4'
    /usr/bin/install -c -m 644 'depend.m4' '/usr/local/share/aclocal-1.9/depend.m4'
    /usr/bin/install -c -m 644 'depout.m4' '/usr/local/share/aclocal-1.9/depout.m4'
    /usr/bin/install -c -m 644 'dmalloc.m4' '/usr/local/share/aclocal-1.9/dmalloc.m4'
    /usr/bin/install -c -m 644 'gcj.m4' '/usr/local/share/aclocal-1.9/gcj.m4'
    /usr/bin/install -c -m 644 'header.m4' '/usr/local/share/aclocal-1.9/header.m4'
    /usr/bin/install -c -m 644 'init.m4' '/usr/local/share/aclocal-1.9/init.m4'
    /usr/bin/install -c -m 644 'install-sh.m4' '/usr/local/share/aclocal-1.9/install-sh.m4'
    /usr/bin/install -c -m 644 'lead-dot.m4' '/usr/local/share/aclocal-1.9/lead-dot.m4'
    /usr/bin/install -c -m 644 'lex.m4' '/usr/local/share/aclocal-1.9/lex.m4'
    /usr/bin/install -c -m 644 'lispdir.m4' '/usr/local/share/aclocal-1.9/lispdir.m4'
    /usr/bin/install -c -m 644 'maintainer.m4' '/usr/local/share/aclocal-1.9/maintainer.m4'
    /usr/bin/install -c -m 644 'make.m4' '/usr/local/share/aclocal-1.9/make.m4'
    /usr/bin/install -c -m 644 'minuso.m4' '/usr/local/share/aclocal-1.9/minuso.m4'
    /usr/bin/install -c -m 644 'missing.m4' '/usr/local/share/aclocal-1.9/missing.m4'
    /usr/bin/install -c -m 644 'mkdirp.m4' '/usr/local/share/aclocal-1.9/mkdirp.m4'
    /usr/bin/install -c -m 644 'multi.m4' '/usr/local/share/aclocal-1.9/multi.m4'
    /usr/bin/install -c -m 644 'obsol-gt.m4' '/usr/local/share/aclocal-1.9/obsol-gt.m4'
    /usr/bin/install -c -m 644 'obsol-lt.m4' '/usr/local/share/aclocal-1.9/obsol-lt.m4'
    /usr/bin/install -c -m 644 'obsolete.m4' '/usr/local/share/aclocal-1.9/obsolete.m4'
    /usr/bin/install -c -m 644 'options.m4' '/usr/local/share/aclocal-1.9/options.m4'
    /usr/bin/install -c -m 644 'protos.m4' '/usr/local/share/aclocal-1.9/protos.m4'
    /usr/bin/install -c -m 644 'python.m4' '/usr/local/share/aclocal-1.9/python.m4'
    /usr/bin/install -c -m 644 'regex.m4' '/usr/local/share/aclocal-1.9/regex.m4'
    /usr/bin/install -c -m 644 'runlog.m4' '/usr/local/share/aclocal-1.9/runlog.m4'
    /usr/bin/install -c -m 644 'sanity.m4' '/usr/local/share/aclocal-1.9/sanity.m4'
    /usr/bin/install -c -m 644 'strip.m4' '/usr/local/share/aclocal-1.9/strip.m4'
    /usr/bin/install -c -m 644 'tar.m4' '/usr/local/share/aclocal-1.9/tar.m4'
    make[2]: Leaving directory `/home/jim/automake-1.9.6/m4'
    make[1]: Leaving directory `/home/jim/automake-1.9.6/m4'
    Making install in lib
    make[1]: Entering directory `/home/jim/automake-1.9.6/lib'
    Making install in Automake
    make[2]: Entering directory `/home/jim/automake-1.9.6/lib/Automake'
    Making install in tests
    make[3]: Entering directory `/home/jim/automake-1.9.6/lib/Automake/tests'
    make[4]: Entering directory `/home/jim/automake-1.9.6/lib/Automake/tests'
    make[4]: Nothing to be done for `install-exec-am'.
    make[4]: Nothing to be done for `install-data-am'.
    make[4]: Leaving directory `/home/jim/automake-1.9.6/lib/Automake/tests'
    make[3]: Leaving directory `/home/jim/automake-1.9.6/lib/Automake/tests'
    make[3]: Entering directory `/home/jim/automake-1.9.6/lib/Automake'
    rm -f Config.tmp Config.pm
    in=`echo Config.pm | sed 's/.[^.]*$//'`; sed -e 's,[@]APIVERSION[@],1.9,g' -e 's,[@]PACKAGE[@],automake,g' -e 's,[@]PERL[@],/usr/bin/perl,g' -e 's,[@]SHELL[@],/bin/sh,g' -e 's,[@]VERSION[@],1.9.6,g' -e "s,[@]configure_input[@],Generated from $in.in; do not edit by hand.,g" -e 's,[@]datadir[@],/usr/local/share,g' ./Config.in >Config.tmp
    chmod +x Config.tmp
    chmod a-w Config.tmp
    mv -f Config.tmp Config.pm
    make[4]: Entering directory `/home/jim/automake-1.9.6/lib/Automake'
    make[4]: Nothing to be done for `install-exec-am'.
    test -z "/usr/local/share/automake-1.9/Automake" || mkdir -p -- "/usr/local/share/automake-1.9/Automake"
    /usr/bin/install -c -m 644 'ChannelDefs.pm' '/usr/local/share/automake-1.9/Automake/ChannelDefs.pm'
    /usr/bin/install -c -m 644 'Channels.pm' '/usr/local/share/automake-1.9/Automake/Channels.pm'
    /usr/bin/install -c -m 644 'Condition.pm' '/usr/local/share/automake-1.9/Automake/Condition.pm'
    /usr/bin/install -c -m 644 'Configure_ac.pm' '/usr/local/share/automake-1.9/Automake/Configure_ac.pm'
    /usr/bin/install -c -m 644 'DisjConditions.pm' '/usr/local/share/automake-1.9/Automake/DisjConditions.pm'
    /usr/bin/install -c -m 644 'FileUtils.pm' '/usr/local/share/automake-1.9/Automake/FileUtils.pm'
    /usr/bin/install -c -m 644 'General.pm' '/usr/local/share/automake-1.9/Automake/General.pm'
    /usr/bin/install -c -m 644 'Item.pm' '/usr/local/share/automake-1.9/Automake/Item.pm'
    /usr/bin/install -c -m 644 'ItemDef.pm' '/usr/local/share/automake-1.9/Automake/ItemDef.pm'
    /usr/bin/install -c -m 644 'Location.pm' '/usr/local/share/automake-1.9/Automake/Location.pm'
    /usr/bin/install -c -m 644 'Options.pm' '/usr/local/share/automake-1.9/Automake/Options.pm'
    /usr/bin/install -c -m 644 'Rule.pm' '/usr/local/share/automake-1.9/Automake/Rule.pm'
    /usr/bin/install -c -m 644 'RuleDef.pm' '/usr/local/share/automake-1.9/Automake/RuleDef.pm'
    /usr/bin/install -c -m 644 'Struct.pm' '/usr/local/share/automake-1.9/Automake/Struct.pm'
    /usr/bin/install -c -m 644 'Variable.pm' '/usr/local/share/automake-1.9/Automake/Variable.pm'
    /usr/bin/install -c -m 644 'VarDef.pm' '/usr/local/share/automake-1.9/Automake/VarDef.pm'
    /usr/bin/install -c -m 644 'Version.pm' '/usr/local/share/automake-1.9/Automake/Version.pm'
    /usr/bin/install -c -m 644 'XFile.pm' '/usr/local/share/automake-1.9/Automake/XFile.pm'
    /usr/bin/install -c -m 644 'Wrap.pm' '/usr/local/share/automake-1.9/Automake/Wrap.pm'
    test -z "/usr/local/share/automake-1.9/Automake" || mkdir -p -- "/usr/local/share/automake-1.9/Automake"
    /usr/bin/install -c -m 644 'Config.pm' '/usr/local/share/automake-1.9/Automake/Config.pm'
    make[4]: Leaving directory `/home/jim/automake-1.9.6/lib/Automake'
    make[3]: Leaving directory `/home/jim/automake-1.9.6/lib/Automake'
    make[2]: Leaving directory `/home/jim/automake-1.9.6/lib/Automake'
    Making install in am
    make[2]: Entering directory `/home/jim/automake-1.9.6/lib/am'
    make[3]: Entering directory `/home/jim/automake-1.9.6/lib/am'
    make[3]: Nothing to be done for `install-exec-am'.
    test -z "/usr/local/share/automake-1.9/am" || mkdir -p -- "/usr/local/share/automake-1.9/am"
    /usr/bin/install -c -m 644 'ansi2knr.am' '/usr/local/share/automake-1.9/am/ansi2knr.am'
    /usr/bin/install -c -m 644 'check.am' '/usr/local/share/automake-1.9/am/check.am'
    /usr/bin/install -c -m 644 'clean-hdr.am' '/usr/local/share/automake-1.9/am/clean-hdr.am'
    /usr/bin/install -c -m 644 'clean.am' '/usr/local/share/automake-1.9/am/clean.am'
    /usr/bin/install -c -m 644 'compile.am' '/usr/local/share/automake-1.9/am/compile.am'
    /usr/bin/install -c -m 644 'configure.am' '/usr/local/share/automake-1.9/am/configure.am'
    /usr/bin/install -c -m 644 'data.am' '/usr/local/share/automake-1.9/am/data.am'
    /usr/bin/install -c -m 644 'dejagnu.am' '/usr/local/share/automake-1.9/am/dejagnu.am'
    /usr/bin/install -c -m 644 'depend.am' '/usr/local/share/automake-1.9/am/depend.am'
    /usr/bin/install -c -m 644 'depend2.am' '/usr/local/share/automake-1.9/am/depend2.am'
    /usr/bin/install -c -m 644 'distdir.am' '/usr/local/share/automake-1.9/am/distdir.am'
    /usr/bin/install -c -m 644 'footer.am' '/usr/local/share/automake-1.9/am/footer.am'
    /usr/bin/install -c -m 644 'header-vars.am' '/usr/local/share/automake-1.9/am/header-vars.am'
    /usr/bin/install -c -m 644 'header.am' '/usr/local/share/automake-1.9/am/header.am'
    /usr/bin/install -c -m 644 'install.am' '/usr/local/share/automake-1.9/am/install.am'
    /usr/bin/install -c -m 644 'inst-vars.am' '/usr/local/share/automake-1.9/am/inst-vars.am'
    /usr/bin/install -c -m 644 'java.am' '/usr/local/share/automake-1.9/am/java.am'
    /usr/bin/install -c -m 644 'lang-compile.am' '/usr/local/share/automake-1.9/am/lang-compile.am'
    /usr/bin/install -c -m 644 'lex.am' '/usr/local/share/automake-1.9/am/lex.am'
    /usr/bin/install -c -m 644 'library.am' '/usr/local/share/automake-1.9/am/library.am'
    /usr/bin/install -c -m 644 'libs.am' '/usr/local/share/automake-1.9/am/libs.am'
    /usr/bin/install -c -m 644 'libtool.am' '/usr/local/share/automake-1.9/am/libtool.am'
    /usr/bin/install -c -m 644 'lisp.am' '/usr/local/share/automake-1.9/am/lisp.am'
    /usr/bin/install -c -m 644 'ltlib.am' '/usr/local/share/automake-1.9/am/ltlib.am'
    /usr/bin/install -c -m 644 'ltlibrary.am' '/usr/local/share/automake-1.9/am/ltlibrary.am'
    /usr/bin/install -c -m 644 'mans-vars.am' '/usr/local/share/automake-1.9/am/mans-vars.am'
    /usr/bin/install -c -m 644 'mans.am' '/usr/local/share/automake-1.9/am/mans.am'
    /usr/bin/install -c -m 644 'multilib.am' '/usr/local/share/automake-1.9/am/multilib.am'
    /usr/bin/install -c -m 644 'program.am' '/usr/local/share/automake-1.9/am/program.am'
    /usr/bin/install -c -m 644 'progs.am' '/usr/local/share/automake-1.9/am/progs.am'
    /usr/bin/install -c -m 644 'python.am' '/usr/local/share/automake-1.9/am/python.am'
    /usr/bin/install -c -m 644 'remake-hdr.am' '/usr/local/share/automake-1.9/am/remake-hdr.am'
    /usr/bin/install -c -m 644 'scripts.am' '/usr/local/share/automake-1.9/am/scripts.am'
    /usr/bin/install -c -m 644 'subdirs.am' '/usr/local/share/automake-1.9/am/subdirs.am'
    /usr/bin/install -c -m 644 'tags.am' '/usr/local/share/automake-1.9/am/tags.am'
    /usr/bin/install -c -m 644 'texi-vers.am' '/usr/local/share/automake-1.9/am/texi-vers.am'
    /usr/bin/install -c -m 644 'texibuild.am' '/usr/local/share/automake-1.9/am/texibuild.am'
    /usr/bin/install -c -m 644 'texinfos.am' '/usr/local/share/automake-1.9/am/texinfos.am'
    /usr/bin/install -c -m 644 'yacc.am' '/usr/local/share/automake-1.9/am/yacc.am'
    make[3]: Leaving directory `/home/jim/automake-1.9.6/lib/am'
    make[2]: Leaving directory `/home/jim/automake-1.9.6/lib/am'
    make[2]: Entering directory `/home/jim/automake-1.9.6/lib'
    make[3]: Entering directory `/home/jim/automake-1.9.6/lib'
    make[3]: Nothing to be done for `install-exec-am'.
    test -z "/usr/local/share/automake-1.9" || mkdir -p -- "/usr/local/share/automake-1.9"
    /usr/bin/install -c -m 644 'COPYING' '/usr/local/share/automake-1.9/COPYING'
    /usr/bin/install -c -m 644 'INSTALL' '/usr/local/share/automake-1.9/INSTALL'
    /usr/bin/install -c -m 644 'texinfo.tex' '/usr/local/share/automake-1.9/texinfo.tex'
    /usr/bin/install -c -m 644 'ansi2knr.c' '/usr/local/share/automake-1.9/ansi2knr.c'
    /usr/bin/install -c -m 644 'ansi2knr.1' '/usr/local/share/automake-1.9/ansi2knr.1'
    /usr/bin/install -c -m 644 'config-ml.in' '/usr/local/share/automake-1.9/config-ml.in'
    test -z "/usr/local/share/automake-1.9" || mkdir -p -- "/usr/local/share/automake-1.9"
    /usr/bin/install -c -m 644 'config.guess' '/usr/local/share/automake-1.9/config.guess'
    /usr/bin/install -c -m 644 'config.sub' '/usr/local/share/automake-1.9/config.sub'
    /usr/bin/install -c -m 644 'install-sh' '/usr/local/share/automake-1.9/install-sh'
    /usr/bin/install -c -m 644 'mdate-sh' '/usr/local/share/automake-1.9/mdate-sh'
    /usr/bin/install -c -m 644 'missing' '/usr/local/share/automake-1.9/missing'
    /usr/bin/install -c -m 644 'mkinstalldirs' '/usr/local/share/automake-1.9/mkinstalldirs'
    /usr/bin/install -c -m 644 'elisp-comp' '/usr/local/share/automake-1.9/elisp-comp'
    /usr/bin/install -c -m 644 'ylwrap' '/usr/local/share/automake-1.9/ylwrap'
    /usr/bin/install -c -m 644 'acinstall' '/usr/local/share/automake-1.9/acinstall'
    /usr/bin/install -c -m 644 'depcomp' '/usr/local/share/automake-1.9/depcomp'
    /usr/bin/install -c -m 644 'compile' '/usr/local/share/automake-1.9/compile'
    /usr/bin/install -c -m 644 'py-compile' '/usr/local/share/automake-1.9/py-compile'
    /usr/bin/install -c -m 644 'symlink-tree' '/usr/local/share/automake-1.9/symlink-tree'
    make install-data-hook
    make[4]: Entering directory `/home/jim/automake-1.9.6/lib'
    chmod +x /usr/local/share/automake-1.9/config.guess
    chmod +x /usr/local/share/automake-1.9/config.sub
    chmod +x /usr/local/share/automake-1.9/install-sh
    chmod +x /usr/local/share/automake-1.9/mdate-sh
    chmod +x /usr/local/share/automake-1.9/missing
    chmod +x /usr/local/share/automake-1.9/mkinstalldirs
    chmod +x /usr/local/share/automake-1.9/elisp-comp
    chmod +x /usr/local/share/automake-1.9/ylwrap
    chmod +x /usr/local/share/automake-1.9/acinstall
    chmod +x /usr/local/share/automake-1.9/depcomp
    chmod +x /usr/local/share/automake-1.9/compile
    chmod +x /usr/local/share/automake-1.9/py-compile
    chmod +x /usr/local/share/automake-1.9/symlink-tree
    make[4]: Leaving directory `/home/jim/automake-1.9.6/lib'
    make[3]: Leaving directory `/home/jim/automake-1.9.6/lib'
    make[2]: Leaving directory `/home/jim/automake-1.9.6/lib'
    make[1]: Leaving directory `/home/jim/automake-1.9.6/lib'
    Making install in tests
    make[1]: Entering directory `/home/jim/automake-1.9.6/tests'
    make[2]: Entering directory `/home/jim/automake-1.9.6/tests'
    make[2]: Nothing to be done for `install-exec-am'.
    make[2]: Nothing to be done for `install-data-am'.
    make[2]: Leaving directory `/home/jim/automake-1.9.6/tests'
    make[1]: Leaving directory `/home/jim/automake-1.9.6/tests'
    linux-p8wc:/home/jim/automake-1.9.6 #
  29. Now try this:


    Quote:


    cd ccd2iso # change directory to ccd2iso

    ./configure --prefix=/usr/local # configure it and have it install to /usr/local

    make # compile it

    su - # become root / superuser

    make install # install it




    If all the requirements are installed it should work.[/code:1:4b644f2309]
  30. Congrats, you've just installed a couple of packages by hand, usually one of the trickier things to do when starting to use Linux. Now that automake and company is installed, you aren't bounded by whatever packages your distro provides, which is a good thing. Great instructions as always linux_0.

    If you haven't already, give the package-based installer a look, it can make installation easier.

    (Images from KDE, should be similar if you chose Gnome)
    Step 1: Open YaST


    Step 2: Select Software Management


    Step 3: Choose which Packages you want to install (can search or browse, up to you)


    Enjoy Linux!
  31. Beautiful screenshots :-D

    :trophy: :trophy:
  32. how to change from linux-p8wc:/home/jim # to adding on automaker- 1.9.6?
  33. Quote:
    how to change from linux-p8wc:/home/jim # to adding on automaker- 1.9.6?



    I hope I understood you correctly.





    man cd # for help

    man command_name # read the manual page / help for command_name

    cd # changes to your home directory ( $HOME ) aka ( ~ ) by default

    cd ~ # changes to your home directory ( $HOME ) aka ( ~ ) by default

    cd $HOME # changes to your home directory ( $HOME ) aka ( ~ ) by default

    cd ~username # changes to your home directory ( $HOME ) aka ( ~ ) by default

    cd /home/username # changes to /home/username


    cd directory_name # change to directory_name


    [/code:1:a135149e55]


    :-D
  34. ok I want to turn this from /home/jim to /home/jim/automake-1.9.6.tar.gz but do I use what you posted? Last time, when you posted a solution for my ccd2iso to be from /home/jim to /home/jim/ccd2iso-0.2.tar.gz

    When I used this linux-p8wc:/home/jim # cd /home/jim # changes directory /home/jim/automake-1.9.6.tar.gz
    linux-p8wc:/home/jim # ./configure --prefix=/usr/local # configure it and have it install to /usr/local

    It came out as this bash: ./configure: No such file or directory
    and it worked for the ccd2iso.0.2.tar.gz. Why isn't that working?
  35. Quote:
    ok I want to turn this from /home/jim to /home/jim/automake-1.9.6.tar.gz but do I use what you posted? Last time, when you posted a solution for my ccd2iso to be from /home/jim to /home/jim/ccd2iso-0.2.tar.gz

    When I used this linux-p8wc:/home/jim # cd /home/jim # changes directory /home/jim/automake-1.9.6.tar.gz
    linux-p8wc:/home/jim # ./configure --prefix=/usr/local # configure it and have it install to /usr/local

    It came out as this bash: ./configure: No such file or directory
    and it worked for the ccd2iso.0.2.tar.gz. Why isn't that working?



    You have to untar automake-1.9.6.tar.gz first


    You need to do something like this:



    cd /home/jim

    tar xzvf automake-1.9.6.tar.gz

    cd automake-1.9.6

    ./configure

    make

    make install

    cd ..

    cd ccd2iso

    ./configure

    make

    make install

    [/code:1:f4df49865e]
  36. When I did make, it give me the same error for missing aclocal-1.6 missing, even though I have tried your method. Is there a way I can get the aclocal to fuse with the ccd2iso-0.2.tar.gz? I have the correct version of it, but it says it's still missing.
  37. Quote:
    When I did make, it give me the same error for missing aclocal-1.6 missing, even though I have tried your method. Is there a way I can get the aclocal to fuse with the ccd2iso-0.2.tar.gz? I have the correct version of it, but it says it's still missing.



    You might want to try the method bmouring suggested above.

    YaST should take care of all the dependencies for you.

    :-D
  38. Quote:
    When I did make, it give me the same error for missing aclocal-1.6 missing, even though I have tried your method. Is there a way I can get the aclocal to fuse with the ccd2iso-0.2.tar.gz? I have the correct version of it, but it says it's still missing.



    You might want to try the method bmouring suggested above.

    YaST should take care of all the dependencies for you.

    :-D

    Uhhh, are you sure it doesn't uses your Suse 10.1 cds, because I don't have them now, and I don't if I need them.
  39. Quote:
    When I did make, it give me the same error for missing aclocal-1.6 missing, even though I have tried your method. Is there a way I can get the aclocal to fuse with the ccd2iso-0.2.tar.gz? I have the correct version of it, but it says it's still missing.



    You might want to try the method bmouring suggested above.

    YaST should take care of all the dependencies for you.

    :-D

    Uhhh, are you sure it doesn't uses your Suse 10.1 cds, because I don't have them now, and I don't if I need them.


    YaST should be able to install them from the online YaST repositories assuming you have a high speed connection.
  40. Ok, how do you install automake-1.6 on YaST?
  41. Quote:
    Ok, how do you install automake-1.6 on YaST?



    Goto:

    System -> YaST



    Click Software Management



    Look under each category until you find automake then select it and install




    Many thanks to bmouring for providing these screenshots :-D
  42. Should I just delete my current version in order to install 1.6 to try to work ccd2iso-0.2.tar.gz?
  43. Quote:
    Should I just delete my current version in order to install 1.6 to try to work ccd2iso-0.2.tar.gz?



    Don't worry about the automake tar you got.

    Just have YaST install whatever version is available via the YaST repositories.
  44. This is exactly the reason why I think that all easy-to-use distros should come with the following by default:

    automake
    gcc
    glibc
    kernel headers (either in the default /usr/src/linux/include or symlinked)
    etc.

    Doing so would make things much much easier.

    Or perhaps provide a stand-in script for make that checks for required packages, then outputs something to tell the user to use yum or apt-get or whatever to get the following packages:..... and if all the packages are in, then run the actual make. Just my $.02
  45. Quote:
    This is exactly the reason why I think that all easy-to-use distros should come with the following by default:

    automake
    gcc
    glibc
    kernel headers (either in the default /usr/src/linux/include or symlinked)
    etc.

    Doing so would make things much much easier.

    Or perhaps provide a stand-in script for make that checks for required packages, then outputs something to tell the user to use yum or apt-get or whatever to get the following packages:..... and if all the packages are in, then run the actual make. Just my $.02



    Aye :-D

    On most distros it's ( usually ) a simple process:



    yum install gcc automake kernel-devel

    apt-get install gcc

    apt-get install autmake

    # etc

    [/code:1:3f1ac94e49]
  46. Agreed that it isn't working with the kernel per se, but for very-first time users, it can seem extremely unfamiliar and arcane. I suppose it's a question of ease-of-use vs. teaching the system, since inevitably you will get your hands dirty when playing with Linus and the gang :)
  47. Quote:
    Agreed that it isn't working with the kernel per se, but for very-first time users, it can seem extremely unfamiliar and arcane. I suppose it's a question of ease-of-use vs. teaching the system, since inevitably you will get your hands dirty when playing with Linus and the gang :)



    Indeed :-D

    Linus and the gang have to improve on a couple of things mostly minor.

    Technically the distros are responsible for the user experience.

    I believe Linus and the kernel team are doing an excellent job and I very grateful to them for their hard work :-D

    Most distros are also doing a good job.
  48. Yeah, didn't really mean to insinuate that it was a task left to the kernel crew, more along the lines that if you play with their baby, no matter who's packaging it, you're going to have to get a little dirty. I should have been clearer before.
Ask a new question

Read More

Sound Blaster Creative