Re: planning binutils NMU (testing wanted ...)

2003-05-12 Thread Gunnar Wolf
Matthias Klose dijo [Sat, May 10, 2003 at 12:24:16PM +0200]:
 - mips and mipsel packages aren't built yet. There is a lack of
   mips/mipsel machine available to developers.

I have a couple of Indy machines over here... I was planning to offer
one of them as a public developer machine - I only need to get a larger
hard disk (they have 400MB, I think - way too little to be useful) and
if possible more RAM (they have 32MB - At least 64 would be nice).

Yes, a MIPS machine is not really required now, as we have te buildds -
but it certainly would be useful :)

If you want to work on my machine as it is now, please send me a
message, and I'll give you an account.

Greetings,

-- 
Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5630-9700 ext. 1366
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973  F800 D80E F35A 8BB5 27AF




re: planning binutils NMU (testing wanted ...)

2003-05-11 Thread Jack Howarth
Matthias,
I rebuilt your test debian binutils 2.14.90.0.1-0.1 package
on my debian ppc sid box and it looks fine. The places where we diverge
are...

your build...

=== binutils Summary ===

# of expected passes28
# of untested testcases 4

and my build

=== binutils Summary ===
 
# of expected passes31
# of expected failures  1

This difference of 4 untested test cases is due to you having
dejagnu 1.4.3 installed and my having downgraded to 1.4.2.

The other divergence is...

your build...

=== ld Summary ===

# of expected passes171
# of unexpected failures6
# of unexpected successes   4
# of expected failures  8


and my build...


=== ld Summary ===
 
# of expected passes177
# of unexpected successes   4
# of expected failures  8

These 6 unexpected failures strongly suggest that the ppc sid
build machine you used had been prelinked. Currently we are
waiting for Jakub to debug why prelinking causes these 6 
unexpected failures. Since I have unprelinked my machine they
aren't triggered. In any case, they are non-fatal for us.
   Jack




Re: planning binutils NMU (testing wanted ...)

2003-05-11 Thread GOTO Masanori
At Sat, 10 May 2003 12:24:16 +0200,
Matthias Klose wrote:
 You can find packages of binutils-2.14.90.0.1 for alpha, arm, hppa,
 ia64, i386, m68k, powerpc, sparc and s390 on
 
   http://ftp-master.debian.org/~doko/binutils/
 
 These packages fix at least some important reports.  In the same
 directory there is a README.test-summaries, which compares the test
 results from the installed version on the build machines with the
 results form the newly built version. Dan already told me about some
 failures which are expected with our current glibc version. Are these
 packages good enough for an NMU?

Cool.  I think it's fine to upload it.  I rebuild the latest 2.3.2-1
with this binutils, and it looks ok on i386.  However I have not
checked this version on the other architecture.  Thanks to Matthias,
Chris, and Dan!

 - mips and mipsel packages aren't built yet. There is a lack of
   mips/mipsel machine available to developers.

Well, it's really problem for toolchain packages.

Regards,
-- gotom




planning binutils NMU (testing wanted ...)

2003-05-10 Thread Matthias Klose
You can find packages of binutils-2.14.90.0.1 for alpha, arm, hppa,
ia64, i386, m68k, powerpc, sparc and s390 on

http://ftp-master.debian.org/~doko/binutils/

These packages fix at least some important reports.  In the same
directory there is a README.test-summaries, which compares the test
results from the installed version on the build machines with the
results form the newly built version. Dan already told me about some
failures which are expected with our current glibc version. Are these
packages good enough for an NMU?

- mips and mipsel packages aren't built yet. There is a lack of
  mips/mipsel machine available to developers.

- Can you check for your favourite binutils report with these
  packages and notify [EMAIL PROTECTED] and [EMAIL PROTECTED]


Thanks, Matthias