Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Illegal instruction Built bcc
Date: Thu, 16 Feb 2012 21:49:05 +0100	[thread overview]
Message-ID: <201202162149.06340.arnout@mind.be> (raw)
In-Reply-To: <4F3CDE48.2030605@labri.fr>

On Thursday 16 February 2012 11:45:28 Jigar SOLANKI wrote:
> But, when I try to compile it with a cross compiler that I have built
> using the bcc sources, it fails with the illegal instruction trap.
> 
> Here is the output of both -v :

 Oh, so you're trying to build a compiler for a bare (non-Linux) system...
Can't really help with that, I'm afraid...  Why are you asking this on
the buildroot mailing list?

 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120216/f4749ffe/attachment.html>

      reply	other threads:[~2012-02-16 20:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15 18:26 [Buildroot] Illegal instruction Built bcc Jigar SOLANKI
2012-02-15 20:55 ` Arnout Vandecappelle
2012-02-16 10:45   ` Jigar SOLANKI
2012-02-16 20:49     ` Arnout Vandecappelle [this message]

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=201202162149.06340.arnout@mind.be \
    --to=arnout@mind.be \
    --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