From: Peter <peter.repliesignored@rimuhosting.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] __wrap_malloc compile error without CONFIG_MODE_TT
Date: Fri, 05 Nov 2004 15:59:04 +1300 [thread overview]
Message-ID: <418AEC78.2010502@rimuhosting.com> (raw)
Hi. I just compiled 2.6.9 + uml-2.6.9-bb1.patch.bz2 and got a compile
error with CONFIG_MODE_TT turned off. Posting here in case it is of
interest to anyone.
diff workingconfig brokenconfig
14c14,15
< CONFIG_MODE_TT=y
---
> # CONFIG_MODE_TT is not set
> # CONFIG_STATIC_LINK is not set
22d22
< # CONFIG_SMP is not set
276a277,279
> # CONFIG_NET_SCH_CLK_JIFFIES is not set
> # CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set
> # CONFIG_NET_SCH_CLK_CPU is not set
LD lib/built-in.o
AR 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
arch/um/kernel/built-in.o(.text+0x1a5f): In function `__wrap_malloc':
arch/um/kernel/main.c:192: undefined reference to `tracing_pid'
arch/um/kernel/built-in.o(.text+0x1ade): In function `__wrap_free':
arch/um/kernel/main.c:236: undefined reference to `tracing_pid'
arch/um/kernel/built-in.o(.text+0x1b21):arch/um/kernel/main.c:240:
undefined reference to `tracing_pid'
arch/um/kernel/built-in.o(.text+0x6a7b): In function `sig_handler':
arch/um/kernel/trap_user.c:108: undefined reference to
`sig_handler_common_tt'
arch/um/kernel/built-in.o(.text+0x6abe): In function `alarm_handler':
arch/um/kernel/trap_user.c:121: undefined reference to
`sig_handler_common_tt'
arch/um/kernel/built-in.o(.text+0x6a5a): In function `usr2_handler':
arch/um/kernel/trap_user.c:80: undefined reference to `syscall_handler_tt'
arch/um/kernel/built-in.o(.text+0x72a3): In function `not_dead_yet':
arch/um/kernel/umid.c:192: undefined reference to `tracing_pid'
arch/um/drivers/built-in.o(.text+0x36f8): In function `register_winch':
arch/um/drivers/chan_user.c:153: undefined reference to `is_tracer_winch'
collect2: ld returned 1 exit status
KSYM .tmp_kallsyms1.S
nm: .tmp_vmlinux1: No such file or directory
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
arch/um/kernel/built-in.o(.text+0x1a5f): In function `__wrap_malloc':
arch/um/kernel/main.c:192: undefined reference to `tracing_pid'
arch/um/kernel/built-in.o(.text+0x1ade): In function `__wrap_free':
arch/um/kernel/main.c:236: undefined reference to `tracing_pid'
arch/um/kernel/built-in.o(.text+0x1b21):arch/um/kernel/main.c:240:
undefined reference to `tracing_pid'
arch/um/kernel/built-in.o(.text+0x6a7b): In function `sig_handler':
arch/um/kernel/trap_user.c:108: undefined reference to
`sig_handler_common_tt'
arch/um/kernel/built-in.o(.text+0x6abe): In function `alarm_handler':
arch/um/kernel/trap_user.c:121: undefined reference to
`sig_handler_common_tt'
arch/um/kernel/built-in.o(.text+0x6a5a): In function `usr2_handler':
arch/um/kernel/trap_user.c:80: undefined reference to `syscall_handler_tt'
arch/um/kernel/built-in.o(.text+0x72a3): In function `not_dead_yet':
arch/um/kernel/umid.c:192: undefined reference to `tracing_pid'
arch/um/drivers/built-in.o(.text+0x36f8): In function `register_winch':
arch/um/drivers/chan_user.c:153: undefined reference to `is_tracer_winch'
collect2: ld returned 1 exit status
make: *** [.tmp_vmlinux2] Error 1
make linux
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2004-11-05 2:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 2:59 Peter [this message]
2004-11-05 19:42 ` [uml-devel] __wrap_malloc compile error without CONFIG_MODE_TT Blaisorblade
2004-11-09 2:17 ` [uml-devel] Re: 2.6.9-bb1, 2.4.27-bs1, SKAS3/2.6-V7 released Peter
2004-11-09 18:35 ` Blaisorblade
2004-11-09 23:12 ` Peter
2004-11-10 8:43 ` stian
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=418AEC78.2010502@rimuhosting.com \
--to=peter.repliesignored@rimuhosting.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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