From: "Johnny Q. Hacker" <trelane@jakob.neurotek.dyndns.org>
To: linux-kernel@vger.kernel.org
Subject: 2.5.27 build errors - linux/i2c-old.h
Date: Sun, 21 Jul 2002 16:45:37 -0500 [thread overview]
Message-ID: <20020721214537.GA24886@ksu.edu> (raw)
Hello.
We're moving, or I'd track thisone down meself. I'd guess that it'll
be fairly easy to rectify.
gcc -E -Wp,-MD,/usr/local/src/kernel/linux-2.5.27/include/linux/modules/drivers/media/video/.i2c-old.ver.d -D__KERNEL__ -I/usr/local/src/kernel/linux-2.5.27/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix include -DMODULE -DKBUILD_BASENAME=i2c_old -D__GENKSYMS__ i2c-old.c | /sbin/genksyms -k 2.5.27 > /usr/local/src/kernel/linux-2.5.27/include/linux/modules/drivers/media/video/i2c-old.ver.tmp
i2c-old.c:17: linux/i2c-old.h: No such file or directory
make[5]: *** [/usr/local/src/kernel/linux-2.5.27/include/linux/modules/drivers/media/video/i2c-old.ver] Error 1
make[5]: Leaving directory `/usr/local/src/kernel/linux-2.5.27/drivers/media/video'
make[4]: *** [video] Error 2
make[4]: Leaving directory `/usr/local/src/kernel/linux-2.5.27/drivers/media'
make[3]: *** [media] Error 2
make[3]: Leaving directory `/usr/local/src/kernel/linux-2.5.27/drivers'
make[2]: *** [_sfdep_drivers] Error 2
make[2]: Leaving directory `/usr/local/src/kernel/linux-2.5.27'
make[1]: *** [include/linux/modversions.h] Error 2
make[1]: Leaving directory `/usr/local/src/kernel/linux-2.5.27'
make: *** [.hdepend] Error 2
--
"We're moving toward a world where all the capabilities of the Internet
are reprocessed through a single filter, with Microsoft's business plan
behind it." Mozilla's Mitchell Baker,
http://news.com.com/2100-1023-941926.html
next reply other threads:[~2002-07-21 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-21 21:45 Johnny Q. Hacker [this message]
2002-07-21 21:49 ` 2.5.27 build errors - linux/i2c-old.h Dave Jones
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=20020721214537.GA24886@ksu.edu \
--to=trelane@jakob.neurotek.dyndns.org \
--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