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 0001474]: toolchain build, arch x86_64 , variant core2 does not build
Date: Fri, 7 Sep 2007 11:55:54 -0700	[thread overview]
Message-ID: <6a159fc7ac57e67bc6483273eb8d8d2d@busybox.net> (raw)


The following issue has been CLOSED 
====================================================================== 
http://busybox.net/bugs/view.php?id=1474 
====================================================================== 
Reported By:                myopiate
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   1474
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     closed
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             08-27-2007 02:04 PDT
Last Modified:              09-07-2007 11:55 PDT
====================================================================== 
Summary:                    toolchain build, arch x86_64 , variant core2 does
not build
Description: 
Problem:
Configuration for the x86_64 architecture with core2 variant stops on
build.

Cause:
gcc-4.2.1 does not accept --with-tune=core2.  Toolchain build dies.

Workaround:
Attached patch works around the problem by using --with-tune=generic.
====================================================================== 

---------------------------------------------------------------------- 
 bernhardf - 09-07-07 11:55  
---------------------------------------------------------------------- 
See ML archives for the correct solution (default core2 if
!GCC_VERSION_THIS && !GCC_VERSION_THAT; gcc-4.3 does support -mtune=core2
just fine, so the proposed solution is not correct). 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-27-07 02:04  myopiate       New Issue                                    
08-27-07 02:04  myopiate       Status                   new => assigned     
08-27-07 02:04  myopiate       Assigned To               => buildroot       
08-27-07 02:04  myopiate       File Added: core2-generic.patch                  
 
09-07-07 11:55  bernhardf      Status                   assigned => closed  
09-07-07 11:55  bernhardf      Note Added: 0002731                          
======================================================================

             reply	other threads:[~2007-09-07 18:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07 18:55 bugs at busybox.net [this message]
2007-09-12 11:40 ` [Buildroot] [buildroot 0001474]: toolchain build, arch x86_64 , variant core2 does not build Roderick Taylor
2007-09-21  9:39   ` Bernhard Fischer
  -- strict thread matches above, loose matches on Subject: below --
2007-08-27  9:04 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=6a159fc7ac57e67bc6483273eb8d8d2d@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