Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001406]: ARM: gcc is not configured for the ARM cpu selected in the menuconfig
Date: Thu, 28 Jun 2007 04:04:55 -0700	[thread overview]
Message-ID: <1e4a2d8fc2187ef2b22d3c154c0ee092@bugs.busybox.net> (raw)


The following issue has been SUBMITTED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1406 
====================================================================== 
Reported By:                bjdooks
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   1406
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             06-28-2007 04:04 PDT
Last Modified:              06-28-2007 04:04 PDT
====================================================================== 
Summary:                    ARM: gcc is not configured for the ARM cpu selected
in the menuconfig
Description: 
The CPU selected in the menuconfig is not used to configure the gcc build
to use the configured CPU. This causes code to be built that will not run
on the target due to instructions that can never be executed.

If the cpu type is not specified, then not only is the compiler producing
builds of packages that are incorrect, but it will also produce an libgcc
with invalid instructions in it.

Passing CFLAGS with -mcpu=<configured-cpu> to the package builds was
considered as a posibility, but this will not ensure that libgcc is built
with the correct architecture flags.
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-28-07 04:04  bjdooks        New Issue                                    
06-28-07 04:04  bjdooks        Status                   new => assigned     
06-28-07 04:04  bjdooks        Assigned To               => buildroot       
06-28-07 04:04  bjdooks        File Added: gcc-pass-cpu-config.patch            
       
======================================================================

             reply	other threads:[~2007-06-28 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28 11:04 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-07-08 19:17 [Buildroot] [buildroot 0001406]: ARM: gcc is not configured for the ARM cpu selected in the menuconfig 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=1e4a2d8fc2187ef2b22d3c154c0ee092@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