From: "Adam Kropelin" <akropel1@rochester.rr.com>
To: "Dave Jones" <davej@suse.de>, "Bob Miller" <rem@osdl.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.7-dj2] Compile Error
Date: Thu, 28 Mar 2002 21:01:01 -0500 [thread overview]
Message-ID: <00a601c1d6c5$93620320$02c8a8c0@kroptech.com> (raw)
In-Reply-To: <200203281216.32590@xsebbi.de> <00c801c1d655$d8e75cd0$02c8a8c0@kroptech.com> <20020328095352.A6291@doc.pdx.osdl.net> <20020328200331.B5064@suse.de>
----- Original Message -----
From: "Dave Jones" <davej@suse.de>
To: "Bob Miller" <rem@osdl.org>
Cc: "Adam Kropelin" <akropel1@rochester.rr.com>; <linux-kernel@vger.kernel.org>
Sent: Thursday, March 28, 2002 2:03 PM
Subject: Re: [2.5.7-dj2] Compile Error
> On Thu, Mar 28, 2002 at 09:53:52AM -0800, Bob Miller wrote:
> > So if you build with CONFIG_BSD_PROCESS_ACCT not set you're build will
> > break. I'm in the process of generating a patch that will make acct.c
> > again conditionally compile based on CONFIG_BSD_PROCESS_ACCT. This
> > should be done in a little bit and I'll post.
> >
> > Dave, where did you get the patch for acct.c?
>
> Al Viro's 0-aliases-c-C7-pre2
> It looks like killing the first occurance of acct.o in kernel/Makefile
> should do the trick. Let me know if that works out.
Works For Me (tm).
(but see my other message for an oops report)
--Adam
next prev parent reply other threads:[~2002-03-29 2:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 11:17 [2.5.7-dj2] Compile Error Sebastian Roth
2002-03-28 12:41 ` Adam Kropelin
2002-03-28 17:53 ` Bob Miller
2002-03-28 18:25 ` [PATCH] " Bob Miller
2002-03-28 19:03 ` Dave Jones
2002-03-29 2:01 ` Adam Kropelin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-28 19:01 Andrey Klochko
2002-03-28 20:07 ` Sebastian Roth
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='00a601c1d6c5$93620320$02c8a8c0@kroptech.com' \
--to=akropel1@rochester.rr.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rem@osdl.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.