Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi again,
I'm starting a new thread with my Alsa-problems, as I am now trying to sort them out properly.
I am trying to compile Alsa 1.0.6 and have no luck. I compiled alsa-driver ok, using --with-cards=emu10k1x.
When running ./configure for alsa-lib it gives me this output and does not complete the job:
[root@home alsa-lib-1.0.6]# ./configure
checking build system type... i686-pc-linux
checking host system type... i686-pc-linux
checking target system type... i686-pc-linux
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 gcc... gcc
checking for C compiler default output... 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 ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
[root@home alsa-lib-1.0.6]#
/lib/cpp exists.
Some system info:
Mandrake 10.1 Community
KDE 3.2
gcc 3.4.1-3mdk
Kernel 2.6.8.1-10mdk
Dell SB soundcard (hence the emu10k1x)
I'll post config.log if requested. It's quite big.
And where do I get that? It's not on my Mandrake cd's. It seems to be a c++ compiler, but as I understand it c++ is included in gcc, so why do I need more? I'm no programmer, and I don't want to be one, I just want things to work.
You need the g++ package, it's so you can compile it. You don't need to be a programmer but alsa needs it cause g++ is the gnu c++ compiler and gcc is the gnu c compiler, two different things. If it's not on your CDs maybe you can find it on an rpm site or whatever mandrakes default way is to download new packages
Well, according to the gno homepage and everywhere I have seen, g++ is a part of gcc, so they are not two different things. And I have gcc installed allready, so I don't understand why I need more.
And about being a programmer, it's just that I want things to work without worrying about stupid things like compilers and stuff. I guess I'll be leaving this stupid os soon and go back to Windows completely. I just want sound out of my speakers, it shouldn't have to take several months of work to get it. I mean, there are some good things in Linux, but the average user doesn't have time or knowledge to get a system running properly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.