Hi David, The -p option is implement by calling the preprocessor of the current compiler (with gcc, it is gcc -E). However, it still uses (on purpose) the emulation header files that CINT provides. In some circunstances, this prevents some initialization to be properly done. (they were exepected to be done by some system that are skipped). If you are example of such difficulties with gcc 3.2, please send them to me (so that we can fix/solve those). Cheers, Philippe. -----Original Message----- From: owner-roottalk@pcroot.cern.ch [mailto:owner-roottalk@pcroot.cern.ch]On Behalf Of David Chamont Sent: Thursday, July 03, 2003 4:43 PM To: roottalk@cern.ch Subject: [ROOT] implementation of rootcint -p Hi Root Gurus, Since I encounter many problems with rootcint when including some low level headers files from /usr/include, such as the dirent.h recently mentionned, I wonder how is implemented the rootcint -p option (preprocessing). Is it a root/cint home-made preprocessing, or is it relying on the default platform preprocessor ? Some undefined symbols let me think that some expected compiler macros definitions are lacking, such as __extension__ (I wrk with root 3.05.05 and linux 7.3 with gcc 3.2). David.
This archive was generated by hypermail 2b29 : Thu Jan 01 2004 - 17:50:13 MET