public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
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 15:26:00 -0000	[thread overview]
Message-ID: <20030107152607.11174.qmail@sources.redhat.com> (raw)

The following reply was made to PR debug/9179; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Al Bogner <al@usenet.pinguin.uni.cc>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Subject: Re: debug/9179: make modules: encode-gbk.o encode-gbk.c
Date: Tue, 7 Jan 2003 09:19:40 -0600 (CST)

 > ftp://ftp.suse.com/pub/people/mantel/next/RPM/kernel-source-2.4.19.SuSE-127.i586.rpm 
 > and I don't know which file(s) you exactly want. Sorry, I am not a 
 > programmer, but of course I will help you as much as I can. The pc 
 > now runs with a working kernel, but has all the kernel-sources 
 > installed. So If you tell me the exact name and if possible the 
 > path I will compress the files and send them to you.
 
 The failure happened with encode-gbk.c, so what you should do is to do the 
 same build again, wait until it crashes. Then go into the directory from 
 which the compilation was invoked (from the output you sent, this should 
 be /usr/src/linux-2.4.19.SuSE/drivers/video/unicon), and do the following
 - issue the same compilation command as what make tells you was the last 
   command; this should crash the compiler again
 - do the same thing, but add the flags -save-temps to the commen line;
   this should again crash the compiler, but leave behind a file named
   encode-gbk.i
 - send this .i file to us, as this is what we need
 
 Thanks
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 
 


             reply	other threads:[~2003-01-07 15:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 15:26 Wolfgang Bangerth [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 11:26 Al Bogner
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=20030107152607.11174.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.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: link
Be 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).