public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug nptl/2612] New: glibc-20060306T1239 build problems on alpha
@ 2006-04-27 12:36 tomri at gmx dot net
  2006-04-27 12:37 ` [Bug nptl/2612] " tomri at gmx dot net
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: tomri at gmx dot net @ 2006-04-27 12:36 UTC (permalink / raw)
  To: glibc-bugs

This is the output from make check for glibc build on alpha.
FC4/5 seems to ignore this failures. Because this is build for alpha and not for
x86, I report it here, not at fedore bugzilla.

make check should run without error.

See attachment.

-- 
           Summary: glibc-20060306T1239 build problems on alpha
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: critical
          Priority: P2
         Component: nptl
        AssignedTo: drepper at redhat dot com
        ReportedBy: tomri at gmx dot net
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=2612

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug nptl/2612] glibc-20060306T1239 build problems on alpha
  2006-04-27 12:36 [Bug nptl/2612] New: glibc-20060306T1239 build problems on alpha tomri at gmx dot net
@ 2006-04-27 12:37 ` tomri at gmx dot net
  2006-04-27 12:43 ` tomri at gmx dot net
  2006-05-01 19:12 ` drepper at redhat dot com
  2 siblings, 0 replies; 4+ messages in thread
From: tomri at gmx dot net @ 2006-04-27 12:37 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From tomri at gmx dot net  2006-04-27 12:36 -------
Created an attachment (id=987)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=987&action=view)
glibc-20060306T1239


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=2612

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug nptl/2612] glibc-20060306T1239 build problems on alpha
  2006-04-27 12:36 [Bug nptl/2612] New: glibc-20060306T1239 build problems on alpha tomri at gmx dot net
  2006-04-27 12:37 ` [Bug nptl/2612] " tomri at gmx dot net
@ 2006-04-27 12:43 ` tomri at gmx dot net
  2006-05-01 19:12 ` drepper at redhat dot com
  2 siblings, 0 replies; 4+ messages in thread
From: tomri at gmx dot net @ 2006-04-27 12:43 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From tomri at gmx dot net  2006-04-27 12:43 -------
I reported some problems a time ago to mr. drepper and got no answer.. :-((

Subject: [Fwd: glibc current from cvs on alpha]
Date: Tue, 21 Feb 2006 13:16:30 +0100
From: Th. Steudten 
To: drepper@redhat.com

The problem with "write successful" which should be block, is
the same on alpha and x86.
The test tf_write() writes to a pipe, and this should block the call.

man write:
"If the O_NONBLOCK flag is clear, a write request may cause the thread to block,
but on normal completion it will return
nbyte."
Independently from the ulimit and PIPE_SIZE values, the write() call blocks
for linux alpha and x86 with kernel 2.6.15 beginning with a size of 1024*1024 byte.

With this patch to tf_write() the tests runs without problem:


--- tst-cancel4.c.orig  2006-02-21 13:11:39.000000000 +0100
+++ tst-cancel4.c       2006-02-21 13:13:43.000000000 +0100
@@ -190,7 +190,7 @@
 tf_write  (void *arg)
 {
   int fd;
-  int r;
+  int r, len = 1024 * 1024;

   if (arg == NULL)
     fd = fds[1];
@@ -198,6 +198,7 @@
     {
       char fname[] = "/tmp/tst-cancel4-fd-XXXXXX";
       tempfd = fd = mkstemp (fname);
+      len = 100000;
       if (fd == -1)
        printf ("%s: mkstemp failed\n", __FUNCTION__);
       unlink (fname);
@@ -220,9 +221,9 @@
   ssize_t s;
   pthread_cleanup_push (cl, NULL);

-  char buf[100000];
+  char buf[1024 * 1024]; /* we need to block write() */
   memset (buf, '\0', sizeof (buf));
-  s = write (fd, buf, sizeof (buf));
+  s = write (fd, buf, len);

   pthread_cleanup_pop (0);

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=2612

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug nptl/2612] glibc-20060306T1239 build problems on alpha
  2006-04-27 12:36 [Bug nptl/2612] New: glibc-20060306T1239 build problems on alpha tomri at gmx dot net
  2006-04-27 12:37 ` [Bug nptl/2612] " tomri at gmx dot net
  2006-04-27 12:43 ` tomri at gmx dot net
@ 2006-05-01 19:12 ` drepper at redhat dot com
  2 siblings, 0 replies; 4+ messages in thread
From: drepper at redhat dot com @ 2006-05-01 19:12 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From drepper at redhat dot com  2006-05-01 19:12 -------
This is fixed differently for quite some time.  Check the current sources.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME


http://sourceware.org/bugzilla/show_bug.cgi?id=2612

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2006-05-01 19:12 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-04-27 12:36 [Bug nptl/2612] New: glibc-20060306T1239 build problems on alpha tomri at gmx dot net
2006-04-27 12:37 ` [Bug nptl/2612] " tomri at gmx dot net
2006-04-27 12:43 ` tomri at gmx dot net
2006-05-01 19:12 ` drepper at redhat dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).