public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: PATCH: Re: other/9031 Date: Thu, 26 Dec 2002 19:16:00 -0000 [thread overview] Message-ID: <20021227031602.12196.qmail@sources.redhat.com> (raw) The following reply was made to PR other/9031; it has been noted by GNATS. From: Alexandre Oliva <aoliva@redhat.com> To: "John David Anglin" <dave@hiauly1.hia.nrc.ca> 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: 27 Dec 2002 01:11:11 -0200 On Dec 26, 2002, "John David Anglin" <dave@hiauly1.hia.nrc.ca> wrote: > The enclosed patch fixes the problem reported in other/9031. The > technique for determining LD is derived from that used by the > libtool AC_PROG_LD macro. > + case $host in > + *-*-mingw*) > + gcc_prog_ld="`$CC -print-prog-name=ld 2>&1 | tr -d '\015'`" ;; > + *) > + gcc_prog_ld="`$CC -print-prog-name=ld 2>&1`" ;; > + esac I don't think this is appropriate. If mingw's CRs are causing trouble, they'd cause trouble when mingw is the build machine, not the 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. Another issue is that CC's ending with gcc may not be a good test for whether the host compiler is CC. I realize this is not the only occurrence of case $CC in *gcc) in the configure script, but even that one should IMHO be changed so as to use something more similar to autoconf's test for whether we are using GNU C. 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? -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org} CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist Professional serial bug killer
next reply other threads:[~2002-12-27 3:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-26 19:16 Alexandre Oliva [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 20:16 John David Anglin 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=20021227031602.12196.qmail@sources.redhat.com \ --to=aoliva@redhat.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).