From: Marc Gauthier <marc@tensilica.com>
To: buildroot@busybox.net
Subject: [Buildroot] my /etc/init.d/rcS won't run
Date: Fri, 1 Aug 2008 08:55:32 -0700 [thread overview]
Message-ID: <KAEOLFIOAJBBAFKHIDEACEBPEMAA.marc@tensilica.com> (raw)
In-Reply-To: <bbbeeccd0808010727i23184f1ey54d7dd38376d6716@mail.gmail.com>
We've also seen this in other architectures (Xtensa).
Turned out bash turns off a whole bunch of features when cross-compiled,
not sure why. Someone worked around it by fiddling with the bash
configure script, IIRC. But we haven't yet come up with a patch to
package/bash/bash.mk to fix it. If you can do that, that would be great!
(Or, talk to bash maintainers and fix the configure script itself.)
Don't know if that's the same problem you're seeing here. We haven't
sync'ed with the main buildroot tree in a few months. So I could be
way off here...
-Marc
Wade Berrier wrote:
> I'm also running into this.
>
> I've found out so far that bash is segfaulting when getting run from init.
>
> Attached is an strace of this happening.
>
> Wade
>
> On Fri, Aug 1, 2008 at 7:12 AM, John Voltz <john.voltz@gmail.com> wrote:
> >>
> >> What I found was that including bash, caused /bin/sh to point to bash
> >> and for dome reason bash does not want to run that early. Currently
> >> I've dropped bash.
> >
> > Try adding init=/bin/bash to your kernel parameters in your
> bootloader. This
> > will boot you directly into a bash shell without running init,
> so you can
> > see if something's wrong with bash.
> >
> > John
next prev parent reply other threads:[~2008-08-01 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 22:36 [Buildroot] my /etc/init.d/rcS won't run Brian Beattie
2008-08-01 7:24 ` Hinko Kocevar
2008-08-01 12:47 ` Brian Beattie
2008-08-01 13:12 ` John Voltz
2008-08-01 14:27 ` Wade Berrier
2008-08-01 15:55 ` Marc Gauthier [this message]
2008-08-04 16:31 ` Wade Berrier
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=KAEOLFIOAJBBAFKHIDEACEBPEMAA.marc@tensilica.com \
--to=marc@tensilica.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