public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ikke <ikke.lkml@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.10-bk3 seems to break CIFS
Date: Thu, 30 Dec 2004 23:06:19 +0100	[thread overview]
Message-ID: <297f4e01041230140630691359@mail.gmail.com> (raw)

When compiling a 2.6.10-bk3 based kernel (with some more patches, none
of them touching CIFS or ipv6 AFAIK), CIFS fails to build due to some
ipv6 error, although I haven't got IPv6 selected in my configuration.

Error message:
gcc -Wp,-MD,fs/cifs/.connect.o.d -nostdinc -iwithprefix include
-D__KERNEL__ -Iinclude  -Wall -Wstrict-prototypes -Wno-trigraphs
-fno-strict-aliasing -fno-common -O2     -fomit-frame-pointer -pipe
-msoft-float -mpreferred-stack-boundary=2 -fno-unit-at-a-time
-march=i686 -mtune=pentium4 -Iinclude/asm-i386/mach-default
-Wdeclaration-after-statement   -DMODULE -DKBUILD_BASENAME=connect
-DKBUILD_MODNAME=cifs -c -o fs/cifs/connect.o fs/cifs/connect.c
In file included from fs/cifs/connect.c:27:
include/linux/ipv6.h: In function `inet6_sk':
include/linux/ipv6.h:278: error: structure has no member named `pinet6'
make[2]: *** [fs/cifs/connect.o] Error 1
make[1]: *** [fs/cifs] Error 2
make: *** [fs] Error 2


Using GCC 3.4.3, Gentoo system.

When looking at the -bk3 diff [1] the pinet6 field seems to be removed.


I did not try to revert this patch and compile it, will try later.


Regards, Ikke


[1] http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv2.6%2Fsnapshots%2Fpatch-2.6.10-bk3.bz2;z=481

                 reply	other threads:[~2004-12-30 22:07 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=297f4e01041230140630691359@mail.gmail.com \
    --to=ikke.lkml@gmail.com \
    --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