reassign 469058 linux-2.6
submitter 469058 [EMAIL PROTECTED]
clone 469058 -1 -2 -3 -4 -5
reassign -1 kfreebsd-6
retitle -1 FreeBSD kernel doesn't follow x86/x86-64 ABI wrt direction flag
reassign -2 kfreebsd-7
retitle -2 FreeBSD kernel doesn't follow x86/x86-64 ABI wrt direction flag
reassign -3 hurd
retitle -3 Hurd crashes when a signal handler is called with DF = 1
reassign -4 gcc-4.3
retitle -4 gcc-4.3: old behavior wrt cld/std should be restored
reassign -5 glibc
retitle -5 libc6 should build-depends on a fixde gcc 4.3 wrt cld/std
submitter -5 [EMAIL PROTECTED]
thanks


On Wed, Mar 05, 2008 at 04:49:21PM +0100, Aurelien Jarno wrote:
> reassign 469058 linux-2.6,gcc-4.3
> thanks
> 
> On Wed, Mar 05, 2008 at 04:10:53PM +0100, Aurelien Jarno wrote:
> That's definitively a kernel/gcc-4.3 problem, I have reported it
> upstream: http://lkml.org/lkml/2008/3/5/207
> 
> I am therefore reassigning the bug to those packages.
> 

Now that the situation is more clear, let's clone/reassign the bugs to
the right packages. While the kernels have to be fixed, gcc 4.3
behavior wrt to cld/std has to be reverted to the old behavior to 
ensure an upgrade path from Etch.

So let's summarize:
- linux 2.6 has to be fixed. A patch is available on the lkml [1] for
  2.6.25-rc. It could be easily backported to 2.6.24
- kfreebsd 6 and 7 exhibit the same behavior. They have to be fixed
- hurd crashes in this case. It has to be fixed
- gcc 4.3 should not strictly follow the ABI when it comes to cld/std
  and use the old behavior, which is now a de facto ABI for some time.
- glibc 2.7-9 is broken with the current kernels. It has to be rebuilt
  with a fixed gcc.

[1] http://lkml.org/lkml/2008/3/5/306
[2] http://gcc.gnu.org/ml/gcc-patches/2006-12/msg00354.html

-- 
  .''`.  Aurelien Jarno             | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   [EMAIL PROTECTED]         | [EMAIL PROTECTED]
   `-    people.debian.org/~aurel32 | www.aurel32.net


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to