From: Greg Ungerer <gerg@snapgear.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.56: undefined reference to `_ebss' from drivers/mtd/maps/uclinux.c
Date: Mon, 13 Jan 2003 17:23:21 +1000 [thread overview]
Message-ID: <3E226969.5080406@snapgear.com> (raw)
In-Reply-To: <20030112095559.GT21826@fs.tum.de>
Hi Adrian,
Adrian Bunk wrote:
> trying to compile 2.5.56 with CONFIG_MTD_UCLINUX fails on i386 with
> undefined reference to `_ebss'
> at the final linking.
>
> It seems _ebss is only defined on the architectures m68knommu and v850?
Hmm, currently that is correct. There doesn't appear to be a
"standard" symbol name applied to the immediate end of the bss
section. Different architectures are using different names:
_ebss -- m68knommu, v850
__bss_stop -- i386, alpha, ppc, s390
__bss_end -- x86_64
_end -- mips, parisc, sparc, (actually most have this)
Actually it looks like _end is probably closer, it seems to
almost always fall strait after the bss, on just about every
architecture that has it.
Come to think of it _end is probably more appropriate anyway.
Since that code is trying to find the location of something
concatenated to the end of the kernel image.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Wizard EMAIL: gerg@snapgear.com
SnapGear Pty Ltd PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: www.SnapGear.com
next prev parent reply other threads:[~2003-01-13 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 9:55 2.5.56: undefined reference to `_ebss' from drivers/mtd/maps/uclinux.c Adrian Bunk
2003-01-13 7:23 ` Greg Ungerer [this message]
2003-03-20 14:59 ` Adrian Bunk
2003-03-20 16:00 ` [patch] " Adrian Bunk
2003-03-21 0:48 ` Greg Ungerer
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=3E226969.5080406@snapgear.com \
--to=gerg@snapgear.com \
--cc=bunk@fs.tum.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.