From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] making buildroot for arm7tdmi static flat fails
Date: Mon, 15 Nov 2010 13:55:50 -0300 [thread overview]
Message-ID: <4CE16616.5090905@zacarias.com.ar> (raw)
In-Reply-To: <1289739946.19487.28.camel@cecilia.engel.home>
On 11/14/10 10:05, Dan Engel wrote:
> I have a follow-up:
>
> In the configuration that led to the above error, I had disabled global
> constructors and destructors in the uclibc configuration ("make
> uclibc-menuconfig").
>
> If I first try to build with global constructors and destructors
> enabled, it eventually gives an error (I think during gcc construction)
> about missing __fini_array and __init_array stuff. If I then change the
> configuration (using "make uclibc-menuconfig") to disable the global
> ctors and dtors and type "make" again, it builds to completion.
> Something in that two-step process gets me past the above error about
> lib/crti.o.
>
> However, when I try to compile and link a simple flat "hello," the
> following happens:
>
> dan at cecilia ~/tmp $ arm-linux-gcc -Wl,-elf2flt hello.c
> /mnt/local/armtc/usr/lib/gcc/arm-unknown-linux-uclibcgnueabi/4.3.5/../../../../arm-unknown-linux-uclibcgnueabi/bin/ld.real: error: no memory region specified for loadable section `.ARM.extab'
> collect2: ld returned 1 exit status
> dan at cecilia ~/tmp $
>
> Does anyone have any idea what I'm missing?
>
> Thanks,
> -Dan
Did you disable MMU support in uclibc's config and enable one of the
flat target file formats?
Regards.
next prev parent reply other threads:[~2010-11-15 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 5:28 [Buildroot] making buildroot for arm7tdmi static flat fails Dan Engel
2010-11-14 13:05 ` Dan Engel
2010-11-15 16:55 ` Gustavo Zacarias [this message]
2010-11-15 18:23 ` Thomas Petazzoni
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=4CE16616.5090905@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.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