From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001405]: ARM OABI builds fail for gcc 4.x
Date: Tue, 26 Jun 2007 06:50:47 -0700 [thread overview]
Message-ID: <89c9717b681471690bf553eee0232c81@bugs.busybox.net> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1405
======================================================================
Reported By: bjdooks
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1405
Category: Architecture Specific
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 06-26-2007 06:50 PDT
Last Modified: 06-26-2007 06:50 PDT
======================================================================
Summary: ARM OABI builds fail for gcc 4.x
Description:
ARM OABI configured builds cannot produce working gcc output due to missing
items in libgcc.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
06-26-07 06:50 bjdooks New Issue
06-26-07 06:50 bjdooks Status new => assigned
06-26-07 06:50 bjdooks Assigned To => buildroot
06-26-07 06:50 bjdooks File Added: buildroot-gcc-412-oabi.build
======================================================================
next reply other threads:[~2007-06-26 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 13:50 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-26 13:56 [Buildroot] [buildroot 0001405]: ARM OABI builds fail for gcc 4.x bugs at busybox.net
2007-06-26 14:17 bugs at busybox.net
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=89c9717b681471690bf553eee0232c81@bugs.busybox.net \
--to=bugs@busybox.net \
--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