Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: John David Anglin <dave.anglin@nrc-cnrc.gc.ca>,
	Randolph Chung <tausq@debian.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Glibc 2.3.2 failures and possible fixes?
Date: Mon, 24 Mar 2003 16:35:08 -0500	[thread overview]
Message-ID: <20030324213508.GA8436@systemhalted> (raw)

John, Tausq,

Succeeded in building glibc 2.3.2 with syscall cancellation support, but
I'm pretty sure it's wrong.

The current list of failures includes:

iconvdata/bug-iconv3.out

- This is a new one.

math/test-fenv.out
math/test-float.out
math/test-double.out
math/test-ifloat.out

- We've had the math test failures for a while, would you like it if I
  tried building glibc with gcc head? It's been so long I've forgotten
  if this was really the delayed fp stuff that I fogot to implement :}
  Will get around to testing this more near the end of April.

stdlib/tst-strtod.out
stdlib/bug-strtod.out

- These are not so new, but indicate problems.

libio/tst-mmap-eofsync.out
libio/tst-mmap-fflushsync.out

- New kernel with Tausq's mmap flushing changes should make these go
  away... have to go into the office to install a new kernel.

dlfcn/default.out
dlfcn/tststatic.out

- New, possibly related to syscalls.

posix/annexc.out

- Expected.

linuxthreads/ex8.out
linuxthreads/ecmutex.out
linuxthreads/ex14.out
linuxthreads/ex15.out
linuxthreads/bug-sleep.out
linuxthreads/tst-cancel1.out
linuxthreads/tst-cancel2.out
linuxthreads/tst-cancel3.out
linuxthreads/tst-cancel4.out
linuxthreads/tst-cancel5.out
linuxthreads/tst-cancel6.out
linuxthreads/tst-popen.out
linuxthreads/tst-popen2.out
linuxthreads/tst-cancel-static.out
linuxthreads/tst-cancel-wrappers.out
rt/tst-shm.out
rt/tst-clock.out
rt/tst-aio.out
rt/tst-aio64.out
rt/tst-aio2.out
rt/tst-aio3.out
rt/tst-aio4.out
rt/tst-aio5.out
rt/tst-aio6.out
rt/tst-aio7.out

- I broke a lot of stuff... :}

elf/vismain.out
elf/neededtest.out
elf/neededtest2.out
elf/neededtest3.out
elf/neededtest4.out
elf/circleload1.out

- These have been around for a while, any idea about how to fix them?

Cheers,
Carlos.

             reply	other threads:[~2003-03-24 21:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 21:35 Carlos O'Donell [this message]
2003-03-24 22:01 ` [parisc-linux] Glibc 2.3.2 failures and possible fixes? Matthew Wilcox
2003-03-25 14:27   ` John David Anglin
2003-03-25 15:41     ` Carlos O'Donell
2003-03-25 11:37 ` Joel Soete
2003-03-25 17:17   ` Carlos O'Donell
2003-03-25 18:01     ` Joel Soete
2003-03-25 23:40       ` [parisc-linux] glibc 2.3.2 patches updated, still no working sysdep-cancel Carlos O'Donell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030324213508.GA8436@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=tausq@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox