vfs tapset compilation error.

[Daniel Fishman]

On Wed, 26 Jan 2011 12:08:04 +0100, Mark Wielaard <mjw@redhat.com> wrote:

>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?