Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
alsa - gcc version problem
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Multimedia
View previous topic :: View next topic  
Author Message
perchut2
Tux's lil' helper
Tux's lil' helper


Joined: 31 Mar 2003
Posts: 96
Location: Paris

PostPosted: Fri May 23, 2003 9:24 am    Post subject: alsa - gcc version problem Reply with quote

hi, i just recompiled my kernel, and i've got a problem recompiling alsa driver :


Code:
root@perchut2 mathieu # env ALSA_CARDS='emu10k1' emerge alsa-driver
Calculating dependencies ...done!
>>> emerge (1 of 1) media-sound/alsa-driver-0.9.3c to /
>>> md5 src_uri ;-) alsa-driver-0.9.3c.tar.bz2
>>> Unpacking source...
>>> Unpacking alsa-driver-0.9.3c.tar.bz2 to /var/tmp/portage/alsa-driver-0.9.3c/work
>>> Source unpacked.
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for i686-pc-linux-gnu-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 executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for i686-pc-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for a BSD compatible install... /bin/install -c
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for gcc option to accept ANSI C... none needed
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether time.h and sys/time.h may both be included... yes
checking whether gcc needs -traditional... no
checking for current directory... /var/tmp/portage/alsa-driver-0.9.3c/work/alsa-driver-0.9.3c
checking cross compile...
checking for directory with kernel source... /usr/src/linux
checking for kernel version... 2.4.20-gentoo-r2
checking for GCC version... Kernel compiler: version gcc 3.2.2 20030322 (Gentoo
Linux 1.4 3.2.2-r2) Used compiler: gcc (GCC) 3.2.2 20030322 (Gentoo Linux 1.4 3.2.2-r2)
Fatal error: Compiler type does not match
 
!!! ERROR: media-sound/alsa-driver-0.9.3c failed.
!!! Function src_compile, Line 57, Exitcode 1
!!! ./configure failed
 


i didn't upgrade gcc ... i compiled my kernel yesterday evening, and alsa this morning.

Thx for your help
_________________
Bonheur Amour Risette,
Labeur Labour Levrette.
Back to top
View user's profile Send private message
feardapenguin
Guru
Guru


Joined: 23 Jul 2003
Posts: 414
Location: Texas

PostPosted: Sat Sep 13, 2003 2:06 am    Post subject: Reply with quote

I just ran into the same problem with alsa-driver after upgrading gcc to 3.3.1. This is an old post. Has anyone gotten around this?

Code:
>>> Unpacking source...
>>> Unpacking alsa-driver-0.9.6.tar.bz2 to /var/tmp/portage/alsa-driver-0.9.6/work
 * Applying makefile.patch...                                                                                                                    [ ok ] * Applying wolk.patch...                                                                                                                        [ ok ]>>> Source unpacked.
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for i686-pc-linux-gnu-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 executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for i686-pc-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for a BSD compatible install... /bin/install -c
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for gcc option to accept ANSI C... none needed
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether time.h and sys/time.h may both be included... yes
checking whether gcc needs -traditional... no
checking for current directory... /var/tmp/portage/alsa-driver-0.9.6/work/alsa-driver-0.9.6
checking cross compile...
checking for directory with kernel source... /usr/src/linux
checking for kernel version... 2.4.20-gentoo-r7
checking for GCC version... Kernel compiler: colortail: invalid option -- ? Try 'colortail --help' for more information. Used compiler: gcc (GCC) 3.3.1 20030904 (Gentoo Linux 3.3.1-r1, propolice)
Fatal error: Compiler type does not match
Decoded kernel compiler: type= version=
Decoded used compiler: type=gcc version=3.3.1
Please, send ./configure output to <alsa-devel@alsa-project.org>
 
!!! ERROR: media-sound/alsa-driver-0.9.6 failed.
!!! Function src_compile, Line 61, Exitcode 1
!!! ./configure failed
Back to top
View user's profile Send private message
boris64
Veteran
Veteran


Joined: 04 Oct 2003
Posts: 1770
Location: Vechelde/Peine

PostPosted: Sun Oct 26, 2003 1:30 pm    Post subject: how to fix Reply with quote

hi, there is a workaround:

1.)
Code:
bash-2.05b# emerge -uD world
Calculating world dependencies ...done!
>>> emerge (1 of 3) media-sound/alsa-driver-0.9.8 to /
>>> md5 src_uri ;-) alsa-driver-0.9.8.tar.bz2
>>> Unpacking source...
>>> Unpacking alsa-driver-0.9.8.tar.bz2 to /var/tmp/portage/alsa-driver-0.9.8/work
 * Applying makefile.patch...                                                                                                                            [ ok ]
>>> Source unpacked.
oss
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for i686-pc-linux-gnu-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 executable suffix...
checking for object suffix...
[1]+  Stopped                 emerge -uD world


2.) -> at this place press [CTRL]+[Z] to pause emerging
(after -> applying patch! && before -> ggc-check!)

3.) now you go into
"/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8"

4.) open file "configure"

5.) goto line 828
Code:
if test "$my_compiler_type" != "$kernel_compiler_type"; then:


and insert before(!) this line
Code:
kernel_compiler_type="gcc"              #your(!) kenrel-compiler
kernel_compiler_version="3.3.1"                #your(!) kernel-compiler-version( 3.2.2?)


6.) now save file "configure"

7.) go back to console where you paused emerging

8.) enter
Code:
bash-2.05b# fg

-> and emerge will continue

9.) now emerge should work like below

Code:
checking for kernel version... 2.4.20-gentoo-r8
checking for GCC version... Kernel compiler:   Used compiler: gcc (GCC) 3.3.1 20030927 (Gentoo Linux 3.3.1-r5, propolice)



-> this is a known bug, i don't remember where i got this fixaround from (sorry)
this fix should work for any alsa-driver-version (0.9.7++)

-> if you need further information about this,
you should search the bug-database...

happy fixing ;)
_________________
boris64.net 200x / visit my desktop / try these tiny kernel patches ;)
Back to top
View user's profile Send private message
spendabuck
Apprentice
Apprentice


Joined: 28 Apr 2002
Posts: 256

PostPosted: Sun Oct 26, 2003 7:45 pm    Post subject: Re: how to fix Reply with quote

borisdigital wrote:
hi, there is a workaround:

1.)
Code:
bash-2.05b# emerge -uD world
Calculating world dependencies ...done!
>>> emerge (1 of 3) media-sound/alsa-driver-0.9.8 to /
>>> md5 src_uri ;-) alsa-driver-0.9.8.tar.bz2
>>> Unpacking source...
>>> Unpacking alsa-driver-0.9.8.tar.bz2 to /var/tmp/portage/alsa-driver-0.9.8/work
 * Applying makefile.patch...                                                                                                                            [ ok ]
>>> Source unpacked.
oss
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for i686-pc-linux-gnu-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 executable suffix...
checking for object suffix...
[1]+  Stopped                 emerge -uD world


2.) -> at this place press [CTRL]+[Z] to pause emerging
(after -> applying patch! && before -> ggc-check!)

3.) now you go into
"/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8"

4.) open file "configure"

5.) goto line 828
Code:
if test "$my_compiler_type" != "$kernel_compiler_type"; then:


and insert before(!) this line
Code:
kernel_compiler_type="gcc"              #your(!) kenrel-compiler
kernel_compiler_version="3.3.1"                #your(!) kernel-compiler-version( 3.2.2?)


6.) now save file "configure"

7.) go back to console where you paused emerging

8.) enter
Code:
bash-2.05b# fg

-> and emerge will continue

9.) now emerge should work like below

Code:
checking for kernel version... 2.4.20-gentoo-r8
checking for GCC version... Kernel compiler:   Used compiler: gcc (GCC) 3.3.1 20030927 (Gentoo Linux 3.3.1-r5, propolice)



-> this is a known bug, i don't remember where i got this fixaround from (sorry)
this fix should work for any alsa-driver-version (0.9.7++)

-> if you need further information about this,
you should search the bug-database...

happy fixing ;)


Thanks for the tip but I'm still confused about exatly where to insert "[code]kernel_compiler_type="gcc" #your(!) kenrel-compiler
kernel_compiler_version="3.3.1" #your(!) kernel-compiler-version( 3.2.2?) [/code" you wrote "goto line 828" whhiich is really line 2828 and then you wrote "and insert before(!) this line" - now this is where I'm confused. do I insert the workaround code in this line (if test "$my_compiler_type" != "$kernel_compiler_type"; then) or just before it?
thanks for your time
Back to top
View user's profile Send private message
JeffBlair
Apprentice
Apprentice


Joined: 23 May 2003
Posts: 175
Location: USA, Lone star state

PostPosted: Wed Oct 29, 2003 7:37 am    Post subject: Reply with quote

Put it right before the ! on the same line.
I just had to do it, and it worked great. Just make sure you put in your version of gcc. Type
Code:

gcc --version

at a prompt. I had gcc 3.3.2 installed.
Back to top
View user's profile Send private message
Leprechaun
n00b
n00b


Joined: 04 Oct 2003
Posts: 49
Location: Minnesota, USA

PostPosted: Thu Oct 30, 2003 1:34 am    Post subject: Reply with quote

I'm having the same problem, but I've been unable to solve it thus far using the above methods. I've tried a few variations of the code, and none of them have worked.

Code:
if test "$my_compiler_type" kernel_compiler_type="gcc" kernel_compiler_version="3.3.2" != "$kernel_compiler_type"; then


Code:
kernel_compiler_type="gcc"
kernel_compiler_version="3.3.2"
if test "$my_compiler_type" != "$kernel_compiler_type"; then


I haven't programmed in python before, so I really don't know any sort of debugging processes I could go through. Does anyone have any tips on either how to get this working, or where I could go to find out? Thanks in advance.
Back to top
View user's profile Send private message
Bor81
n00b
n00b


Joined: 31 Aug 2003
Posts: 68
Location: Kyiv, UA

PostPosted: Fri Oct 31, 2003 9:06 pm    Post subject: Reply with quote

I have some problem
my kernel compiler is not find :(

Quote:

checking for kernel version... 2.4.20-gentoo-r8
checking for GCC version... Kernel compiler: Used compiler: gcc (GCC) 3.3.2 20031022 (Gentoo Linux 3.3.2-r2, propolice)
Fatal error: Compiler type does not match
Decoded kernel compiler: type= version=
Decoded used compiler: type=gcc version=3.3.2
Back to top
View user's profile Send private message
Bor81
n00b
n00b


Joined: 31 Aug 2003
Posts: 68
Location: Kyiv, UA

PostPosted: Fri Oct 31, 2003 9:15 pm    Post subject: Re: how to fix Reply with quote

borisdigital wrote:
hi, there is a workaround:

2.) -> at this place press [CTRL]+[Z] to pause emerging
(after -> applying patch! && before -> ggc-check!)



Right IS
after applying patch (sources unpacked)
but before configure run
Back to top
View user's profile Send private message
Leprechaun
n00b
n00b


Joined: 04 Oct 2003
Posts: 49
Location: Minnesota, USA

PostPosted: Sat Nov 01, 2003 1:41 am    Post subject: Fixed Reply with quote

Well, I don't pretend to understand it, but I got mine to work. Turns out if I use kernel_compiler_version="3.3.1" (even though my compiler is 3.3.2) it works. Who knows. Anyone having the same problems I was, give that a shot. Best of luck.
Back to top
View user's profile Send private message
Cuchulainn
Tux's lil' helper
Tux's lil' helper


Joined: 10 Apr 2003
Posts: 107

PostPosted: Mon Nov 24, 2003 7:00 pm    Post subject: Reply with quote

Thanks for the workaround! Worked like a charm. Btw, it is in line 2828, not 828.

Cheers, Cuchu
Back to top
View user's profile Send private message
[FU] bEtA
n00b
n00b


Joined: 14 Feb 2003
Posts: 5
Location: Huber Heights, OH, USA

PostPosted: Tue Nov 25, 2003 8:18 pm    Post subject: My problem was in compile.h Reply with quote

I tried the above method with no luck. So I googled around for a while and found this solution that worked for my system.

My original /usr/local/src/include/linux/compile.h was not quite right. It looked like this (domain names have been changed to protect the innocent):
Code:
#define UTS_VERSION "#1 Tue Nov 25 10:35:21 EST 2003"
#define LINUX_COMPILE_TIME "10:35:21"
#define LINUX_COMPILE_BY "root"
#define LINUX_COMPILE_HOST "beta"
#define LINUX_COMPILE_DOMAIN "mystupidhomedomain.com"
#define LINUX_COMPILER ""

Notice the last line? Nothing is defined for LINUX_COMPILER. Once I used "gcc" in the LINUX_COMPILER field alsa-driver compiled beautifully.

Modified compile.h
Code:
#define UTS_VERSION "#1 Tue Nov 25 10:35:21 EST 2003"
#define LINUX_COMPILE_TIME "10:35:21"
#define LINUX_COMPILE_BY "root"
#define LINUX_COMPILE_HOST "beta"
#define LINUX_COMPILE_DOMAIN "mystupidhomedomain.com"
#define LINUX_COMPILER "gcc"


To give credit where credit is due, here is the article that helped me out: http://www.mail-archive.com/alsa-user@lists.sourceforge.net/msg09612.html

bEtA
Back to top
View user's profile Send private message
boris64
Veteran
Veteran


Joined: 04 Oct 2003
Posts: 1770
Location: Vechelde/Peine

PostPosted: Tue Nov 25, 2003 11:07 pm    Post subject: Reply with quote

nice!

worked like a charm and is much easier
than the other workaround...

;)
_________________
boris64.net 200x / visit my desktop / try these tiny kernel patches ;)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Multimedia All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum