From: Jody <jbruchon@nc.rr.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Possible bug in Dev86
Date: Mon, 08 May 2006 00:41:30 -0400 [thread overview]
Message-ID: <445ECBFA.7090102@nc.rr.com> (raw)
When building elkscmd, I find that elks/include/linuxmt/config.h is
causing an error on line 5 stating "cannot open include file." Digging
deeper, the include file is present in the included folder, and the two
#include'd before and after are not whined about. Renaming the file or
moving the tree around does nothing. I do not see how this can be a
problem with the code itself.
reply other threads:[~2006-05-08 4:41 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=445ECBFA.7090102@nc.rr.com \
--to=jbruchon@nc.rr.com \
--cc=linux-8086@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.