The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: clem@clem.clem-digital.net, linux-kernel@vger.kernel.org, neilb@suse.de
Subject: Re: 2.6.20-git8 fails compile -- net/built-in.o __ipv6_addr_type
Date: Wed, 14 Feb 2007 16:59:57 -0800	[thread overview]
Message-ID: <45D3B08D.6040602@oracle.com> (raw)
In-Reply-To: <20070212.202054.104031463.davem@davemloft.net>

[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]

David Miller wrote:
> From: Pete Clements <clem@clem.clem-digital.net>
> Date: Mon, 12 Feb 2007 20:10:13 -0500 (EST)
> 
>> 2.6.20-git8 fails compile:
>>
>>   CHK     include/linux/compile.h
>>   UPD     include/linux/compile.h
>>   CC      init/version.o
>>   LD      init/built-in.o
>>   LD      .tmp_vmlinux1
>> net/built-in.o: In function `svc_udp_recvfrom':
>> svcsock.c:(.text+0x61be4): undefined reference to `__ipv6_addr_type'
>> make: *** [.tmp_vmlinux1] Error 1
> 
> Chuck, you will need to somehow make CONFIG_SUNRPC "depend" upon IPV6
> so that if IPV6 is modular SUNRPC can only be built modular.
> 
> Otherwise the symbols won't resolve correctly.
> 
> Everybody hits this problem when they add ipv6 support to
> something. :-)
> 

Interestingly, doing a build with ALLYESCONFIG, ALLMODCONFIG, and 
ALLNOCONFIG doesn't catch this type of error.

I just did a copy+paste and that brought in ipv6_addr_type.  So I'm not 
convinced it's really needed here.  David, can you take a look at the 
code in svcsock.c right around the ipv6_addr_type() call and let me know 
if we can avoid that call outright?

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 265 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture Linux Projects Group
email;internet:chuck dot lever at nospam oracle dot com
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
version:2.1
end:vcard


      reply	other threads:[~2007-02-15  1:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13  1:10 2.6.20-git8 fails compile -- net/built-in.o __ipv6_addr_type Pete Clements
2007-02-13  2:12 ` Andrew Morton
2007-02-13  2:13   ` YOSHIFUJI Hideaki / 吉藤英明
2007-02-13  2:35     ` Pete Clements
2007-02-13  2:52       ` Neil Brown
2007-02-13  4:23         ` David Miller
2007-02-13  2:55       ` YOSHIFUJI Hideaki / 吉藤英明
2007-02-13  3:13         ` Pete Clements
2007-02-24 22:50         ` Adrian Bunk
2007-02-25  0:54           ` David Miller
2007-02-13  4:22   ` David Miller
2007-02-13  4:20 ` David Miller
2007-02-15  0:59   ` Chuck Lever [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=45D3B08D.6040602@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=clem@clem.clem-digital.net \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    /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