public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/229] gcc reports an error (invalid quotes) in csu/version-info.h during crossbuild. Date: Tue, 10 Aug 2004 02:37:00 -0000 [thread overview] Message-ID: <20040810023722.15158.qmail@sourceware.org> (raw) In-Reply-To: <20040620145059.229.pluto@pld-linux.org> ------- Additional Comments From drepper at redhat dot com 2004-08-10 02:37 ------- This last patch is not better than what we have now. You complain about missing SUS compliance of the script and use echo with an option yourself. The SUS echo must not have any option. You can correct your patch by testing for bash, and if bash is used, use shopt -s xpg_echo ... shopt -u xpg_echo around the echos in the your patch. Please change your patch and test it. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |drepper at redhat dot com Status|NEW |WAITING http://sources.redhat.com/bugzilla/show_bug.cgi?id=229 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2004-08-10 2:37 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-06-20 14:51 [Bug libc/229] New: gcc repoers " pluto at pld-linux dot org 2004-06-20 17:43 ` [Bug libc/229] " pluto at pld-linux dot org 2004-06-21 16:33 ` nickc at redhat dot com 2004-06-22 8:45 ` qboosh at pld-linux dot org 2004-06-24 12:40 ` [Bug libc/229] gcc reports " schwab at suse dot de 2004-06-25 3:28 ` akss at nsk dot ru 2004-08-10 2:37 ` drepper at redhat dot com [this message] 2004-08-30 20:17 ` qboosh at pld-linux dot org 2004-08-31 6:23 ` aj at suse dot de
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=20040810023722.15158.qmail@sourceware.org \ --to=sourceware-bugzilla@sources.redhat.com \ --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).