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]

request to add arch dir to stap include_path


I think this was brought up at the F2F but do not recall a definitive solution...
Not questioning the merit of the (script language) enhancement to support %( CONDITION %? TRUE-TOKENS %: FALSE-TOKENS %) pre-processor statements. However I can foresee probe script code becoming difficult to manage (or at least ugly) if entangled between a lot of 'ifdefs'. I think it would be appropriate - and consistent with Linux's traditional way of ordering source code - if (arch specific)
tapset code was able to be placed in tapset/arch/ directory (eg. SYSTEMTAP_TAPSET=$SRCDIR/tapset/arch/`uname -i`/*.stp)


--
Kevin Stafford
DES 2 | MS 2M3
Beaverton - OR
Linux Technology Center
IBM Systems & Technology
Phone: 1-503-578-3039
Email: kevinrs@us.ibm.com




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