public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Al Bogner <al@usenet.pinguin.uni.cc> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: debug/9179: make modules: encode-gbk.o encode-gbk.c Date: Tue, 07 Jan 2003 11:26:00 -0000 [thread overview] Message-ID: <20030107112602.4475.qmail@sources.redhat.com> (raw) The following reply was made to PR debug/9179; it has been noted by GNATS. From: Al Bogner <al@usenet.pinguin.uni.cc> To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: debug/9179: make modules: encode-gbk.o encode-gbk.c Date: Tue, 7 Jan 2003 12:16:49 +0100 On Dienstag, 7. Januar 2003 02:06 bangerth@dealii.org wrote: > Synopsis: make modules: encode-gbk.o encode-gbk.c > > State-Changed-From-To: open->feedback > State-Changed-By: bangerth > State-Changed-When: Mon Jan 6 17:06:10 2003 > State-Changed-Why: > Can you please send us the preprocessed sources for the one > file that failed? (See the instructions on the webpage that > is referenced in the compiler message.) > > Thanks > Wolfgang > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&dat >abase=3Dgcc&pr=3D9179 Hi, as mentioned I used=20 ftp://ftp.suse.com/pub/people/mantel/next/RPM/kernel-source-2.4.19.SuSE-1= 27.i586.rpm=20 and I don't know which file(s) you exactly want. Sorry, I am not a=20 programmer, but of course I will help you as much as I can. The pc=20 now runs with a working kernel, but has all the kernel-sources=20 installed. So If you tell me the exact name and if possible the=20 path I will compress the files and send them to you. Albert
next reply other threads:[~2003-01-07 11:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-07 11:26 Al Bogner [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-13 15:15 bangerth 2003-01-13 15:06 Al Bogner 2003-01-07 22:56 Al Bogner 2003-01-07 22:56 Wolfgang Bangerth 2003-01-07 15:26 Wolfgang Bangerth 2003-01-07 1:06 bangerth 2003-01-05 19:26 al
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=20030107112602.4475.qmail@sources.redhat.com \ --to=al@usenet.pinguin.uni.cc \ --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).