Re: No manpage for gcc is a policy violation

2007-03-18 Thread Matthias Klose
Jordi Gutierrez Hermoso writes: > I'm well aware of Debian's stance on GFDL docs (though I have a hard > time agreeing with it myself), but an important package like not > containing a manpage at all is a policy violation, and having the > manpage along with the rest of the documentation in the non

Bug#408888: gcj-4.1: FTBFS on GNU/Hurd

2007-03-18 Thread Matthias Klose
Samuel Thibault writes: > Samuel Thibault, le Sat 10 Mar 2007 00:48:31 +0100, a écrit : > > Matthias Klose, le Fri 09 Mar 2007 09:44:55 +0100, a écrit : > > > thanks for the patch. Please could you update it for gcj-4.1 from > > > experimental? > > > > Mmm, there's something odd with gcj-4.1 from

Bug#408888: gcj-4.1: FTBFS on GNU/Hurd

2007-03-18 Thread Matthias Klose
Samuel Thibault writes: > Mmm, gcj-4.1 build-depends on itself, gcj-4.1. Is that on purpose? (the > compilation seems to need it indeed). yes. build the packages from unstable first; an alternative might be to use the gcc-snapshot package for your first build. -- To UNSUBSCRIBE, email to [EMAI

No manpage for gcc is a policy violation

2007-03-18 Thread Jordi Gutierrez Hermoso
I'm well aware of Debian's stance on GFDL docs (though I have a hard time agreeing with it myself), but an important package like not containing a manpage at all is a policy violation, and having the manpage along with the rest of the documentation in the non-free section is unacceptable, as Debia

Bug#396609: marked as done (gnat-4.1: Link fails (Message: gnatlink.adb:1731 range check failed))

2007-03-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Mar 2007 15:42:55 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#396609: gnat-4.1: Link fails (Message: gnatlink.adb:1731 range check failed) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dea

Bug#396609: gnat-4.1: Link fails (Message: gnatlink.adb:1731 range check failed)

2007-03-18 Thread Matthieu Moy
Ludovic Brenta <[EMAIL PROTECTED]> writes: > Hi Matthieu, > > I have not been able to reproduce this bug, but it appears to be in a > Windows-specific part of gnatlink which we can safely remove. Could > you please try to recompile gnatlink with the following patch and see > if it solves your pro