[arch-dev-public] gcc 4.5 bug - what to do?

Thomas Bächler thomas at archlinux.org
Tue Jul 20 17:00:06 EDT 2010

Am 20.07.2010 22:52, schrieb Firmicus:
> Yesterday I had bug report on a segfaulting binary for x86_64 that ships
> with texlive-bin in testing:
> http://bugs.archlinux.org/task/20199
> I have reported the bug upstream:
> https://sourceforge.net/tracker/?func=detail&aid=3031498&group_id=145640&atid=762580
> and as suspected it turned out to be a bug with gcc 4.5:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45008
> Now this means I have no means to include a working binary of dvisvgm
> for x86_64 in texlive-bin until that bug is resolved, since I cannot
> rely on gcc 4.4.x and no patch is available...
> What is the procedure you guys follow is such situations?

Run in circles, scream and shout at people. Then after some time start
crying. I have really no idea.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-dev-public/attachments/20100720/a6484b2b/attachment.bin>

More information about the arch-dev-public mailing list