public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: PATCH: Re: other/9031 Date: Thu, 26 Dec 2002 20:16:00 -0000 [thread overview] Message-ID: <20021227041601.28323.qmail@sources.redhat.com> (raw) The following reply was made to PR other/9031; it has been noted by GNATS. From: "John David Anglin" <dave@hiauly1.hia.nrc.ca> To: aoliva@redhat.com (Alexandre Oliva) Cc: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, dave.anglin@nrc.ca, gcc-patches@gcc.gnu.org, binutils@sources.redhat.com Subject: Re: PATCH: Re: other/9031 Date: Thu, 26 Dec 2002 23:10:28 -0500 (EST) > host. So perhaps it would be more reasonable to change case $host to > case $build. Besides, I suppose the problem may actually be caused by > the unnecessary use of double quotes in the assignment. I *think* > taking them out may cause the needless CR to go away without affecting > anything else. I don't think so. The double quotes were mine and not in the original libtool macro. The original comment regarding the CR was that gcc leaves a trailing CR which upsets mingw. I am unable to test whether this is actually a problem. The libtool patch to strip carriage returns was made by Gary Vaughan on 1999-08-03. The predates the libtool archive. I agree that $host should be $build. > Also, pathname canonicalization is tricky business. Replacing > foo/../ with / is only a good idea when foo is not a soft link. Do we > really need this? I did the pathname canonicalization because the libtool macro did it and I was trying the provide a default value for LD comparible to what libtool would generate. It's unnecessary in the configurations that I use and would have no objection in removing it. Dave -- J. David Anglin dave.anglin@nrc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next reply other threads:[~2002-12-27 4:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-26 20:16 John David Anglin [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-04 21:06 John David Anglin 2002-12-28 1:26 Alexandre Oliva 2002-12-27 22:36 Alexandre Oliva 2002-12-27 22:26 John David Anglin 2002-12-26 19:16 Alexandre Oliva 2002-12-26 14:26 John David Anglin
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=20021227041601.28323.qmail@sources.redhat.com \ --to=dave@hiauly1.hia.nrc.ca \ --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).