Mail Archives: djgpp/2000/06/10/01:26:38
> From: Krogg <krogg DOT no DOT to DOT spam AT gtcom DOT net>
> Newsgroups: comp.os.msdos.djgpp
> Date: Fri, 09 Jun 2000 21:21:07 -0400
>
> #undef DJGPP_MINOR
> #undef __DJGPP_MINOR
> #undef __DJGPP_MINOR__
>
> #define DJGPP_MINOR 2
> #define __DJGPP_MINOR 2
> #define __DJGPP_MINOR__ 2
>
> hmmmmmmm,I am going to infer that this means...
>
> Djgpp version 2 minor 2... == 2.02
Yes, this is 2.02. In that version, the results of profiling are
simply wrong: you'd get 100% of CPU time spent in the first function
that appears in the profile.
Upgrade to v2.03 and try again.
Also note that it is not enough to relink wothout -pg, to remove the
profiling code. You need also to recompile all the sources without
the -pg switch (since -pg is used both when compiling and when
linking).
> ITs getting to be that you got to be some kind of expert to use
> a compiler nowadays.
No, not really. Everything I said is in the FAQ, so you could be an
expert in reading the FAQ instead ;-)
> > One way of finding out what versions do you have installed, is to look
> > at the *.ver files in your manifest directory.
>
> Sounds like an chance for me to write a utility....unless
> a better one allready exists....
I think the zippo project does that.
However, it's very simple to know the versions just by looking at the
*.ver files' names. E.g., if you have djdev202.ver, you know you have
DJGPP v2.02 installed, even without looking inside the file.
- Raw text -