From: John Weber <weber@nyc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: More errors compiling kernel with GCC 3.1
Date: Wed, 02 Jan 2002 23:58:21 -0500 [thread overview]
Message-ID: <3C33E4ED.3020609@nyc.rr.com> (raw)
In-Reply-To: <fa.cast4mv.l0adg7@ifi.uio.no>
John Weber wrote:
> I'm just trying to read the source code, and I am having trouble in a
> few areas. For example, I am completely baffled by the number of macros
> that get called in some places. For example, in the semaphore code...
> just wondering why DECLARE_MUTEX (macro) calls DECLARE_SEMAPHORE_GENERIC
> (macro) calls SEMAPHORE_INITIALIZER (macro) calls
> WAIT_QUEUE_HEAD_INITIALIZER (macro) and so on, and so on...
I apologize, but this was mistakenly sent to the wrong mailing list...
I was complaining about some parts of the kernel that gcc 3.1 was having
trouble with, which upon reading I was having trouble with :).
Sorry for the pollution...
next parent reply other threads:[~2002-01-03 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.cast4mv.l0adg7@ifi.uio.no>
2002-01-03 4:58 ` John Weber [this message]
2002-01-03 4:50 More errors compiling kernel with GCC 3.1 John Weber
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=3C33E4ED.3020609@nyc.rr.com \
--to=weber@nyc.rr.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox