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 0002694]: busybox generates illegal instruction error on ARM platform
Date: Wed, 26 Mar 2008 17:07:02 -0700	[thread overview]
Message-ID: <a7b7533c001839146cf389c646b86c02@busybox.net> (raw)


A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=2694 
====================================================================== 
Reported By:                ychuang
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   2694
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             03-26-2008 04:30 PDT
Last Modified:              03-26-2008 17:07 PDT
====================================================================== 
Summary:                    busybox generates illegal instruction error on ARM
platform
Description: 
After applying current new patchs (using svn) for buildroot, busybox
commands: insmod, rmmod, and ping generate illegal instruction error after
rebuilding the whole toolchain and recompiling busybox 1.9 (or 1.10).

busybox 1.9.0 was working with old toolchain back on 2007/11/02.
====================================================================== 

---------------------------------------------------------------------- 
 hbr_in - 03-26-08 17:07  
---------------------------------------------------------------------- 
Hi,

I also had the same issue with busybox and buildroot. Then i updated my
buildroot and busybox config and its working fine now. I have tested it
against Busybox-1.9.1 version. Attached is the buildroot and busybox
config files.
Let me know if this has helped you any way.

Regards
Gururaja 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-26-08 04:30  ychuang        New Issue                                    
03-26-08 04:30  ychuang        Status                   new => assigned     
03-26-08 04:30  ychuang        Assigned To               => buildroot       
03-26-08 04:30  ychuang        File Added: .config                          
03-26-08 17:00  hbr_in         File Added: myboard_defconfig                    
03-26-08 17:00  hbr_in         File Added: busybox-1.9.1-full_opti.config       
            
03-26-08 17:07  hbr_in         Note Added: 0006094                          
======================================================================

             reply	other threads:[~2008-03-27  0:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27  0:07 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-28  7:59 [Buildroot] [buildroot 0002694]: busybox generates illegal instruction error on ARM platform bugs at busybox.net
2008-03-26 11:30 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=a7b7533c001839146cf389c646b86c02@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