public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Neulinger, Nathan" <nneul@umr.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: RE: other/1512: Path confusion w/ -print-prog-name + autoconf Date: Fri, 06 Dec 2002 11:56:00 -0000 [thread overview] Message-ID: <20021206195600.26607.qmail@sources.redhat.com> (raw) The following reply was made to PR other/1512; it has been noted by GNATS. From: "Neulinger, Nathan" <nneul@umr.edu> To: "Wolfgang Bangerth" <bangerth@ticam.utexas.edu> Cc: <gcc-gnats@gcc.gnu.org> Subject: RE: other/1512: Path confusion w/ -print-prog-name + autoconf Date: Fri, 6 Dec 2002 13:53:00 -0600 Yes, gcc 3.2.1 still generates paths containing bin/../lib mkdir /tmp/c ln -s /umr/s/gcc321/install/redhat71/lib /tmp/c/lib ln -s /umr/s/gcc321/install/redhat71/bin /tmp/c/bin /tmp/c/bin/gcc -print-prog-name=3Dld /tmp/c/bin/../lib/gcc-lib/i686-pc-linux-gnu/3.2.1/../../../../i686-pc-li nux-gnu/bin/ld There's nothing _wrong_ with that path, but I figured that having gcc generate a path without the ..'s would help the situation some. (The bin/../lib is where the problem occurs if autoconf uses non-intelligent handling of .. in paths containing symlinked dirs.) /tmp/c/bin/.. !=3D /tmp/c if /tmp/c/bin is a symlink.=20 As people are more likely to install updated O/S with new gcc, fixing here is more likely to have a benefical impact than getting everyone to move to new autoconf, especially for older products.=20 -- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: nneul@umr.edu University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 > -----Original Message----- > From: Wolfgang Bangerth [mailto:bangerth@ticam.utexas.edu]=20 > Sent: Friday, December 06, 2002 8:46 AM > To: Neulinger, Nathan > Cc: gcc-gnats@gcc.gnu.org > Subject: Re: other/1512: Path confusion w/ -print-prog-name + autoconf >=20 >=20 >=20 > > Please let me know if I can explain this further. I'll let=20 > you know if > > it is still an issue with the version y'all just released=20 > when I get it > > installed. >=20 > Thanks for your explanation. I think it was very clear. >=20 > It would be great if you could let us know whether it works=20 > now in your=20 > experiments. >=20 > Thanks > Wolfgang >=20 > -------------------------------------------------------------- > ----------- > Wolfgang Bangerth email: =20 > bangerth@ticam.utexas.edu > www:=20 > http://www.ticam.utexas.edu/~bangerth >=20 >=20 >=20
next reply other threads:[~2002-12-06 19:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-06 11:56 Neulinger, Nathan [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-09 12:36 Neulinger, Nathan 2002-12-09 12:28 bangerth 2002-12-06 6:56 Wolfgang Bangerth 2002-12-05 19:46 Nathan Neulinger 2002-12-05 12:01 bangerth
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=20021206195600.26607.qmail@sources.redhat.com \ --to=nneul@umr.edu \ --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).