On Thu, Jan 29, 2009 at 02:55:20 +, Steve Cotton wrote:
> I've spent a while looking at what runs what, and realised that it will be
> quite time consuming for someone not familiar with your package to extact
> a test case.
>
> Would it be possible for you to isolate the gsf-scan bit;
.c and .
Hi Ray,
I've spent a while looking at what runs what, and realised that it
will be quite time consuming for someone not familiar with your
package to extact a test case. Would it be possible for you to
isolate the gsf-scan bit; and provide the arguments and input
files to run it in isolation rath
forwarded 513420 http://gcc.gnu.org/PR39015
tag 513420 + upstream
tag 513420 + pending
thanks
preparing 4.3.3-3.
caused by the fix for PR38615. would it be possible to track down the
miscompiled source file and update the upstream report?
J.H.M. Dassen (Ray) schrieb:
> Package: gcc-4.3
> Version
Processing commands for cont...@bugs.debian.org:
> forwarded 513420 http://gcc.gnu.org/PR39015
Bug#513420: Breaks building libgsf from source
Noted your statement that Bug has been forwarded to http://gcc.gnu.org/PR39015.
> tag 513420 + upstream
Bug#513420: Breaks building libgsf from
Package: gcc-4.3
Version: 4.3.3-1
Severity: serious
Justification: causes libgsf to no longer build from source; regression
compared to testing's gcc-4.3 packages.
What am I trying to do:
* Build libgsf from source again on amd64 (or build libgsf svn trunk).
How am I trying to do it / steps to re
5 matches
Mail list logo
