From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001615]: Can not build?
Date: Tue, 27 Nov 2007 23:04:08 -0800 [thread overview]
Message-ID: <98e48ae08c66837d871c6be10e5c5310@busybox.net> (raw)
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=1615
======================================================================
Reported By: linsample
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1615
Category: Other
Reproducibility: always
Severity: trivial
Priority: normal
Status: assigned
======================================================================
Date Submitted: 11-27-2007 22:28 PST
Last Modified: 11-27-2007 23:04 PST
======================================================================
Summary: Can not build?
Description:
Anybody knows the compile error when I try to build buildroot???
/home/sample/projects/LX_2618_RG_5_3_00r4_SRC/buildroot/toolchain_build_mips/gcc-4.2.1/gcc/crtstuff.
c:1: error: unsupported combination: -mabicalls -mabi=eabi
make[2]: *** [crtbegin.o] Error 1
make[2]: Leaving directory
`/home/sample/projects/LX_2618_RG_5_3_00r4_SRC/buildroot/toolchain_build_
mips/gcc-4.2.1-initial/gcc'
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory
`/home/sample/projects/LX_2618_RG_5_3_00r4_SRC/buildroot/toolchain_build_
mips/gcc-4.2.1-initial'
make: ***
[/home/sample/projects/LX_2618_RG_5_3_00r4_SRC/buildroot/toolchain_build_mips/gcc-4.2.1-in
itial/.compiled] Error 2
======================================================================
----------------------------------------------------------------------
linsample - 11-27-07 22:47
----------------------------------------------------------------------
I use Fedora Core 4
----------------------------------------------------------------------
UlfSamuelsson - 11-27-07 23:00
----------------------------------------------------------------------
Isn't EABI (-mabi=eabi) an ARM thing and not applicable to MIPS arch?
----------------------------------------------------------------------
linsample - 11-27-07 23:04
----------------------------------------------------------------------
But I dont do anything for latest buildroot source code.
My steps are as follows:
1. make menuconfig
only change CPU type to MIPS
2. make
I dont know why the compiler adds ARM related words?
Issue History
Date Modified Username Field Change
======================================================================
11-27-07 22:28 linsample New Issue
11-27-07 22:28 linsample Status new => assigned
11-27-07 22:28 linsample Assigned To => buildroot
11-27-07 22:46 linsample Issue Monitored: linsample
11-27-07 22:46 linsample Issue End Monitor: linsample
11-27-07 22:47 linsample Note Added: 0002982
11-27-07 23:00 UlfSamuelsson Note Added: 0002983
11-27-07 23:04 linsample Note Added: 0002984
======================================================================
next reply other threads:[~2007-11-28 7:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 7:04 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-24 20:55 [Buildroot] [buildroot 0001615]: Can not build? bugs at busybox.net
2008-04-25 8:25 ` Guillaume Dargaud
2007-11-28 7:57 bugs at busybox.net
2007-11-28 7:00 bugs at busybox.net
2007-11-28 6:47 bugs at busybox.net
2007-11-28 6:28 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=98e48ae08c66837d871c6be10e5c5310@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