Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Asbjoern Laurberg <asl@thrane.com>
To: buildroot@busybox.net
Subject: [Buildroot] compile error with 'crtstuff.c'
Date: Mon, 05 Oct 2009 11:18:12 +0200	[thread overview]
Message-ID: <4AC9B9D4.5020305@thrane.com> (raw)
In-Reply-To: <1D6034426110564DA0DEA9EE9793B38357C834B900@NBE-MBX01.americas.swk.pri>

Heyendal, Carl wrote:
> Hi,

Hi,

> /home/heyendal/buildroot/output/toolchain/gcc-4.3.4/libgcc/../gcc/crtstuff.c 
> -DCRT_BEGIN
> /home/heyendal/buildroot/output/toolchain/gcc-4.3.4/libgcc/../gcc/crtstuff.c: 
> In function '__do_global_dtors_aux':
> /home/heyendal/buildroot/output/toolchain/gcc-4.3.4/libgcc/../gcc/crtstuff.c:306: 
> error: '__DTOR_LIST__' undeclared (first use in this function)
> /home/heyendal/buildroot/output/toolchain/gcc-4.3.4/libgcc/../gcc/crtstuff.c:306: 
> error: (Each undeclared identifier is reported only once
> /home/heyendal/buildroot/output/toolchain/gcc-4.3.4/libgcc/../gcc/crtstuff.c:306: 
> error: for each function it appears in.)

To get GCC compiling in Buildroot with a ARM926 + EABI-configuration the 
following post+patch was the solution:

http://www.mail-archive.com/gcc-bugs at gcc.gnu.org/msg115966.html

-- 
Best regards,
Asbjoern Laurberg
Development Engineer
Thrane & Thrane A/S

  reply	other threads:[~2009-10-05  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 18:37 [Buildroot] compile error with 'crtstuff.c' Heyendal, Carl
2009-10-05  9:18 ` Asbjoern Laurberg [this message]
2009-10-05 20:44   ` Heyendal, Carl
  -- strict thread matches above, loose matches on Subject: below --
2009-10-02 20:20 Heyendal, Carl

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=4AC9B9D4.5020305@thrane.com \
    --to=asl@thrane.com \
    --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