public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Dave Jones <davej@suse.de>
Cc: Ben Pharr - Lists <ben-lists@benpharr.com>, linux-kernel@vger.kernel.org
Subject: Re: Missing Files
Date: Wed, 5 Dec 2001 23:23:13 +0000	[thread overview]
Message-ID: <20011205232313.C27558@flint.arm.linux.org.uk> (raw)
In-Reply-To: <5.1.0.14.0.20011205160555.00a10ec0@sunset.olemiss.edu> <Pine.LNX.4.33.0112052323440.18145-100000@Appserv.suse.de>
In-Reply-To: <Pine.LNX.4.33.0112052323440.18145-100000@Appserv.suse.de>; from davej@suse.de on Wed, Dec 05, 2001 at 11:25:23PM +0100

On Wed, Dec 05, 2001 at 11:25:23PM +0100, Dave Jones wrote:
> On Wed, 5 Dec 2001, Ben Pharr - Lists wrote:
> > gcc -D__KERNEL__ -I/usr/src/linux-2.4.17-pre4/include -Wall
> > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> > -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
> > -march=i686  -E -D__GENKSYMS__ sa1100fb.c
> > | /sbin/genksyms  -k 2.4.17 >
> > /usr/src/linux-2.4.17-pre4/include/linux/modules/sa1100fb.ver.tmp
> > sa1100fb.c:164: linux/cpufreq.h: No such file or directory
> 
> Looks like an incomplete ARM sync. But why are you trying to
> build sa1100fb on x86 anyway ?

The files are there.  This is just one of the kbuild 2.4 disease -
unconditionally making module symbols for all files specified in
export-objs.  Hopefully kbuild 2.5 fixes this.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


      reply	other threads:[~2001-12-05 23:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05 22:07 Missing Files Ben Pharr - Lists
2001-12-05 22:25 ` Dave Jones
2001-12-05 23:23   ` Russell King [this message]

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=20011205232313.C27558@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=ben-lists@benpharr.com \
    --cc=davej@suse.de \
    --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