All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: clem@clem.clem-digital.net
Cc: linux-kernel@vger.kernel.org, chuck.lever@oracle.com, neilb@suse.de
Subject: Re: 2.6.20-git8 fails compile -- net/built-in.o __ipv6_addr_type
Date: Mon, 12 Feb 2007 20:20:54 -0800 (PST)	[thread overview]
Message-ID: <20070212.202054.104031463.davem@davemloft.net> (raw)
In-Reply-To: <200702130110.l1D1ADai012897@clem.clem-digital.net>

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. :-)


  parent reply	other threads:[~2007-02-13  4:20 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 [this message]
2007-02-15  0:59   ` Chuck Lever

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=20070212.202054.104031463.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=chuck.lever@oracle.com \
    --cc=clem@clem.clem-digital.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.