Hi, It's still required with the latest GCC. :(
Just wanting to know what Rin and Matt make of it before I write or update a HACKS entry. Best regards, Nat On Thu, 17 Jul 2025 21:06:47 Christos Zoulas wrote: > thanks! > > christos > > > On Jul 16, 2025, at 9:43 PM, Nat Sloss <nathanialsl...@yahoo.com.au> > > wrote: > > > > Hi Christos, > > > > (I've CC'd mrg and rin on this email also) > > > >> Is that a permanent thing? Should it be mentioned in HACKS? Is it a > >> compiler bug? > > > > Sorry for the late reply. > > > > I hope it's not permanent I'll will check this against the latest version > > of GCC when it's been added to the tree. > > > > I believe this is the same issue as metioned in hacks for libXfont2 > > (while it pertains to strsuftoll - which uses strncpy internally which > > is the same in this case). > > > > I'm hoping to pigyback the existing hacks entry and have written to Rin > > and Matthew about it - just waiting to see their thoughts on this. > > > > Hopefully with the GCC update this is no longer necessary. I will check > > when that happens. > > > > Best regards, > > > > Nat > > > > > > -- > > This message has been 'sanitized'. This means that potentially > > dangerous content has been rewritten or removed. The following > > log describes which actions were taken. > > > > Sanitizer (start="1752716624"): > > Split unusually long word(s) in header. > > > > SanitizeFile (filename="unnamed.txt", mimetype="Text/Plain"): > > Match (names="unnamed.txt", rule="9"): > > Enforced policy: accept > > > > Total modifications so far: 1 > > > > Anomy 0.0.0 : Sanitizer.pm > > $Id: Sanitizer.pm,v 1.94 2006/01/02 16:43:10 bre Exp $
