From: Vadim Antonov avg@postman.ncube.com
Subject: BUG in a kernel mkfile
Date: Wed, 23 Aug 1995 02:03:49 -0400 [thread overview]
Message-ID: <19950823060349.Bz_B8LpZyk6h6pOtOHboN1vshSaqdIB4nWCHxYWIkzY@z> (raw)
Strange -- i cannot reproduce it. When i first did
it i used 1.0 binaries in /386/bin, though; and loaded
newer ones later. The problem was that everything
in $names was one space-separated string, not an array.
Sorry for the false alarm.
--vadim
If this is a bug I don't understand how I've ever been able to make a kernel.
The distributed mkfile works fine for me.
next reply other threads:[~1995-08-23 6:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-23 6:03 Vadim [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-23 17:51 bobf
1995-08-23 1:18 jmk
1995-08-22 6:47 Vadim
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=19950823060349.Bz_B8LpZyk6h6pOtOHboN1vshSaqdIB4nWCHxYWIkzY@z \
--to=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).