public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net>
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: Mon, 28 Jan 2002 19:56:00 -0000	[thread overview]
Message-ID: <20020129035601.8750.qmail@sources.redhat.com> (raw)

The following reply was made to PR other/5515; it has been noted by GNATS.

From: Craig Rodrigues <rodrigc@mediaone.net>
To: Carlo Wood <carlo@alinoe.com>
Cc: Edwin Bates <ebates@Ebix.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: Mon, 28 Jan 2002 22:54:29 -0500

 On Tue, Jan 29, 2002 at 04:00:09AM +0100, Carlo Wood wrote:
 > <guru mode on>
 > Maybe I can shine a light on this.
 > One of the reasons that configure fails to substitue
 > is when
 > 1) A substitution contains new-lines
 > 2) The substitution is exactly overlapping
 >    the border at which the substitution command
 >    is cut into multiple sed commands.
 > 
 > Obviously this a coincidence, but in fact only
 > truely safe when none of the substitution contain
 > new-lines.
 > 
 > What the patch below might change is replacing
 > new-lines in ${subdirs} into spaces.
 > </guru mode off>
 
 OK.  Zack Weinberg applied a patch which does a similar
 thing to subdirs:
 http://subversions.gnu.org/cgi-bin/viewcvs/gcc/gcc/gcc/configure.in.diff?r1=text&tr1=1.573&r2=text&tr2=1.574&diff_format=u
 
 and:
 http://subversions.gnu.org/cgi-bin/viewcvs/gcc/gcc/gcc/configure.diff?r1=text&tr1=1.583&r2=text&tr2=1.584&diff_format=u
 
 So maybe that is the right thing to do here?
 
 Edwin, can you try changing your fix to:
 subdirs='$subdirs'
 
 and see if that works?
 
 -- 
 Craig Rodrigues        
 http://www.gis.net/~craigr    
 rodrigc@mediaone.net          


             reply	other threads:[~2002-01-29  3:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-28 19:56 Craig Rodrigues [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 11:06 'Zack Weinberg'
2002-01-29  7:06 Edwin Bates
2002-01-28 20:16 Zack Weinberg
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=20020129035601.8750.qmail@sources.redhat.com \
    --to=rodrigc@mediaone.net \
    --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: link
Be 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).