public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sqweek at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/3266] New: ldd doesn't work when /bin/sh is dash Date: Tue, 26 Sep 2006 16:02:00 -0000 [thread overview] Message-ID: <20060926160242.3266.sqweek@gmail.com> (raw) The problem is in line 122: 122:if set -o pipefail 2> /dev/null; then When dash hits the unknown pipefail option, it prints a diagnostic (which is suppressed of course) and then exits. This appears to be well within the rights of a compliant shell <http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_08_01>, though it's arguable whether the specific case of "set -o foo" is covered (especially since the table entries aren't exactly explicit about their meaning). Anyway, I mean to contact dash about this aswell but I didn't find a mailing list or bug database - only got as far as here tonight. As an aside, ldd also uses bash style $"" strings all over the place despite claiming to be bourne compatible via #!/bin/sh (of course this still works in dash you just get random $ signs in the output). -- Summary: ldd doesn't work when /bin/sh is dash Product: glibc Version: 2.3.6 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: sqweek at gmail dot com CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=3266 ------- 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:[~2006-09-26 16:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-09-26 16:02 sqweek at gmail dot com [this message] 2006-09-27 17:00 ` [Bug libc/3266] " drepper at redhat dot com 2006-10-02 8:38 ` sqweek at gmail dot com 2007-07-04 15:44 ` richardvoigt at gmail dot com 2007-07-04 15:47 ` richardvoigt at gmail dot com 2007-07-04 16:47 ` drepper at redhat dot com 2007-07-04 17:53 ` richardvoigt at gmail dot com 2010-07-30 11:56 ` a4239214 at bofthew dot com 2010-07-30 12:02 ` jakub at redhat dot com 2010-08-09 18:39 ` sqweek at gmail dot com
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=20060926160242.3266.sqweek@gmail.com \ --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).