linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test2 make failure
Date: Mon, 28 Jul 2003 21:38:44 -0400	[thread overview]
Message-ID: <200307282138.44960.gene.heskett@verizon.net> (raw)

Greets everybody;

Here is one I haven't seen before, and its my first thru 4th try at 
building 2.6.0-test2.

The error exit looks like this:
-------------------------
gcc  -DMODVERSIONS -include 
/lib/modules/2.4.22-pre8/build/include/linux/modversions.h 
-D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. 
-Ikernel/include -I/usr/local/include 
-I/lib/modules/2.4.22-pre8/build/include  -nostdinc -I 
/usr/lib/gcc-lib/i386-redhat-linux/3.2/include  -Wall -O2   -c 
kernel/busses/i2c-nforce2.c -o kernel/busses/i2c-nforce2.o
kernel/busses/i2c-nforce2.c: In function `nforce2_probe_smb':
kernel/busses/i2c-nforce2.c:337: structure has no member named `owner'
make: *** [kernel/busses/i2c-nforce2.o] Error 1
--------------------------
Please note the wrong /lib/modules/version reference above!  It 
faintly resembles the i2c errors, errors made because the version is 
apparently being extracted from a uname return by the Makefile.

Backtracking up thru half a meg of shell history, I find this:
---------------
Ahh, never mind, I see all sorts of warnings about NOT building in i2c 
stuff, it must be modules, and the fscking makefile is broken anyway 
since it determines the architecture its being built from via the use 
of uname, which of course is reporting 2.4.22-pre8.  Like I said, the 
Makefile in the i2c subdir is busted, and I will have to build, and 
boot to, 2.6.0-test2 before I can build the hardware sensors stuff...

That I can fix...

Ok, back to the real exit above, I've no doubt got something fubared, 
but I do have a GForce2 MX-200 32 meg card it would be nice to be 
able to use since its the only video in this machine :-)

Do I have to turn that off, build to the vga screen first, boot to it, 
and then rebuild it so the module versions are correct before this 
will build?

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.


                 reply	other threads:[~2003-07-29  1:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200307282138.44960.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).