On Mon, 2008-01-21 at 05:52 +0100, Lucas Nussbaum wrote:
> On 20/01/08 at 23:28 +0000, Neil Williams wrote:
> > On Sun, 20 Jan 2008 23:12:56 +0100
> > Lucas Nussbaum <[EMAIL PROTECTED]> wrote:
> > 
> > I can't tell which bug is being discussed here - the To: list is too
> > long to be scanned. How do I find out which of the bugs listed in To:
> > actually apply to any of my packages?
> > 
> > Did you mean to set the To: list as BCC: instead?
> > 
> > Is there a usertag page that shows the actual bugs?

> http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=qa-ftbfs-dash;[EMAIL 
> PROTECTED]

In which case, the title of 459066 is wrong.
CANNOT FIND 'debian/*FFI*'
is a normal output message of any gcc build - the build proceeds
normally after that point.

The actual error is much further down the log:
> ../../src/gcc/config/i386/crtfastmath.c:106: warning: integer constant
is too large for 'long' type
> ../../src/gcc/config/i386/crtfastmath.c:106: warning: integer constant is too 
> large for 'long' type
> ../../src/gcc/config/i386/crtfastmath.c:106: warning: left shift count >= 
> width of type
> ../../src/gcc/config/i386/crtfastmath.c:106: warning: integer overflow in 
> expression
> make[5]: *** [crtfastmath.o] Error 1
> make[5]: *** Waiting for unfinished jobs....
> /bin/sh ../../src/gcc/../move-if-change tmp-macro_list macro_list
> echo timestamp > s-macro_list
> rm fsf-funding.pod gcov.pod gfdl.pod cpp.pod gpl.pod gcc.pod
> make[5]: Leaving directory `/build/user/gcc-4.2-4.2.2/build/gcc'
> make[4]: *** [all-stage1-gcc] Error 2
> make[4]: Leaving directory `/build/user/gcc-4.2-4.2.2/build'
> make[3]: *** [stage1-bubble] Error 2

It's not the move-if-change script - checkbashisms doesn't find anything
in the shell script to cause trouble. I can also do test runs of that
script using dash without problems (echo $? returns 0). (Besides, that
script is called elsewhere in the build without errors.)

This looks like a compiler error:
> ../../src/gcc/config/i386/crtfastmath.c: In function 'set_fast_math':

Is this failure reproducible with bash on the same machine?

Is it actually due to the use of dash?

There's no point making an NMU on this - the problem hasn't even been
identified, let alone fixed.

(I'm subscribed to the gcc BTS because of the need to cross build gcc
for Emdebian.)

-- 


Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/


Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to