qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Christian MICHON <christian.michon@gmail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, uClibc <uclibc@uclibc.org>,
	qemu-devel@nongnu.org, detaolb-devel@lists.sourceforge.net
Subject: Re: [Detaolb-devel] [Qemu-devel] ANN: DetaolB v0.4 is released
Date: Wed, 11 Jul 2007 13:33:49 -0400	[thread overview]
Message-ID: <200707111333.49852.rob@landley.net> (raw)
In-Reply-To: <46d6db660707110634g7f6d4adeqb142c0b71e8bffc@mail.gmail.com>

On Wednesday 11 July 2007 9:34:17 am Christian MICHON wrote:
> I just managed a compilation of bash-3.2 using ncurses-5.6 and
> uClibc-0.9.29 inside a qemu-system-sparc (native compilation,
> no cross compilation).
>
> "ldd ./bash" points naturally to libdl.so.0, libc.so.0, ld-uClibc.so.0
>
> ./bash
> Segmentation fault

When you get that kind of segmentation fault, see if "hello world" segfaults 
too.  (In general, when building with a new toolchain, new C library, new 
kernel, new root filesystem packaging method, or a new system in general, if 
anything goes wrong back up a few steps and make sure "hello world" works 
before trying to debug anything fancier.)

> I do not have gdb compiled yet... I'll check soon with busybox
> ash, since I recompiled uClibc with the sched_affinity patch.

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

  parent reply	other threads:[~2007-07-11 17:33 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29 23:58 [Qemu-devel] ANN: DetaolB v0.4 is released Christian MICHON
2007-06-30  7:47 ` Blue Swirl
2007-06-30 10:36   ` Johannes Schindelin
2007-06-30 10:51     ` Thiemo Seufer
2007-06-30 12:07       ` Christian MICHON
2007-06-30 17:15       ` Blue Swirl
2007-07-10 17:34         ` Rob Landley
2007-07-10 18:30           ` Blue Swirl
2007-07-10 19:42             ` Rob Landley
2007-07-11 11:17               ` Blue Swirl
2007-07-11 13:34                 ` [Detaolb-devel] " Christian MICHON
2007-07-11 14:20                   ` Christian MICHON
2007-07-11 17:33                   ` Rob Landley [this message]
2007-07-11 20:20                     ` Christian MICHON
2007-07-11 17:38                 ` Rob Landley
2007-07-11 20:26                   ` [Detaolb-devel] " Christian MICHON
2007-06-30 12:10     ` Christian MICHON
2007-07-04 18:30   ` Christian MICHON
2007-07-04 18:54     ` Blue Swirl
2007-07-04 19:45       ` Christian MICHON
2007-07-04 20:18         ` Blue Swirl
2007-07-04 20:30           ` Christian MICHON
2007-07-04 20:52             ` Blue Swirl
2007-07-04 21:04               ` Christian MICHON
2007-07-05 12:41                 ` Christian MICHON
2007-07-04 20:25         ` Andreas Färber
2007-07-04 20:32           ` Christian MICHON
2007-07-06 15:07             ` Rob Landley
2007-07-04 19:50     ` Cedric Hombourger
2007-07-04 19:54       ` Cedric Hombourger
2007-07-10 20:32         ` Bernhard Fischer
2007-07-10 20:36           ` Christian MICHON
2007-07-04 20:11       ` Christian MICHON
2007-07-05 19:23         ` Rob Landley
2007-07-05 20:28           ` Christian MICHON

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=200707111333.49852.rob@landley.net \
    --to=rob@landley.net \
    --cc=blauwirbel@gmail.com \
    --cc=christian.michon@gmail.com \
    --cc=detaolb-devel@lists.sourceforge.net \
    --cc=qemu-devel@nongnu.org \
    --cc=uclibc@uclibc.org \
    /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;
as well as URLs for NNTP newsgroup(s).