From: Gary Thomas <gthomas@cygnus.co.uk>
To: Grant Edwards <grante@visi.com>
Cc: ecos-discuss@sourceware.cygnus.com, Nicholas_Clarey@ivesco.co.uk
Subject: Re: [ECOS] Building rommable images for the AEB-1C
Date: Thu, 06 Jan 2000 07:01:00 -0000 [thread overview]
Message-ID: <XFMail.000106080141.gthomas@cygnus.co.uk> (raw)
In-Reply-To: <20000106085025.A26913@visi.com>
On 06-Jan-00 Grant Edwards wrote:
>
>> > /usr/cygnus/ecosSWtools-arm-990321/i686-pc-linux-gnu/lib/gcc-lib/arm-elf/2.9
>> >
>> > -ecosSWtools-arm-990321/../../../../arm-elf/bin/ld: warning: no memory
>> > region specified for section `.glue_7'
>> > /usr/cygnus/ecosSWtools-arm-990321/i686-pc-linux-gnu/lib/gcc-lib/arm-elf/2.9
>> >
>> > -ecosSWtools-arm-990321/../../../../arm-elf/bin/ld: warning: no memory
>> > region specified for section `.glue_7t'
>>
>> I don't understand these warnings at all [yes, I know what they mean, I just
>> don't know how you created them].
>
> I've always gotten the "glue" sections when I build stuff for the ARM.
> I had to add an output section to the target.ld file to make the
> linker happy:
>
> .glue ALIGN (0x1) : { . = . ; *(.glue*) } > ram
>
This sounds like a toolchain problem. The ".glue" sections should only be present
if compiling in THUMB mode.
However, if they are indeed empty, then this should not be a problem to just ignore
the warnings.
next prev parent reply other threads:[~2000-01-06 7:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-06 4:38 Nicholas_Clarey
2000-01-06 5:00 ` Gary Thomas
2000-01-06 6:50 ` Grant Edwards
2000-01-06 7:01 ` Gary Thomas [this message]
2000-01-06 7:03 ` Dan Hovang
2000-01-06 5:40 Nicholas_Clarey
[not found] <OF3C6DA87D.CDC4B358-ON8025685E.004A10DF@ivesco.co.uk>
2000-01-06 6:45 ` Gary Thomas
[not found] <OF7B928FC7.8F137C30-ON8025685E.005316F3@ivesco.co.uk>
2000-01-06 7:15 ` Gary Thomas
2000-01-07 6:46 ` Dan Hovang
2000-01-07 7:19 ` Gary Thomas
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=XFMail.000106080141.gthomas@cygnus.co.uk \
--to=gthomas@cygnus.co.uk \
--cc=Nicholas_Clarey@ivesco.co.uk \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=grante@visi.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).