Hi On 10-08-15 11:45, Abou Al Montacir wrote: > Does this give enough info to lower the severity of the bug or to > forward the bug to binutils?
I don't know. When I just tried to reproduce Abou's results of
yesterday, the ld call doesn't seem to be the problem to me. When I let
the process run a little longer (patience) then instead of the last line
waiting for ld.bdf I get:
(sid_armel-dchroot)elbrus@abel:~/ddrescueview-0.4~alpha2$ ps fux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
elbrus 25228 0.0 0.1 13332 4724 ? S 11:05 0:00 sshd:
elbrus@pts/0
elbrus 25229 0.0 0.1 8684 6472 pts/0 Ss 11:05 0:00 \_ -bash
elbrus 8533 0.0 0.0 3504 2816 pts/0 S 11:23 0:00 -bash
elbrus 18706 0.0 0.0 1932 1328 pts/0 S 12:20 0:00 \_
/usr/bin/make -f debian/rules binary
elbrus 18707 1.3 0.1 9152 7444 pts/0 S 12:20 0:00 | \_
/usr/bin/perl -w /usr/bin/dh binary
elbrus 18712 0.0 0.0 1932 1324 pts/0 S 12:20 0:00 |
\_ /usr/bin/make -f debian/rules override_dh_auto_build
elbrus 18713 0.0 0.0 1776 336 pts/0 S 12:20 0:00 |
\_ /bin/sh -c lazbuild source/ddrescueview.lpi --bm="GNU/Lin
elbrus 18714 2.4 0.3 22128 14052 pts/0 Sl 12:20 0:00 |
\_ lazbuild source/ddrescueview.lpi --bm=GNU/Linux Relea
elbrus 18732 0.0 0.0 0 0 pts/0 Z 12:20 0:00 |
\_ [fpc] <defunct>
elbrus 18749 0.0 0.0 6612 2668 pts/0 R+ 12:20 0:00 \_ ps fux
Where you can see that lazbuild is waiting for some event to happen
(haven't checked, but I assume the line that Graham already mentioned in
the upstream bug report). So to be honest, I think it already passed the
linker. However, what I noticed is that there is no output to the screen
at all during the building by lazbuild, while I expected to see the same
text as by manually running fpc. It seems that something in the new file
exttools.pas is broken on ARM.
Paul
signature.asc
Description: OpenPGP digital signature
