Hi dtrace people,
I''m new to the list. I''ve just finished the 3-day sun course
on
dtrace, and since my copmany is going to be rolling out a bunch of
python-based internal tools, I thought "hey, it''d be *great* if we
could use dtrace on these things since some of the are performance
sensetive". So I took the patches to 2.4.4, applied them to 2.5.1
(with those changes that were necessary - not too many) and tried to
build python with gcc. At this point, things started breaking down.
First, I shoudl say that python builds just fine with gcc. I''m using a
gcc that is different from the /usr/sfw version because that''s the
standard here, and we need things like the gnu f77 and fortarn library
to correctly link the things we need for this project. I did try
*really* hard to make this work with studio-11 since that''s our
preferred way to go, but that wasn''t working with a couple of the most
important modules we were building.
Anyway, now that I''ve got python-2.5.1 patches for dtrace that look
reasonable, I''ve been trying to build, which seems to go
smoothly. However, once I get the the phelper.d script, I''m lost. This
is what it looks like:
19:05 /var/tmp/python-build/Python-2.5.1+dtrace $ dtrace -o Python/phelper.o
-DPHELPER -I. -I./Include -C -G -s ./Python/phelper.d
dtrace: failed to compile script ./Python/phelper.d:
"/usr/include/time.h", line 301: syntax error near "{"
Can anyone explain how suns built-in C pre-processor can''t grok
/usr/include/time.h?
Thanks,
--
The 5 year plan:
In five years we''ll make up another plan.
Or just re-use this one.