From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: nfs@lists.sourceforge.net
Subject: nfs-utils 1.0.3 compile error w/gcc-3.2.2
Date: Fri, 28 Mar 2003 08:29:22 -0500 [thread overview]
Message-ID: <3E844E32.4000008@lucidpixels.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 107 bytes --]
-rw-r--r-- 1 war wheel 2.7k Mar 28 08:24 log.bz2
The error is contained in the attachment.
[-- Attachment #2: log.bz2 --]
[-- Type: application/octet-stream, Size: 2803 bytes --]
next reply other threads:[~2003-03-28 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 13:29 Justin Piszcz [this message]
2003-03-28 14:57 ` nfs-utils 1.0.3 compile error w/gcc-3.2.2 Alex Thiel
2003-03-28 15:13 ` Justin Piszcz
2003-03-28 19:58 ` Alex Thiel
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=3E844E32.4000008@lucidpixels.com \
--to=jpiszcz@lucidpixels.com \
--cc=nfs@lists.sourceforge.net \
/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