We had similar issues. We had to go back to our old 2.4.10 kernel which
still continues to work fine. We also tried 2.4.22, with seemingly no
ill effect. Just FYI.
On Fri, 2003-10-31 at 12:25, Chris Croswhite wrote:
> Has anyone seen this behavior?:
>
> Compiling source soucer code for another application, I realized that
> I
> did not configure correctly. So I removed the src dir and untar'ed
> the
> soruces again in the exact same directory. I than proceed to change
> the
> configure and recompiled the source. However, I got the exact same
> code
> size for libs and exectuable. So I tried the process over again,
> erased
> the original source code, untar'ed to the same dir, configured and
> then
> compiled again. But yet again I got the exact same exectuable and lib
> sizes which did not make sense.
>
> Figuring something was up, I moved the source to a different name and
> untar'ed again the original source, configured, and compiled, this
> time
> I got the correct result, a binary that had debugging information and
> libraries that were different (and correct).
>
> So my question, why did I see this!?!?!
>
> kernel 2.4.20 with aa patches (includes XFS support).
>
> TIA,
> Chris
--
Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Coremetrics, Inc.
|