Linux PPP protocol development
 help / color / mirror / Atom feed
From: James Chapman <jchapman@katalix.com>
To: linux-ppp@vger.kernel.org
Subject: Re: build #309 failed for 2.6.23-rc1-gd941cf5 in linux/drivers/net/pppol2tp.c
Date: Mon, 30 Jul 2007 11:14:16 +0000	[thread overview]
Message-ID: <46ADC808.204@katalix.com> (raw)
In-Reply-To: <200707272022.50619.toralf.foerster@gmx.de>

Hi Toralf,

Toralf Förster wrote:
> Hello,
> 
> the build with the attached .config failed, make ends with:
> ...
>   CC      arch/i386/lib/usercopy.o
>   AR      arch/i386/lib/lib.a
>   GEN     .version
>   CHK     include/linux/compile.h
>   UPD     include/linux/compile.h
>   CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> drivers/built-in.o: In function `pppol2tp_getsockopt':
> pppol2tp.c:(.text+0x454dd): undefined reference to `udp_prot'
> drivers/built-in.o: In function `pppol2tp_setsockopt':
> pppol2tp.c:(.text+0x46771): undefined reference to `udp_prot'
> drivers/built-in.o: In function `pppol2tp_sendmsg':
> pppol2tp.c:(.text+0x4753d): undefined reference to `ip_queue_xmit'
> drivers/built-in.o: In function `pppol2tp_xmit':
> pppol2tp.c:(.text+0x47a64): undefined reference to `ip_queue_xmit'
> make: *** [.tmp_vmlinux1] Error 1

I don't understand how udp_prot or ip_queue_xmit could ever be 
undefined. 2.6.23-rc1 builds just fine for me. Is this the standard 
kernel from kernel.org?

-- 
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development


  reply	other threads:[~2007-07-30 11:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 18:22 build #309 failed for 2.6.23-rc1-gd941cf5 in linux/drivers/net/pppol2tp.c Toralf Förster
2007-07-30 11:14 ` James Chapman [this message]
2007-07-30 11:38 ` James Chapman
2007-07-30 11:46 ` Toralf Förster

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=46ADC808.204@katalix.com \
    --to=jchapman@katalix.com \
    --cc=linux-ppp@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