public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nneul@umr.edu, nobody@gcc.gnu.org Subject: Re: other/1512: Path confusion w/ -print-prog-name + autoconf Date: Mon, 09 Dec 2002 12:28:00 -0000 [thread overview] Message-ID: <20021209202815.19101.qmail@sources.redhat.com> (raw) Synopsis: Path confusion w/ -print-prog-name + autoconf State-Changed-From-To: feedback->open State-Changed-By: bangerth State-Changed-When: Mon Dec 9 12:28:14 2002 State-Changed-Why: Still happens. I am not qualifies to say what should be done for this one. There are plans to move to AutoConf 2.50, maybe that will help... http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=1512
next reply other threads:[~2002-12-09 20:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-09 12:28 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-09 12:36 Neulinger, Nathan 2002-12-06 11:56 Neulinger, Nathan 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=20021209202815.19101.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nneul@umr.edu \ --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).