public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steve dot hancher at aonix dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/15796] linefeed characters prevent successful build
Date: Thu, 03 Jun 2004 18:54:00 -0000 [thread overview]
Message-ID: <20040603185448.29593.qmail@sourceware.org> (raw)
In-Reply-To: <20040603163342.15796.shancher@aonix.com>
------- Additional Comments From steve dot hancher at aonix dot com 2004-06-03 18:54 -------
Subject: Re: linefeed characters prevent successful build
pinskia at gcc dot gnu dot org wrote:
>------- Additional Comments From pinskia at gcc dot gnu dot org 2004-06-03 17:27 -------
>Invalid as I know it works for everyone, you might want to try gnutar when untaring it.
>
>
>
I tried gnutar. Many files contain linefeeds. It does not work for
everyone because it does not work for me.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15796
prev parent reply other threads:[~2004-06-03 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 16:33 [Bug other/15796] New: " shancher at aonix dot com
2004-06-03 16:35 ` [Bug other/15796] " pinskia at gcc dot gnu dot org
2004-06-03 17:27 ` pinskia at gcc dot gnu dot org
2004-06-03 18:54 ` steve dot hancher at aonix dot com [this message]
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=20040603185448.29593.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).