[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#624696: marked as done (exim4: broken build with gcc-4.6)

Your message dated Tue, 24 May 2011 13:03:25 +0200
with message-id <20110524110325.GA27774@volta.aurel32.net>
and subject line Re: memmove
has caused the Debian Bug report #619963,
regarding exim4: broken build with gcc-4.6
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
619963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619963
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: exim4
Version: 4.75-2
Severity: serious

Hello,

when built with gcc-4.6 on i386 the resulting binary is broken:

------------------
./build-Linux-x86_64/exim -C /tmp/foo -be '${if bool{0}{yes}{no}} X
${if !bool{0}{yes}{no}}'
Segmentation fault
------------------

It builds correctly

* without hardening_wrapper or disabled hardening_wrapper (i.e. not
  setting DEB_BUILD_HARDENING=1)
* with gcc-4.5

This also applies to upstream git head.

I doubt that this is actually a bug in exim, it might also be a
toolchain issue, but it is quite severe and needs to be documented.

cu andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

--- End Message ---
--- Begin Message --- 
Version: 2.13-1

On Sun, Apr 10, 2011 at 12:18:43PM +0300, Török Edwin wrote:
> Marc Glisse wrote:
> > Hello,
> > 
> > in the prototype of memmove (taken from glibc bits/string3.h), you will 
> > notice __restrict in front of the arguments. This is not present in more 
> > recent glibc versions and is a likely cause of your trouble.
> > 
> 
> Indeed if I remove __restrict the bug is gone, and if I upgrade to libc6
> 2.13-0exp5, VLC's dec.c seems to be compiled correctly too.

This bug has been fixed in eglibc 2.13-1. Closing the bug.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---
Reply to: