From: Sven Joachim <svenjoac@gmx.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Eric Anholt <eric@anholt.net>, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: 2.6.36-rc2 build failure: implicit declaration of function 'seq_printf'
Date: Mon, 23 Aug 2010 10:06:42 +0200 [thread overview]
Message-ID: <87bp8tda7h.fsf@turtle.gmx.de> (raw)
Commit 6ef3d4278034982c13df87c4a51e0445f762d316 causes a build failure
for me:
,----
| CC [M] drivers/gpu/drm/i915/intel_overlay.o
| drivers/gpu/drm/i915/intel_overlay.c: In function 'intel_overlay_print_error_state':
| drivers/gpu/drm/i915/intel_overlay.c:1467: error: implicit declaration of function 'seq_printf'
| make[4]: *** [drivers/gpu/drm/i915/intel_overlay.o] Error 1
`----
Adding a line with
#include <linux/seq_file.h>
to intel_overlay.c fixes this. Looking at include/drm/*.h, I notice
that <linux/seq_file.h> is only #included if CONFIG_DEBUG_FS is set,
which is not the case in my configuration.
Sven
WARNING: multiple messages have this Message-ID (diff)
From: Sven Joachim <svenjoac@gmx.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: 2.6.36-rc2 build failure: implicit declaration of function 'seq_printf'
Date: Mon, 23 Aug 2010 10:06:42 +0200 [thread overview]
Message-ID: <87bp8tda7h.fsf@turtle.gmx.de> (raw)
Commit 6ef3d4278034982c13df87c4a51e0445f762d316 causes a build failure
for me:
,----
| CC [M] drivers/gpu/drm/i915/intel_overlay.o
| drivers/gpu/drm/i915/intel_overlay.c: In function 'intel_overlay_print_error_state':
| drivers/gpu/drm/i915/intel_overlay.c:1467: error: implicit declaration of function 'seq_printf'
| make[4]: *** [drivers/gpu/drm/i915/intel_overlay.o] Error 1
`----
Adding a line with
#include <linux/seq_file.h>
to intel_overlay.c fixes this. Looking at include/drm/*.h, I notice
that <linux/seq_file.h> is only #included if CONFIG_DEBUG_FS is set,
which is not the case in my configuration.
Sven
next reply other threads:[~2010-08-23 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 8:06 Sven Joachim [this message]
2010-08-23 8:06 ` 2.6.36-rc2 build failure: implicit declaration of function 'seq_printf' Sven Joachim
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=87bp8tda7h.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--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 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.