Re: DHCP server bug (miscompiled by GCC compiler)

On Fri, Sep 09, 2005 at 10:56:49AM -0400, David L. Parsley wrote:
> On Fri, 2005-09-09 at 09:40 -0500, Ed Wilts wrote:
> > On Fri, Sep 09, 2005 at 09:44:24AM -0400, David L. Parsley wrote:
> > > On Fri, 2005-09-09 at 08:24 +0200, Milan Ker=C5=A1l=C3=A1ger wrote:
> > > It's spelled out pretty nicely here:
> > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=3D150267
> > >=20
> > > So it looks like gcc > 3.4.3-13 (Tao 4 now at 3.4.3-22.1) should fi=
x
> > > this.  I've recompiled w/ current gcc and put a version-bumped buil=
d in
> > > a new 'testing' repo.
> > >=20
> > > Milan, could you please check these out and get back to me, before =
I
> > > make an errata?
> >=20
> > Doesn't this generate a fork from the RHEL releases?
>=20
> Yes :-/
>=20
> >   Can we tell which
> > gcc Red Hat compiled their current shipping version with?
>=20
> Sure, it's right there in the bug report:
> The dhcp-3.0.1-12_EL package was built on Nov 17th 2004,
> with compiler 3.4.3-2.EL4 and that is the version that=20
> was tested, when no such problems were found .
>=20
> That compiler isn't available anywhere I can find, though it might have
> been in RHEL4 beta1 (RHEL4 b2 had gcc-3.4.3-9, which has the bug).

Interesting.  I've heard claims before that a rebuild of the sources
doesn't necessarily get you the equivalent of the binaries because you
can't guarantee the build order but I didn't realize that Red Hat used
compilers that weren't publicly available.  I thought it was FUD before
but I guess it really is true that the rebuilds aren't bug for bug
compatible.

Not that it bothers me much but I like to have all the facts in hand if
I can. =20

Thanks,
        .../Ed

--=20
Ed Wilts, Mounds View, MN, USA
mailto:[email protected]