I don't recall do you have a package manager in slackware?

Ive used slapt-get and pkgtool to install software.

hmmm when I run the slapt-get -search arts command it comes back with

arts-1.5.2-i486-1 [inst=yes]: arts (Analog Realtime Synthesizer)

when i try to upgrade or update it just comes back to the slapt-get --help screen

when I run slapt-get -install arts-1.5.2-i486-1

it comes back with
slapt-get -search -install arts-1.5.2-i486-1
Reading Package Lists... Done
No such package: arts-1.5.2-i486-1
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Done



when i do slapt-get -search arts | grep no I get this

arts-1.4.2-i486-2_slack10.2 [inst=no]: Analog Realtime Synthesizer)

should I install this one?

right if it loaded gxine then can you try it from step 5

yes that would be help full

when i tried to dop step 11 it crashes so I ran artscontrol from a terminal and got this


whereis artscontrol
artscontrol: /opt/kde/bin/artscontrol
/opt/kde/bin/artscontrol
/opt/kde/bin/artscontrol: symbol lookup error: /opt/kde/lib/libartskde.so.1: undefined symbol: _ZTv0_n28_N4Arts16SynthModule_stub11autoSuspendEv

Why not forgo arts trickery and just get a build of audacity which can utilize ALSA directly?

Or you could compile it yourself (it’s not that hard). E.g.,
Just make sure the configure output says “Including support for ALSA” or something similar.

can you grab the output from alsa and use it as an input ?

^^ Do I need to uninstall my current Audacity install? Or is what you suggested just a supplemtent?


^
How would I do that?

that was a general question from me not a question to you. sorry for the confusion.

I guess it’s a supplement in that both builds can coexist simultaneously. The tgz most likely placed its files under “/usr/{bin,share,doc}” and the self-compiled one will most likely put its files under “/usr/local/{bin,share,doc}” instead. So as long as /usr/local/bin is in front of /usr/bin in your $PATH, the second build will actually be run when you type
into a terminal. Of course, to be sure you could always type the full path:

When I tried to run ./configure I get this:


./configure
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... /lib/cpp
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.





ls -l /lib/cpp
lrwxrwxrwx 1 root root 12 2006-05-20 17:16 /lib/cpp -> /usr/bin/cpp*

Something seems to be incorrect with your toolchain (which is odd for Slackware).
See what “config.log” says (it will most likely be a lot of text, but just look at the part around where the error occurs).

Make sure you have glibc headers installed (e.g., /usr/include/stdlib.h and friends should exist).

Just as a test, try compiling this program (type all text as shown into a terminal):
If the compilation fails (at the line beginning with “gcc”) with the error: “test.c:1: stdio.h: No such file or directory”, this means there is a problem with your glibc (you have the library files installed, but not the headers).

Another thing to check is for weird options in the environment variable CFLAGS (e.g., “-nostdinc” or something similar) which would inhibit the compilation. To check your current CFLAGS (and it’s relatives), type this in a terminal:

assuming I did what you suggested correctly it looks like it ran with no errors.


cat > test.c << EOF
> #include <stdio.h>
> int main()
> {
> printf("This is a test.\n");
> return 0;
> }
> EOF
$ gcc -o test test.c
$ ./test
This is a test.



echo $CFLAGS

echo $CPPFLAGS

echo $CXXFLAGS

$


the results of each of the echo command was a blank line.



ls -l /usr/include/stdlib.h
-rw-r--r-- 1 root root 33872 2006-03-13 03:43 /usr/include/stdlib.h



In file included from /usr/include/bits/posix1_lim.h:153,
from /usr/include/limits.h:144,
from /usr/lib/gcc/i486-slackware-linux/3.4.6/include/limits.h:122,
from /usr/lib/gcc/i486-slackware-linux/3.4.6/include/syslimits.h:7,
from /usr/lib/gcc/i486-slackware-linux/3.4.6/include/limits.h:11,
from conftest.c:9:
/usr/include/bits/local_lim.h:36:26: linux/limits.h: No such file or directory
configure:2789: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
| Syntax error



configure:2783: gcc -E conftest.c
In file included from /usr/include/bits/posix1_lim.h:153,
from /usr/include/limits.h:144,
from /usr/lib/gcc/i486-slackware-linux/3.4.6/include/limits.h:122,
from /usr/lib/gcc/i486-slackware-linux/3.4.6/include/syslimits.h:7,
from /usr/lib/gcc/i486-slackware-linux/3.4.6/include/limits.h:11,
from conftest.c:9:
/usr/include/bits/local_lim.h:36:26: linux/limits.h: No such file or directory
configure:2789: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
| Syntax error
configure:2783: gcc -E -traditional-cpp conftest.c
In file included from /usr/include/features.h:308,
from /usr/include/assert.h:36,
from conftest.c:11:
/usr/include/sys/cdefs.h:31: #error "You need a ISO C conforming compiler to use the glibc headers"



after that there are a lot more syntax errors. I can post the entire log if you want to see.

Yes, that confirms your problem is not with the glibc headers themselves.
That’s the problem… do you have a file named “/usr/include/linux/limits.h”? If not, you’ll need to download and install the kernel-headers package.