Bug#425011: gcc-4.1: FTBFS on m68k and arm, multiple definitions of ffi_prep_closure

To: Matthias Klose <doko@cs.tu-berlin.de>, 425011@bugs.debian.org
Cc: Peter Green <Peter.Green@student.manchester.ac.uk>
Subject: Bug#425011: gcc-4.1: FTBFS on m68k and arm, multiple definitions of ffi_prep_closure
From: Riku Voipio <riku.voipio@iki.fi>
Date: Fri, 18 May 2007 17:39:13 +0300
Message-id: <[🔎] 20070518143913.GG2074@kos.to>
Reply-to: Riku Voipio <riku.voipio@iki.fi>, 425011@bugs.debian.org
In-reply-to: <[🔎] 17997.44688.706410.700446@gargle.gargle.HOWL>
References: <[🔎] 20070518143038.s2dm5gqp5wgg8g4o@webmail.manchester.ac.uk> <[🔎] 17997.44688.706410.700446@gargle.gargle.HOWL>

On Fri, May 18, 2007 at 03:48:00PM +0200, Matthias Klose wrote:
> Peter Green writes:
> > package:gcc-4.1
> > version:4.1.2-7
> > severity:serious

> > from the relavent buildd logs:

> Note, that the severity is not RC for 68k; I do not intend to fix
> that.  Same for arm

Is building libffi.so.4 from gcc4.1 relevant anyway? Shouldn't we
help getting gcc-4.2 into shape instead?

Reply to:

Follow-Ups:
- Bug#425011: gcc-4.1: FTBFS on m68k and arm, multiple definitions of ffi_prep_closure
  - From: Matthias Klose <doko@cs.tu-berlin.de>

References:
- Bug#425011: gcc-4.1: FTBFS on m68k and arm, multiple definitions of ffi_prep_closure
  - From: Peter Green <Peter.Green@student.manchester.ac.uk>
- Bug#425011: gcc-4.1: FTBFS on m68k and arm, multiple definitions of ffi_prep_closure
  - From: Matthias Klose <doko@cs.tu-berlin.de>

Prev by Date: Bug#425011: gcc-4.1: FTBFS on m68k and arm, multiple definitions of ffi_prep_closure
Next by Date: Bug#425011: gcc-4.1: FTBFS on m68k and arm, multiple definitions of ffi_prep_closure
Previous by thread: Bug#425011: gcc-4.1: FTBFS on m68k and arm, multiple definitions of ffi_prep_closure
Next by thread: Bug#425011: gcc-4.1: FTBFS on m68k and arm, multiple definitions of ffi_prep_closure
Index(es):
- Date
- Thread