From: erik quanstrom <quanstro@quanstro.net>
To: rc@hawkwind.utcs.toronto.edu
Subject: rc-1.6s20010618 configuration problems
Date: Mon, 18 Jun 2001 13:41:34 -0500 [thread overview]
Message-ID: <20010618174134.911073EA0A@quanstro.net> (raw)
autoconf seems not to like me
[...]
checking how to run the C preprocessor... grep: *+: No such file or directory
gcc -E
checking for ln... ln
checking for sys/resource.h... grep: *+: No such file or directory
yes
checking for sys/time.h... grep: *+: No such file or directory
yes
checking for sys/types.h... grep: *+: No such file or directory
yes
checking for unistd.h... grep: *+: No such file or directory
yes
[...]
; uname -a
Linux linuxdev.somewhere.com 2.2.16-3smp #1 SMP Fri Oct 27 19:01:58 PDT 2000 i686 unknown
--
erik
reply other threads:[~2001-06-18 18:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010618174134.911073EA0A@quanstro.net \
--to=quanstro@quanstro.net \
--cc=rc@hawkwind.utcs.toronto.edu \
/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 NNTP newsgroup(s).