Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
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 18:37:45 +1000	[thread overview]
Message-ID: <20071019083745.GA19263@cloud.net.au> (raw)
In-Reply-To: <47188770.1070704@promwad.com>

On Fri, Oct 19, 2007 at 09:31:12AM -0100, Kuten Ivan wrote:
> > 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.
> 
> 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".

Hi Ivan,

I have no idea - I did not try EABI. I wasted too much time with 4.2.1
with EABI to try it again. Maybe this patch is not required for everyone
but it was required for me.

Soft float does not compile for OABI for other reasons (see the other
bug I submitted) too so who knows.

I had 4.2.1 OABI working, but a kernel I compiled with it does not boot.
4.1.2 compiles the same kernel with a working result.

Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  parent reply	other threads:[~2007-10-19  8:37 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
2007-10-19  8:36   ` Ulf Samuelsson
2007-10-19  8:47     ` Hamish Moffatt
2007-10-19  8:37   ` Hamish Moffatt [this message]
  -- 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=20071019083745.GA19263@cloud.net.au \
    --to=hamish@cloud.net.au \
    --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