Re: aufs vs. m68k conflict, please advice

2011-12-17 Thread Uwe Kleine-König
On Sat, Dec 17, 2011 at 07:00:00PM +, Thorsten Glaser wrote: > Uwe Kleine-K�nig dixit: Your mailer is broken. And it added: X-Message-Flag: Your mailer is broken. Get an update at http://www.washington.edu/pine/getpine/pcpine.html for free. to your mail :-) I guess it means you not m

Re: aufs vs. m68k conflict, please advice

2011-12-17 Thread Thorsten Glaser
Uwe Kleine-K�nig dixit: >On Sat, Dec 17, 2011 at 02:28:35PM +, Thorsten Glaser wrote: >> Maybe something like this? […] >> Just an idea of the moment, Well, it does make the thing compile with minimal effort. >IMHO the problem is that aufs provides an incomplete definition of >pr_fmt. Eithe

Re: aufs vs. m68k conflict, please advice

2011-12-17 Thread Uwe Kleine-König
On Sat, Dec 17, 2011 at 02:28:35PM +, Thorsten Glaser wrote: > Ben Hutchings dixit: > > >why other architectures get away with it. Maybe they just don't use > >pr_*() in headers. > > Maybe something like this? > > #define ack_bad_irq(irq) do { \ > pr_cr

Re: aufs vs. m68k conflict, please advice

2011-12-17 Thread Thorsten Glaser
Dixi quod… >Maybe something like this? With that, aufs indeed compiles and module-links. bye, //mirabilos -- “Having a smoking section in a restaurant is like having a peeing section in a swimming pool.” -- Edward Burr -- To UNSUBSCR

Re: aufs vs. m68k conflict, please advice

2011-12-17 Thread Ben Hutchings
On Sat, 2011-12-17 at 14:28 +, Thorsten Glaser wrote: > Ben Hutchings dixit: > > >why other architectures get away with it. Maybe they just don't use > >pr_*() in headers. > > Maybe something like this? > > #define ack_bad_irq(irq) do { \ > pr_crit("une

Re: aufs vs. m68k conflict, please advice

2011-12-17 Thread Thorsten Glaser
Ben Hutchings dixit: >why other architectures get away with it. Maybe they just don't use >pr_*() in headers. Maybe something like this? #define ack_bad_irq(irq) do { \ pr_crit("unexpected IRQ trap at vector %02x\n", \ (unsigned int)

Re: aufs vs. m68k conflict, please advice

2011-12-16 Thread Thorsten Glaser
Ben Hutchings dixit: >Maybe, but it should work just as long as AUFS_NAME is also defined in Right, looks like it. >advance. Not sure why that's not also provided on the command line, or Hrm. Can you forward this to the aufs people then, and maybe get us some fix? >why other architectures get

Re: aufs vs. m68k conflict, please advice

2011-12-16 Thread Ben Hutchings
On Fri, 2011-12-16 at 14:42 +, Thorsten Glaser wrote: > Hi, > > a build of linux-2.6 (3.2~rc4-1~experimental.1) with gcc-4.6 (to > check whether we can switch to it for the kernel, too) fails: [...] > /tmp/buildd/linux-2.6-3.2~rc4/debian/build/source_m68k_none/arch/m68k/include/asm/hardirq.h:

aufs vs. m68k conflict, please advice

2011-12-16 Thread Thorsten Glaser
Hi, a build of linux-2.6 (3.2~rc4-1~experimental.1) with gcc-4.6 (to check whether we can switch to it for the kernel, too) fails: […] LD [M] fs/affs/affs.o LD fs/aufs/built-in.o CC [M] fs/aufs/module.o In file included from /tmp/buildd/linux-2.6-3.2~rc4/debian/build/source_m68k_non