From: Disconnect <kernel@gotontheinter.net>
To: Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Martin List-Petersen <martin@list-petersen.dk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: implicid declaration of function task_suspended - Was: [PATCHSET] 2.4.21-rc6-dis3 released
Date: 12 Jun 2003 12:10:47 -0400 [thread overview]
Message-ID: <1055434247.11780.26.camel@slappy> (raw)
In-Reply-To: <1055431855.11780.5.camel@slappy>
Somewhere TASK_SUSPENDED isn't getting defined when SWSUSP is disabled.
So the fix is to enable SWSUSP (which is a big part of this patchset
anyway ;) ..) for now, and I'll see if I can't get it tracked down
before -dis4..
On Thu, 2003-06-12 at 11:30, Disconnect wrote:
> On Thu, 2003-06-12 at 07:47, Nigel Cunningham wrote:
> > TASK_SUSPENDED is a swsusp macro. What version of swsusp do you have
> > included in your kernel? (There were some compile problems fixed a while
> > ago - you probably have a version pre then).
>
> It may not be directly related to swsusp - it may be that in wiggling a
> patch I missed an #ifdef SWSUSP ...
>
> ..
>
> OK I looked there - its can_schedule() thats triggering it. I'm going
> to try a build without software suspend and see if I can reproduce. In
> the meantime, send me the .config file that triggered it. (And make sure
> you did 'make mrproper ; make [x/menu/old]config ; make dep ; make
> clean' ..)
>
> FWIW its 2.4.21-rc6 with the following suspend-related patches:
> - ACPI 20030523-2.4.21-rc3.diff
> - patch-acpi-acpi20021212-swsusp19.gz
> - patch-agp for swsusp on i810 motherboards
>
> > Regards,
> >
> > Nigel
> >
> > On Thu, 2003-06-12 at 21:37, Martin List-Petersen wrote:
> > > I tried to compile this (both on rc6 and rc7) and the compile fails with:
> > >
> > > kernel/kernel.o(.text+0x2d8): In function 'schedule':
> > > : undefined reference to 'TASK_SUSPENDED'
> > > kernel/kernel.o(.text+0x392): In function 'schedule':
> > > : undefined reference to 'TASK_SUSPENDED'
> > >
> > > The compile allready stated in the beginning:
> > > sched.c: In function 'schedule':
> > > sched.c:611: implicit declaration of function 'TASK_SUSPENDED'
> > >
> > > Any idea's what i can leave out to avoid these failures ?
> > >
> > > Regards,
> > > Martin List-Petersen
> > > martin at list-petersen dot dk
> > > --
> > > Q: What do you get when you cross the Godfather with an attorney?
> > > A: An offer you can't understand.
> > >
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > > Please read the FAQ at http://www.tux.org/lkml/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-06-12 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 9:37 implicid declaration of function task_suspended - Was: [PATCHSET] 2.4.21-rc6-dis3 released Martin List-Petersen
2003-06-12 11:47 ` Nigel Cunningham
2003-06-12 15:30 ` Disconnect
2003-06-12 16:10 ` Disconnect [this message]
2003-06-12 19:35 ` Nigel Cunningham
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=1055434247.11780.26.camel@slappy \
--to=kernel@gotontheinter.net \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@list-petersen.dk \
--cc=ncunningham@clear.net.nz \
/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