This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: compile error when using newer version ecos configuration tool
- To: "'Andrew Lunn'" <andrew dot lunn at ascom dot ch>, "'HuangQiang'" <jameshq at liverpool dot ac dot uk>
- Subject: RE: [ECOS] compile error when using newer version ecos configuration tool
- From: "Trenton D. Adams" <tadams at theone dot dnsalias dot com>
- Date: Mon, 12 Nov 2001 14:46:38 -0700
- Cc: "'eCos'" <ecos-discuss at sources dot redhat dot com>
I don't know what it stands for, but I know what it's used for.
Here's a quote from a Technical Article from MSDN which should be
relevant since bss is the same for ELF binaries as it is for PE binaries
as far as I know! :)
The size of the sections that the loader commits space for in the
virtual address space, but that don't take up any space in the disk
file. These sections don't need to have specific values at program
startup, hence the term uninitialized data. Uninitialized data usually
goes into a section called .bss.
> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com
> [mailto:ecos-discuss-owner@sources.redhat.com] On Behalf Of
> Andrew Lunn
> Sent: November 12, 2001 9:23 AM
> To: HuangQiang
> Cc: eCos
> Subject: Re: [ECOS] compile error when using newer version
> ecos configuration tool
>
>
> > /tools/H-i686-pc-cygwin/arm-elf/bin/ld: address 0x9817c of a.out
> > section .bss is not within region ram
> > collect2: ld returned 1 exit status
>
> Either something has gone wrong with the memory map, or you
> have a very large image. The linker is saying it cannot put
> the bss segment into RAM. Check your definitions of where the
> RAM starts and how long it is.
>
> Andrew
>
> PS. What does BSS stand for anyway? Answers on a post card please.
>