All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike@bilbo.math.uni-mannheim.de>
To: linux-kernel@vger.kernel.org
Subject: Re: build error in 2.5.45
Date: Mon, 4 Nov 2002 10:16:07 +0100	[thread overview]
Message-ID: <200211041016.07936@bilbo.math.uni-mannheim.de> (raw)

Von Hiro Yoshioka:

>   ld -m elf_i386 -e stext -T arch/i386/vmlinux.lds.s
>   arch/i386/kernel/head.o arch/i386/kernel/init_task.o  init/built-in.o
>   --start-group  arch/i386/kernel/built-in.o  arch/i386/mm/built-in.o 
>   arch/i386/mach-generic/built-in.o  kernel/built-in.o  mm/built-in.o 
>   fs/built-in.o  ipc/built-in.o  security/built-in.o  crypto/built-in.o
>    lib/lib.a  arch/i386/lib/lib.a  drivers/built-in.o  sound/built-in.o
>    arch/i386/pci/built-in.o  arch/i386/oprofile/built-in.o 
>   net/built-in.o --end-group  -o .tmp_vmlinux1
> net/built-in.o: In function `p8022_request':
> net/built-in.o(.text+0xf4b9): undefined reference to
> `llc_build_and_send_ui_pkt' net/built-in.o: In function
> `register_8022_client': net/built-in.o(.text+0xf502): undefined
> reference to `llc_sap_open' net/built-in.o: In function
> `unregister_8022_client': net/built-in.o(.text+0xf52e): undefined
> reference to `llc_sap_close' net/built-in.o: In function
> `snap_request': net/built-in.o(.text+0xf663): undefined reference to
> `llc_build_and_send_ui_pkt' net/built-in.o: In function `snap_init':
> net/built-in.o(.init.text+0x613): undefined reference to `llc_sap_open'
> make: *** [.tmp_vmlinux1] Error 1

I had the same problem here. This one helped:

326c326,330
< # CONFIG_TR is not set
---
> CONFIG_TR=y
> # CONFIG_IBMTR is not set
> CONFIG_TMS380TR=m
> CONFIG_TMSISA=m
> # CONFIG_SMCTR is not set

Eike

             reply	other threads:[~2002-11-04  9:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04  9:16 Rolf Eike Beer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-01  3:56 build error in 2.5.45 Hiro Yoshioka

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=200211041016.07936@bilbo.math.uni-mannheim.de \
    --to=eike@bilbo.math.uni-mannheim.de \
    --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 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.