This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: vfs tapset compilation error.


On Tue, 2011-01-25 at 17:10 -0800, Josh Stone wrote:
> I think we need a way to mark that certain paths should only be included
> via the main tapset path (PREFIX/systemtap/tapset or SYSTEMTAP_TAPSET).
>  There are many means, but perhaps something like just an empty
> ".systemtap_tapset" file could indicate that this path should not be
> searched via -I or XDG_DATA_DIRS.
> 
> You'd have to manually add this to old installations in order to get
> newer staps to ignore such paths, but at least this is a possible
> workaround.  Any other ideas?

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.

Cheers,

Mark


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]