Bug 113878

Summary: Kernel does not compile with custom .config
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Stefan Nordhausen <nordhaus>
Component: KernelAssignee: Olaf Kirch <okir>
Status: RESOLVED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Beta 2   
Target Milestone: ---   
Hardware: i686   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: My .config for the kernel

Description Stefan Nordhausen 2005-08-29 14:48:41 UTC
Compiling the kernel with Suse's default settings works perfect. But when I use
my custom .config files (based on Suse's default settings) then I get the
following error:
 CC [M]  net/netfilter/nf_conntrack_core.o
net/netfilter/nf_conntrack_core.c: In function ‘nf_conntrack_in’:
net/netfilter/nf_conntrack_core.c:854: warning: ‘set_reply’ may be used
uninitialized in this function
  CC [M]  net/netfilter/nf_conntrack_standalone.o
  CC [M]  net/netfilter/nf_conntrack_l3proto_generic.o
  CC [M]  net/netfilter/nf_conntrack_proto_generic.o
  CC [M]  net/netfilter/nf_conntrack_proto_tcp.o
  CC [M]  net/netfilter/nf_conntrack_proto_udp.o
net/netfilter/nf_conntrack_proto_udp.c: In function ‘csum6’:
net/netfilter/nf_conntrack_proto_udp.c:158: error: dereferencing pointer to
incomplete type
net/netfilter/nf_conntrack_proto_udp.c:158: error: dereferencing pointer to
incomplete type
make[2]: *** [net/netfilter/nf_conntrack_proto_udp.o] Fehler 1
make[1]: *** [net/netfilter] Fehler 2
make: *** [net] Fehler 2

Only thing I changed in the .config is (IIRC)
-removed _lots_ of stuff
-optimized for Pentium M

When you fix it please also post the patch here, since downloading 40MB via ISDN
is no fun.
Comment 1 Stefan Nordhausen 2005-08-29 14:49:57 UTC
Created attachment 48022 [details]
My .config for the kernel
Comment 2 Hubert Mantel 2005-08-31 15:11:58 UTC
Custom built kernels are not supported. Olaf, feel free to close as WONTFIX or
INVALID
Comment 3 Olaf Kirch 2005-08-31 15:22:51 UTC
I agree with Hubert here. We will of course look into any patches you 
have that fix this problem for you, and consider including them.