Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kuten Ivan <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001543]: gcc 4.1.2 libmudflap fails to build due to missing execinfo.h
Date: Fri, 19 Oct 2007 09:31:12 -0100	[thread overview]
Message-ID: <47188770.1070704@promwad.com> (raw)
In-Reply-To: <e73b1f587b0c993034a1396b7e2cc5d3@bugs.uclibc.org>

bugs at busybox.net wrote:
> The following issue has been SUBMITTED. 
> ====================================================================== 
> http://busybox.net/bugs/view.php?id=1543 
> ====================================================================== 
> Reported By:                hmoffatt
> Assigned To:                buildroot
> ====================================================================== 
> Project:                    buildroot
> Issue ID:                   1543
> Category:                   Architecture Specific
> Reproducibility:            always
> Severity:                   major
> Priority:                   normal
> Status:                     assigned
> ====================================================================== 
> Date Submitted:             10-19-2007 01:21 PDT
> Last Modified:              10-19-2007 01:21 PDT
> ====================================================================== 
> Summary:                    gcc 4.1.2 libmudflap fails to build due to missing
> execinfo.h
> Description: 
> During the gcc-4.1.2-final build, libmudflap files to compile due to
> missing execinfo.h. configure detects that execinfo.h exists but is
> unusable, but that's because it used the wrong cpp and found the host
> version instead.
> 
> The fix is to pass CPP=<target_cpp>, as in the attached patch.
> ====================================================================== 
> 
> Issue History 
> Date Modified   Username       Field                    Change               
> ====================================================================== 
> 10-19-07 01:21  hmoffatt       New Issue                                    
> 10-19-07 01:21  hmoffatt       Status                   new => assigned     
> 10-19-07 01:21  hmoffatt       Assigned To               => buildroot       
> 10-19-07 01:21  hmoffatt       File Added: br-gcc412-cpp-fix                    
> ======================================================================
> 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot

Hi hmoffatt,

Is that bug specific to "gcc-4.1.2 + oabi + soft float" configuration?
Because I remember to build&run all correctly with "gcc-4.1.2 + eabi + no soft float".

BR,
Ivan

-- 
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------

  reply	other threads:[~2007-10-19 10:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  8:21 [Buildroot] [buildroot 0001543]: gcc 4.1.2 libmudflap fails to build due to missing execinfo.h bugs at busybox.net
2007-10-19 10:31 ` Kuten Ivan [this message]
2007-10-19  8:36   ` Ulf Samuelsson
2007-10-19  8:47     ` Hamish Moffatt
2007-10-19  8:37   ` Hamish Moffatt
  -- strict thread matches above, loose matches on Subject: below --
2007-10-20 18:15 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=47188770.1070704@promwad.com \
    --to=ivan.kuten@promwad.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