More compile errors, 2.4.27-rc3 with gcc-3.4.0

More compile errors, 2.4.27-rc3 with gcc-3.4.0

[haiquy]

Hi,

just in case someone find it usefull I attached the nearly complete
errors and to continue my last post.
kernel 2.4.27-rc3 with the gcc-2.4.0 compile fix patch

gcc-4 -D__KERNEL__ -I/home/linux-2.4.27-rc3/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fno-strength-reduce -ffast-math -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -fno-unit-at-a-time -DMODULE -DHISAX_MAX_CARDS=8 -nostdinc -iwithprefix include -DKBUILD_BASENAME=st5481_usb  -c -o st5481_usb.o st5481_usb.c
st5481_usb.c: In function `usb_next_ctrl_msg':
st5481_usb.c:51: error: parse error before "__FUNCTION__"
st5481_usb.c: In function `usb_ctrl_msg':
st5481_usb.c:67: error: parse error before "__FUNCTION__"
st5481_usb.c: In function `usb_ctrl_complete':
st5481_usb.c:134: error: parse error before "__FUNCTION__"
st5481_usb.c: In function `usb_int_complete':
st5481_usb.c:188: error: parse error before "__FUNCTION__"
st5481_usb.c: In function `st5481_setup_usb':
st5481_usb.c:244: error: parse error before "__FUNCTION__"
st5481_usb.c:253: error: parse error before "__FUNCTION__"
st5481_usb.c:263: error: parse error before "__FUNCTION__"
st5481_usb.c: In function `st5481_start':
st5481_usb.c:360: error: parse error before "__FUNCTION__"
st5481_usb.c: In function `usb_in_complete':
st5481_usb.c:474: error: parse error before "__FUNCTION__"
st5481_usb.c:504: error: parse error before "__FUNCTION__"
st5481_usb.c:510: error: parse error before "__FUNCTION__"
st5481_usb.c:512: error: parse error before "__FUNCTION__"
st5481_usb.c:514: error: parse error before "__FUNCTION__"
st5481_usb.c:522: error: parse error before "__FUNCTION__"
st5481_usb.c: In function `st5481_start_rcv':
st5481_usb.c:609: error: parse error before "__FUNCTION__"
st5481_usb.c:612: error: parse error before "__FUNCTION__"
make[3]: *** [st5481_usb.o] Error 1
make[3]: Leaving directory `/home/linux-2.4.27-rc3/drivers/isdn/hisax'
make[2]: *** [_modsubdir_hisax] Error 2
make[2]: Leaving directory `/home/linux-2.4.27-rc3/drivers/isdn'
make[1]: *** [_modsubdir_isdn] Error 2
make[1]: Leaving directory `/home/linux-2.4.27-rc3/drivers'
make: *** [_mod_drivers] Error 2


gcc-4 -D__KERNEL__ -I/home/linux-2.4.27-rc3/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fno-strength-reduce -ffast-math -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -fno-unit-at-a-time -DMODULE  -nostdinc -iwithprefix include -DKBUILD_BASENAME=ns83820  -c -o ns83820.o ns83820.c
ns83820.c:591: error: conflicting types for 'rx_refill_atomic'
ns83820.c:589: error: previous declaration of 'rx_refill_atomic' was here
ns83820.c:591: error: conflicting types for 'rx_refill_atomic'
ns83820.c:589: error: previous declaration of 'rx_refill_atomic' was here
ns83820.c:612: error: conflicting types for 'phy_intr'
ns83820.c:610: error: previous declaration of 'phy_intr' was here
ns83820.c:612: error: conflicting types for 'phy_intr'
ns83820.c:610: error: previous declaration of 'phy_intr' was here
ns83820.c:797: error: conflicting types for 'ns83820_rx_kick'
ns83820.c:795: error: previous declaration of 'ns83820_rx_kick' was here
ns83820.c:797: error: conflicting types for 'ns83820_rx_kick'
ns83820.c:795: error: previous declaration of 'ns83820_rx_kick' was here
ns83820.c:818: error: conflicting types for 'rx_irq'
ns83820.c:816: error: previous declaration of 'rx_irq' was here
ns83820.c:818: error: conflicting types for 'rx_irq'
ns83820.c:816: error: previous declaration of 'rx_irq' was here
ns83820.c:589: warning: 'rx_refill_atomic' declared `static' but never defined
ns83820.c:610: warning: 'phy_intr' declared `static' but never defined
ns83820.c:795: warning: 'ns83820_rx_kick' declared `static' but never defined
ns83820.c:816: warning: 'rx_irq' declared `static' but never defined
ns83820.c:1708: warning: 'ns83820_probe_phy' defined but not used
make[2]: *** [ns83820.o] Error 1
make[2]: Leaving directory `/home/linux-2.4.27-rc3/drivers/net'
make[1]: *** [_modsubdir_net] Error 2
make[1]: Leaving directory `/home/linux-2.4.27-rc3/drivers'
make: *** [_mod_drivers] Error 2


gcc-4 -D__KERNEL__ -I/home/linux-2.4.27-rc3/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fno-strength-reduce -ffast-math -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -fno-unit-at-a-time -DMODULE  -nostdinc -iwithprefix include -DKBUILD_BASENAME=core  -c -o core.o core.c
core.c:410: error: conflicting types for '__rfcomm_dlc_throttle'
/home/linux-2.4.27-rc3/include/net/bluetooth/rfcomm.h:265: error: previous declaration of '__rfcomm_dlc_throttle' was here
core.c:410: error: conflicting types for '__rfcomm_dlc_throttle'
/home/linux-2.4.27-rc3/include/net/bluetooth/rfcomm.h:265: error: previous declaration of '__rfcomm_dlc_throttle' was here
core.c:421: error: conflicting types for '__rfcomm_dlc_unthrottle'
/home/linux-2.4.27-rc3/include/net/bluetooth/rfcomm.h:266: error: previous declaration of '__rfcomm_dlc_unthrottle' was here
core.c:421: error: conflicting types for '__rfcomm_dlc_unthrottle'
/home/linux-2.4.27-rc3/include/net/bluetooth/rfcomm.h:266: error: previous declaration of '__rfcomm_dlc_unthrottle' was here
make[3]: *** [core.o] Error 1
make[3]: Leaving directory `/home/linux-2.4.27-rc3/net/bluetooth/rfcomm'
make[2]: *** [_modsubdir_rfcomm] Error 2
make[2]: Leaving directory `/home/linux-2.4.27-rc3/net/bluetooth'
make[1]: *** [_modsubdir_bluetooth] Error 2
make[1]: Leaving directory `/home/linux-2.4.27-rc3/net'
make: *** [_mod_net] Error 2

// As this bluetooth module is essential then I disabled all blue tooth support to continue so not sure if any other file in bluetooth has compiling problem or not.

Best regards,

Steve Kieu

Re: More compile errors, 2.4.27-rc3 with gcc-3.4.0

[Mikael Pettersson]

On Sun, 25 Jul 2004 22:30:13 +0000 (UTC), haiquy@yahoo.com wrote:
>kernel 2.4.27-rc3 with the gcc-2.4.0 compile fix patch
>
>gcc-4 -D__KERNEL__ -I/home/linux-2.4.27-rc3/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fno-strength-reduce -ffast-math -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -fno-unit-at-a-time -DMODULE -DHISAX_MAX_CARDS=8 -nostdinc -iwithprefix include -DKBUILD_BASENAME=st5481_usb  -c -o st5481_usb.o st5481_usb.c
>st5481_usb.c: In function `usb_next_ctrl_msg':
>st5481_usb.c:51: error: parse error before "__FUNCTION__"

__FUNCTION__ string concatenation errors

>gcc-4 -D__KERNEL__ -I/home/linux-2.4.27-rc3/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fno-strength-reduce -ffast-math -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -fno-unit-at-a-time -DMODULE  -nostdinc -iwithprefix include -DKBUILD_BASENAME=ns83820  -c -o ns83820.o ns83820.c
>ns83820.c:591: error: conflicting types for 'rx_refill_atomic'
>ns83820.c:589: error: previous declaration of 'rx_refill_atomic' was here

FASTCALL/fastcall mismatches

>gcc-4 -D__KERNEL__ -I/home/linux-2.4.27-rc3/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fno-strength-reduce -ffast-math -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -fno-unit-at-a-time -DMODULE  -nostdinc -iwithprefix include -DKBUILD_BASENAME=core  -c -o core.o core.c
>core.c:410: error: conflicting types for '__rfcomm_dlc_throttle'
>/home/linux-2.4.27-rc3/include/net/bluetooth/rfcomm.h:265: error: previous declaration of '__rfcomm_dlc_throttle' was here

FASTCALL/fastcall mismatches

These problems are fixed in
<http://www.csd.uu.se/~mikpe/linux/patches/2.4/patch-gcc340-fixes-v4-2.4.27-rc3>
or apply the incremental patch below. The fixes are trivial
and correspond to changes already present in the 2.6 kernel.

/Mikael

--- linux-2.4.27-rc3/drivers/isdn/hisax/st5481.h.~1~	2004-07-25 13:26:44.000000000 +0200
+++ linux-2.4.27-rc3/drivers/isdn/hisax/st5481.h	2004-07-25 13:44:20.000000000 +0200
@@ -219,13 +219,13 @@
 #define L1_EVENT_COUNT (EV_TIMER3 + 1)
 
 #define ERR(format, arg...) \
-printk(KERN_ERR __FILE__ ": " __FUNCTION__ ": " format "\n" , ## arg)
+printk(KERN_ERR "%s:%s: " format "\n" , __FILE__,  __FUNCTION__ , ## arg)
 
 #define WARN(format, arg...) \
-printk(KERN_WARNING __FILE__ ": " __FUNCTION__ ": " format "\n" , ## arg)
+printk(KERN_WARNING "%s:%s: " format "\n" , __FILE__,  __FUNCTION__ , ## arg)
 
 #define INFO(format, arg...) \
-printk(KERN_INFO __FILE__ ": " __FUNCTION__ ": " format "\n" , ## arg)
+printk(KERN_INFO "%s:%s: " format "\n" , __FILE__,  __FUNCTION__ , ## arg)
 
 #include "isdnhdlc.h"
 #include "fsm.h"
--- linux-2.4.27-rc3/drivers/net/ns83820.c.~1~	2004-02-18 15:16:23.000000000 +0100
+++ linux-2.4.27-rc3/drivers/net/ns83820.c	2004-07-25 13:34:50.000000000 +0200
@@ -587,7 +587,7 @@
 }
 
 static void FASTCALL(rx_refill_atomic(struct ns83820 *dev));
-static void rx_refill_atomic(struct ns83820 *dev)
+static void fastcall rx_refill_atomic(struct ns83820 *dev)
 {
 	rx_refill(dev, GFP_ATOMIC);
 }
@@ -608,7 +608,7 @@
 }
 
 static void FASTCALL(phy_intr(struct ns83820 *dev));
-static void phy_intr(struct ns83820 *dev)
+static void fastcall phy_intr(struct ns83820 *dev)
 {
 	static char *speeds[] = { "10", "100", "1000", "1000(?)", "1000F" };
 	u32 cfg, new_cfg;
@@ -793,7 +793,7 @@
 }
 
 static void FASTCALL(ns83820_rx_kick(struct ns83820 *dev));
-static void ns83820_rx_kick(struct ns83820 *dev)
+static void fastcall ns83820_rx_kick(struct ns83820 *dev)
 {
 	/*if (nr_rx_empty(dev) >= NR_RX_DESC/4)*/ {
 		if (dev->rx_info.up) {
@@ -814,7 +814,7 @@
  *	
  */
 static void FASTCALL(rx_irq(struct ns83820 *dev));
-static void rx_irq(struct ns83820 *dev)
+static void fastcall rx_irq(struct ns83820 *dev)
 {
 	struct rx_info *info = &dev->rx_info;
 	unsigned next_rx;
--- linux-2.4.27-rc3/net/bluetooth/rfcomm/core.c.~1~	2004-04-14 20:22:21.000000000 +0200
+++ linux-2.4.27-rc3/net/bluetooth/rfcomm/core.c	2004-07-25 13:41:03.000000000 +0200
@@ -406,7 +406,7 @@
 	return len;
 }
 
-void __rfcomm_dlc_throttle(struct rfcomm_dlc *d)
+void fastcall __rfcomm_dlc_throttle(struct rfcomm_dlc *d)
 {
 	BT_DBG("dlc %p state %ld", d, d->state);
 
@@ -417,7 +417,7 @@
 	rfcomm_schedule(RFCOMM_SCHED_TX);
 }
 
-void __rfcomm_dlc_unthrottle(struct rfcomm_dlc *d)
+void fastcall __rfcomm_dlc_unthrottle(struct rfcomm_dlc *d)
 {
 	BT_DBG("dlc %p state %ld", d, d->state);