[arch-dev-public] gcc 4.5 bug - what to do?
allan at archlinux.org
Wed Jul 21 04:41:11 EDT 2010
On 21/07/10 17:07, Firmicus wrote:
> On 20/07/2010 23:16, Pierre Schmitz wrote:
>> On Tue, 20 Jul 2010 23:00:06 +0200, Thomas Bächler
>> <thomas at archlinux.org> wrote:
>>> Am 20.07.2010 22:52, schrieb Firmicus:
>>>> Yesterday I had bug report on a segfaulting binary for x86_64 that
>>>> with texlive-bin in testing:
>>>> I have reported the bug upstream:
>>>> and as suspected it turned out to be a bug with gcc 4.5:
>>>> 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.
>> A more practical approach would be to compile the package with gcc 4.4
>> (there are mirrors containing old packages) and accept that this is an
>> ugly but temporary workaround. You should also open a bug report on our
>> bug tracker and link to the upstream one.
> Done: http://bugs.archlinux.org/task/20242
> but I see that Allan is already listed on the cc list upstream.
It is an interesting bug... It is fixed in gcc mainline. In fact, it
is fixed within a week of branching gcc-4.5, so it is weird that it has
not been backported.
More information about the arch-dev-public