From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Anton Altaparmakov <aia21@cam.ac.uk>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [uml-devel] Re: Partial fix! - Was: Re: [BUG report] UML linux-2.6 latest BK doesn't compile
Date: Mon, 07 Mar 2005 19:10:11 -0500 [thread overview]
Message-ID: <200503080010.j280ABbc005264@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Mon, 07 Mar 2005 20:44:48 +0100." <200503072044.49206.blaisorblade@yahoo.it>
blaisorblade@yahoo.it said:
> a) wrong because you say __GNUC_PATCHLEVEL__ > 4 rather than >=
Correct, this is now fixed.
> b) wrong because for he the link failed on __bb_init_func at the
> beginning. So in the case you need to export BOTH symbols.
Incorrect, the link failure was caused by trying to export __bb_init_func,
which makes a reference to it, which was subsequently not being resolved.
You can't export a symbol which doesn't exist.
Jeff
next prev parent reply other threads:[~2005-03-07 22:10 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
2005-03-07 19:44 ` [uml-devel] " Blaisorblade
2005-03-08 0:10 ` Jeff Dike [this message]
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=200503080010.j280ABbc005264@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=aia21@cam.ac.uk \
--cc=blaisorblade@yahoo.it \
--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