---------- Forwarded message ---------- From: Rémy Oudompheng<oudomphe@phare.normalesup.org> Date: 2010/7/20 Subject: Re: [arch-dev-public] gcc 4.5 bug - what to do? To: Public mailing list for Arch Linux development <arch-dev-public@archlinux.org>

On 2010/7/20, Firmicus<Firmicus@gmx.net> wrote:

...

Hi guys,

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... Can't we use the random patch I posted as a follow-up to the bug report (until GCC gets fixed...) ? Ah thanks, I'll look at it. (I had not noticed your patch when I wrote the above). But even if it works I'd prefer to ask the dev of dvisvgm first for his expert opinion on this

Another solution would be to use clang++ ;) Given the complexity and the integrated nature of the texlive build environment, that would probably be hard to achieve locally. A cleaner approach would be to (temporarily)

On 20/07/2010 23:44, Rémy Oudompheng wrote: patch. I've already asked him actually. package dvisvgm separately and disable it in the texlive-bin configuration. I'll contact you offlist on this if this becomes a necessity ;) Rémy, thanks for the patch btw ;) F