4.8.0 Release...

[thomas bonfort]

Is that the bug I talked to you about a couple of months ago (I also
sent you a mapfile and shapefile that consistently segfaulted for me)?
If this isn't the case could you also see with Thomas Boutell to get
the one line patch in 2.0.34 (I posted the patch to the mailing list
here:
http://www.nabble.com/Re%3A-UMN_MAPSERVER-USERS-antialiasing-line-features..-p1303400.html
cheers,
tb
On 1/5/06, Steve Lime <steve.lime at dnr.state.mn.us> wrote:
> By trivial I mean 1 line of code in gd.c... One other option would be to implement the busted functions in GD within MapServer (fixed of course) for the time being. Could introduce licensing headaches though.
>
> Steve
>
> >>> Stephen Woodbridge <woodbri at swoodbridge.com> 01/05/06 10:09 AM >>>
> Anti aliased lines are my primary (only?) reason for moving to 4.8. So
> anything that we can do to facilitate distributing a patch or whatever
> would help. It will take longer than whenever for the new gd release to
> appear on all the distribution packages :(
>
> -Steve
>
> Steve Lime wrote:
> > Hi folks: Sean and I found a bug in the antialiasing code (single
> > pixel lines) within GD that causes segfaults under certain
> > circumstances. It's a problem with the way they implement clipping
> > for aa lines. I contacted Thomas Boutell late last night and actually
> > heard back this morning. The issue has been fixed in the upcoming GD
> > 2.0.34 release (no date on that release).
> >
> > How should we handle on our end? This does not affect the fuzzy brush
> > code.
> >
> > I was thinking about asking for a preview release of 2.0.34 and then
> > perhaps adjusting the configure process to detect that version. The
> > patch to fix GD is trivial so we could even offer a patched version
> > (or the patch itself) for folks that want to use aa.
> >
> > Steve
> >
>