You are not logged in.
Hi All
I was having a bit of trouble with alsa-driver after updating yesterday.
[04/29/04 18:11] upgraded alsa-driver (1.0.4-2 -> 1.0.4-3)
[04/29/04 18:11] upgraded freetype2 (2.1.7-1 -> 2.1.8-1)
[04/29/04 18:11] upgraded gcc (3.3.3-1 -> 3.4.0-1)
[04/29/04 18:11] upgraded groff (1.19-1 -> 1.19-2)
[04/29/04 18:11] upgraded perl (5.8.3-3 -> 5.8.4-1)
[04/29/04 18:11] upgraded perlxml (2.34-2 -> 2.34-3)
[04/29/04 18:11] upgraded samba (3.0.2-3 -> 3.0.3-1)
[04/29/04 18:12] upgraded xfree86 (4.4.0-1 -> 4.4.0-2)
I have a custom kernel (2.4.26) and alsa was working fine and alsa-driver was updated by pacman. After the update, I recompiled alsa-drivers using makepkg and rebooted and still had also problems. This is similar to the thread below:
http://bbs.archlinux.org/viewtopic.php?t=4267
So my next step was to recompile the kernel. I did this because I noticed that gcc was updated from v 3.3.3 to v 3.4. My uninformed thinking was that there might be some interaction between gcc 3.3.3 and 3.4 code. I did the usual "make mrpoper" etc and simply rebuilt my kernel using gcc3.4. To my surprise, the build failed. Below is a partial output from the console.
Is there something that I am missing?
Thanks
Kevin
make[2]: Entering directory `/usr/src/linux-2.4.26/kernel'
gcc -D__KERNEL__ -I/usr/src/linux-2.4.26/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix include -DKBUILD_BASENAME=sched -fno-omit-frame-pointer -c -o sched.o sched.c
sched.c:213: error: conflicting types for 'reschedule_idle'
sched.c:210: error: previous declaration of 'reschedule_idle' was here
sched.c:213: error: conflicting types for 'reschedule_idle'
sched.c:210: error: previous declaration of 'reschedule_idle' was here
sched.c:371: error: conflicting types for 'wake_up_process'
/usr/src/linux-2.4.26/include/linux/sched.h:603: error: previous declaration of 'wake_up_process' was here
Offline
Yes, we had real trouble getting 2.4 to compile as well. Check out the patches that are included in abs and see if you can get any farther then.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
Thanks, I'll take a look.
Offline
Well, the patch workded fine and I was able to compile 2.4.26 with gcc 3.4. Though, I am still having troubles. I am still getting the same errors when I compile alsa-driver (I referebce the thread above).
In general, is there a way to downgrade to gcc3.3.3 - and prevent it from being upgraded? I ask because I am using one comercial package that uses a vendor supplied model to read a USB dongle. It will never work with gcc3.4 compiled kernels and it will be a while before they supply a newer module.
Offline
I would also like to take a step backward on gcc, anything to get my sound and video modules loaded again :x
Offline
I simply download gcc 3.3.3-1 and used pacman to install it. I rebooted before I used it.
wget ftp://ftp.ibiblio.org/pub/linux/distrib … pkg.tar.gz
Kev
Offline
I just want to add a note that I upgraded back to gcc 3.4 after compiling my kernels and modules. Downgrading breaks other things in arch.
Everything is now in good working order with my arch box.
Offline