public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: 'Zack Weinberg' <zack@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/5515: ./configure fails: sed: Function s%@subdirs@% cp cannot be parsed. Date: Tue, 29 Jan 2002 11:06:00 -0000 [thread overview] Message-ID: <20020129190600.30007.qmail@sources.redhat.com> (raw) The following reply was made to PR other/5515; it has been noted by GNATS. From: 'Zack Weinberg' <zack@codesourcery.com> To: Edwin Bates <ebates@Ebix.com> Cc: Craig Rodrigues <rodrigc@mediaone.net>, Carlo Wood <carlo@alinoe.com>, "'rodrigc@gcc.gnu.org'" <rodrigc@gcc.gnu.org>, "'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>, "'gcc-prs@gcc.gnu.org'" <gcc-prs@gcc.gnu.org>, "'nobody@gcc.gnu.org'" <nobody@gcc.gnu.org>, "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>, Steve Moore <SMoore@Ebix.com> Subject: Re: other/5515: ./configure fails: sed: Function s%@subdirs@% cp cannot be parsed. Date: Tue, 29 Jan 2002 11:04:54 -0800 On Tue, Jan 29, 2002 at 10:02:58AM -0500, Edwin Bates wrote: > Thank you all for your input. Carlo was correct: it's inserting a newline, > but only after the first directory (cp), and, as Craig said, it shouldn't be > doing it. (What are you doing, AIX?) Hmmm. Can you get a copy of GNU sed and repeat the test with it installed ahead of AIX sed in your PATH, please? > + echo ./cp/config-lang.in > + sed -e s,^.*/\([^/]*\)/config-lang.in$,\1, > subdirs= cp > *boggle* zw
next reply other threads:[~2002-01-29 19:06 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-29 11:06 'Zack Weinberg' [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-22 16:07 neroden 2002-02-08 10:36 'Zack Weinberg' 2002-02-06 13:26 Edwin Bates 2002-01-30 11:46 'Zack Weinberg' 2002-01-29 11:46 Edwin Bates 2002-01-29 7:06 Edwin Bates 2002-01-28 20:16 Zack Weinberg 2002-01-28 19:56 Craig Rodrigues 2002-01-28 19:06 Carlo Wood 2002-01-28 18:26 Craig Rodrigues 2002-01-28 16:56 Edwin Bates 2002-01-28 10:37 rodrigc 2002-01-28 9:16 ebates
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=20020129190600.30007.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.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: 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).