public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "walch dot martin at web dot de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/9854] New: glibc opens up new tty to print *** %n in writable segment detected *** Date: Tue, 17 Feb 2009 00:33:00 -0000 [thread overview] Message-ID: <20090217003308.9854.walch.martin@web.de> (raw) I am a user of Gentoo Linux and I found some warnings on my screen that I could not redirect like stdout or stderr. They appear during execution of configure scripts, like the ones from coreutils or m4 and are caused by glibc. So I wrote a bug report on the Gentoo bug tracker. But the guys there say that everything is as it should be: http://bugs.gentoo.org/show_bug.cgi?id=257279 But I do not think, that this is acceptable. Next, I wrote to the bug-autoconf mailing list: http://lists.gnu.org/archive/html/bug-autoconf/2009-02/msg00006.html and was forwarded to bug-gnulib: http://lists.gnu.org/archive/html/bug-gnulib/2009-02/msg00103.html and from there I was sent here: http://lists.gnu.org/archive/html/bug-gnulib/2009-02/msg00106.html -- Summary: glibc opens up new tty to print *** %n in writable segment detected *** Product: glibc Version: 2.8 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: walch dot martin at web dot de CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=9854 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2009-02-17 0:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-17 0:33 walch dot martin at web dot de [this message] 2009-02-17 1:42 ` [Bug libc/9854] " drepper at redhat dot com 2009-02-17 8:38 ` walch dot martin at web dot de 2009-09-11 20:03 ` kees at outflux dot net
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=20090217003308.9854.walch.martin@web.de \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).