Compiling without -no-gcc did the trick. Now I'm trying why we've
been compiling with that flag for years now....
On Mar 16, 2006, at 1:19 PM, Pete Wyckoff wrote:
[EMAIL PROTECTED] wrote on Thu, 16 Mar 2006 07:40 -0600:
So unless you're __GNUC__ you don't get the int64_t. Is there a way
around this?
Didn't I see you use a flag like -no-gcc? Maybe getting rid of
that, and presumably letting icc define __GNUC__ is good enough?
On a couple of my machines, we have (rhel as3) glibc-2.3.2-95.37
and (rh fc4) glibc-2.3.5-10.3 where those sections of the files
are a bit different in ways that look to me that int64_t should
get picked up. Even explicit "defined __INTEL_COMPILER && ..."
in features.h. I hate to say go upgrade, but if that's an option
that may fix things. You could alternatively edit your system header
files (blecch).
Is there some way to edit the romio source to force it to pick up
stdint.h before sys/types.h? If that's all it takes to fix it,
that seems like an easy patch to justify.
-- Pete
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
