Re: [cbm4linux-users] cbm4linux on Suse 8.2 & GCC 3.3
Brought to you by:
cbm4linux
From: Michael K. <mic...@pu...> - 2003-04-13 20:13:13
|
On Sun, 13 Apr 2003, Andreas wrote: > Sonntag, 13. April 2003 12:24 wrote Michael Klein: > > > > - This will fix the printf help output to get compiled without problems > > > on my 2.4.20 kernel and gcc-3.3. > > > > Thanks, will fix that! > > > > Are multi-line literals an error in gcc 3.3? (2.95 Doesn't complain at > > all here, while 3.0 prints a deprecation warning) > > > > Happy hacking, > > Michael > > Yes. I am a complete moron on C/C++, but it heavily errored with stuff like: > stray "\" on main.c in line XXX ... > > So it seems it doesnt support the Bash like line-breaking anymore. This form of line continuation is actually a preprocessor thing, and multi-line macros ('#define's) are ANSI AFAIK, so I'm quite a bit surprised about this particular error message ;-) Hm, did you unpack the sources on a DOS/W32 box? Source file with MS-DOS style newlines are likely to cause this error... Just an idea ;-) > I had similar problems getting the driver loaded, but the posted modules.conf > fixes that. > (Why doesnt: > modprobe parport ; insmod cbm lp=0 work, while: > modprobe lp ; rmmod lp ; insmod cbm lp=0 works fine ? Did you run "depmod -a" after installing? This should update the module dependencies... > lp module loads parport stuff the same way that the plain parport module is > loaded. Hmmm ... had quite some ambigous dmesg outputs aswell.) > > l8r > > -- Michael registered linux user #189917 -- http://counter.li.org/ |