From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001417]: Busybox compiled but not working on SH3
Date: Mon, 2 Jul 2007 09:13:16 -0700 [thread overview]
Message-ID: <33b0760455d72a5e41a07bc4ce9aa949@busybox.net> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1417
======================================================================
Reported By: joshash
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1417
Category: Architecture Specific
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 07-02-2007 09:13 PDT
Last Modified: 07-02-2007 09:13 PDT
======================================================================
Summary: Busybox compiled but not working on SH3
Description:
I am using buildroot-20070615.tar.bz2 with combination of uclibc-0.9.29 ,
binutils-2.17 , busybox-1.6.0 and gcc-4.2.0.
I made the following changes :
1. During compilation, I had to change a line in
toolchain/gcc/gcc-uclibc-3.x.mk
Patch is attached. This is not the best that can be done, but it works
for me.
2. I had to add libgcc_s.so* libraries in the root file system manually.
The current situation is, the toolchain is built and I can compile and run
simple "Hello world!" like programs dynamically. But, the busybox does not
start and give any command prompt on serial console or tty0.
It gives the message like "Please press Enter to activate this console".
After pressing Enter's, same message appears again and again.
One more problem is, I can get login prompt on tty2 or so, but I cannot
login. I cannot configure the user and respective passwords coz I dont
have any command prompt to do so.
One more thing. The simple application has Flags=0x2,sh2 whereas the
busybox gets built with Flags=0x16.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
07-02-07 09:13 joshash New Issue
07-02-07 09:13 joshash Status new => assigned
07-02-07 09:13 joshash Assigned To => buildroot
07-02-07 09:13 joshash File Added: gcc-uclibc-mk.patch
======================================================================
next reply other threads:[~2007-07-02 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 16:13 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-07 18:56 [Buildroot] [buildroot 0001417]: Busybox compiled but not working on SH3 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=33b0760455d72a5e41a07bc4ce9aa949@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