Re: vfs tapset compilation error.

[Mark Wielaard <mjw at redhat dot com>]

> >Good idea. We could just use an existing system tapset file like
> >null.stp for this. Or if you are afraid someone might put such a file
> >in
> >their own tapset include dir, use something a little more obscure
> >like
> ><arch>/nd_syscalls.stp.
> 
> Is the problem exists only in case of system paths? What would happen
> if
> user has private tapset (or maybe even just identically named function
> in different private tapsets) that could be found in multiple
> locations on
> XDG_DATA_DIRS paths?

Frank raised a somewhat similar issue in this bug report:
http://sourceware.org/bugzilla/show_bug.cgi?id=12443
Although that is about application/package installed tapsets in the
"system path".

But in general having multiple somewhat identical private tapsets on
the include path just doesn't work. Since as you say if you have
identical named functions they will clash. So, I do think it is only
a real problem with tapset in "system" dirs (and as Frank pointed out
if you put a "private" tapset in such a dir).

Cheers,

Mark