gcc 2.95.x would silently remove the ## in case where it was inappropriate. fcc 3.x complains instead. Anyway, as ftape is a kernel module, it may be safer to compile this with 2.95 as the kernel itself is still not happy with 3.x either.

As it is, I get another compilation error tucked in between the "invalid token" messages (and this one does not go away by using gcc 2.95):


In file included from ftape-tracing.h:35,
from ftape_syms.c:33:
../lowlevel/ftape-init.h: In function `ft_sigtest':
../lowlevel/ftape-init.h:70: error: structure has no member named `signal'


There are a few references on Google which advise to use the latest unstable tarball at [link|http://www.instmath.rwth-aachen.de/~heine/ftape/archives/ftape-4.x/unstable/|http://www.instmath....ape-4.x/unstable/] but even that seems not to compile under 2.4.18

I guess this is more the result of past cavalier attitude towards the ANSI C standard on the part of the FSF than anything else. v3 seems to stick closer to the standard with miscellaneous breakage as a result.