On 29 September 2010 08:07, #SINHA SHARAD# wrote: > Hi, > > I presume this happens because the glibc with gcc 4.2.1 is smarter than the > one with gcc 3.2.2. Hence, what was missed during execution with 3.2.2 was > caught in 4.2.1
N.B. glibc does not come with GCC, you can generally use a new GCC on a machine with an old glibc and vice versa - they are separate projects and are released independently.
