From: Adrian Bunk <bunk@stusta.de>
To: Jeff Dike <jdike@addtoit.com>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>,
Blaisorblade <blaisorblade@yahoo.it>,
lkml <linux-kernel@vger.kernel.org>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: Partial fix! - Was: Re: [BUG report] UML linux-2.6 latest BK doesn't compile
Date: Sat, 5 Mar 2005 19:31:34 +0100 [thread overview]
Message-ID: <20050305183134.GH6373@stusta.de> (raw)
In-Reply-To: <200503051945.j25JjIB5003539@ccure.user-mode-linux.org>
On Sat, Mar 05, 2005 at 02:45:18PM -0500, Jeff Dike wrote:
> aia21@cam.ac.uk said:
> > Yes. I finally found a way to get it to compile. Compiling without
> > TT mode and WITHOUT static build it still fails with the same problem
> > (__bb_init_func problem I already reported). But compiling without TT
> > but WITH static build the __bb_init_func problem goes away but instead
> > I get a __gcov_init missing symbol in my modules.
> >
> > Note I have gcc-3.3.4-11 (SuSE 9.2) and it defines __gcov_init. So I
> > added this as an export symbol and lo and behold the kernel and
> > modules compiled and I am now up an running with UML and NTFS as a
> > module. (-:
>
> Can you try this patch? It exports either __gcov_init or __bb_init_func
> depending on your gcc version.
>
> Jeff
>
> Index: linux-2.6.10/arch/um/kernel/gmon_syms.c
> ===================================================================
> --- linux-2.6.10.orig/arch/um/kernel/gmon_syms.c 2005-02-28 17:22:29.000000000 -0500
> +++ linux-2.6.10/arch/um/kernel/gmon_syms.c 2005-03-02 12:19:14.000000000 -0500
> @@ -5,8 +5,14 @@
>
> #include "linux/module.h"
>
> +#if __GNUC__ > 3 || (__GNUC__ == 3 && __GNUC_MINOR__ > 3) || \
> + (__GNUC__ == 3 && __GNUC_MINOR__ == 3 && __GNUC_PATCHLEVEL__ > 4)
This line has to be something like
( (__GNUC__ == 3 && __GNUC_MINOR__ == 3 && __GNUC_PATCHLEVEL__ >= 4) && \
HEAVILY_PATCHES_SUSE_GCC )
I hope SuSE has added some #define to distinguish what they call
"gcc 3.3.4" from GNU gcc 3.3.4 ...
> +extern void __gcov_init(void *);
> +EXPORT_SYMBOL(__gcov_init);
> +#else
> extern void __bb_init_func(void *);
> EXPORT_SYMBOL(__bb_init_func);
> +#endif
>...
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-03-05 18:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 10:09 [BUG report] UML linux-2.6 latest BK doesn't compile Anton Altaparmakov
2005-02-08 10:22 ` Blaisorblade
2005-02-08 10:40 ` Anton Altaparmakov
2005-02-08 17:48 ` [uml-devel] " Blaisorblade
2005-02-08 22:21 ` Jeff Dike
2005-02-08 18:29 ` Jeff Dike
2005-02-08 17:37 ` Blaisorblade
2005-02-08 22:22 ` Jeff Dike
2005-02-14 11:35 ` Partial fix! - Was: " Anton Altaparmakov
2005-02-16 18:27 ` [uml-devel] " Blaisorblade
2005-03-05 19:45 ` Jeff Dike
2005-03-05 18:31 ` Adrian Bunk [this message]
2005-03-07 19:44 ` [uml-devel] " Blaisorblade
2005-03-08 0:10 ` Jeff Dike
2005-03-13 20:06 ` Blaisorblade
[not found] ` <EBD0B8CF381E8B44BB99E8EA137E27C0021AD010@CPEXBE-EML06.kpnsp.local>
2006-09-09 9:31 ` Blaisorblade
2006-09-11 15:27 ` Jeff Dike
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=20050305183134.GH6373@stusta.de \
--to=bunk@stusta.de \
--cc=aia21@cam.ac.uk \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--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