Re: Unix-domain sockets - abstract addresses

Keith Owens (kaos@ocs.com.au)
Mon, 12 Aug 2002 13:20:09 +1000


On Sun, 11 Aug 2002 19:59:06 -0700 (PDT),
"David S. Miller" <davem@redhat.com> wrote:
>I don't like this solution, please fix this right and get rid of the
>limitations at their source.
>
>If I name a module "foo" and this causes "fo" to become a defined
>CPP symbol in when compiling the sources for that module, that is
>completely broken!
>
>net/unix is just a trite example. How about a driver for device "foo"
>that has a member "foo" in one of it's structures? They have to get
>this undef thing too or rename their module, that's rediculious.

I think you misunderstood the problem. Calling a driver "foo" does not
make "foo" a cpp symbol. The problem here is that 'unix' is a driver
name and also a symbol that is defined by gcc.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/