public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Bill" <bill@radiantideas.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: RE: libstdc++/10285: Library won't install Date: Tue, 01 Apr 2003 14:16:00 -0000 [thread overview] Message-ID: <20030401141600.3549.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/10285; it has been noted by GNATS. From: "Bill" <bill@radiantideas.com> To: <ehrhardt@mathematik.uni-ulm.de>, <bill@radiantideas.com>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Cc: Subject: RE: libstdc++/10285: Library won't install Date: Tue, 1 Apr 2003 09:07:05 -0500 Thanks for the speedy reply -- when I add those flags, it spits out a bunch of stuff, but doesn't compile. TIA, Bill >-----Original Message----- >From: ehrhardt@mathematik.uni-ulm.de >[mailto:ehrhardt@mathematik.uni-ulm.de] >Sent: Tuesday, April 01, 2003 8:54 AM >To: bill@radiantideas.com; gcc-bugs@gcc.gnu.org; >gcc-prs@gcc.gnu.org; nobody@gcc.gnu.org >Subject: Re: libstdc++/10285: Library won't install > > >Synopsis: Library won't install > >State-Changed-From-To: open->feedback >State-Changed-By: cae >State-Changed-When: Tue Apr 1 13:54:14 2003 >State-Changed-Why: > Could you please issue the very last command by hand and >add the flags > -v and -save-temps. This should cause the very same >Internal compiler > error but with more verbose output from gcc. In addition it should > generate a file named crtstuff.i. Please send the complete > output of the command and the file crtstuff.i. If you send it in > private, I'll attach it properly to the bug report. > > Thanks in advance. > > >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&d atabase=gcc&pr=10285
next reply other threads:[~2003-04-01 14:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-01 14:16 Bill [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-02 20:16 Zack Weinberg 2003-04-01 13:54 ehrhardt 2003-04-01 13:36 bill
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=20030401141600.3549.qmail@sources.redhat.com \ --to=bill@radiantideas.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).