From: "Cedric Hombourger" <chombourger@gmail.com>
To: Christian MICHON <christian.michon@gmail.com>
Cc: uClibc <uclibc@uclibc.org>,
qemu-devel@nongnu.org, detaolb-devel@lists.sourceforge.net
Subject: Re: [Qemu-devel] ANN: DetaolB v0.4 is released
Date: Wed, 4 Jul 2007 21:50:00 +0200 [thread overview]
Message-ID: <34115e380707041250v38fe88a6v63331ecb8e3b3f98@mail.gmail.com> (raw)
In-Reply-To: <46d6db660707041130l32a896bdqd85d4d28e44605ff@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
Hi,
You may want to look at crosskit.sourceforge.net (a crosstool/buildroot-like
project that I have recently started and that you can find on sourceforge).
Following your e-mails, I have added sparc support. The toolchain builds
fine but busybox fails to link (sched_getaffinity and sched_setaffinity
undefined). If I manage to pass this issue, I will then try to build a
kernel for sparc for testing with qemu-sparc. I will also add glibc support
(crosskit aims at providing scripts for building packages against either
uclibc or glibc).
I haven't looked at detaoib yet but it was surely created before crosskit
and may therefore be a safer bet.
Regards,
Cedric Hombourger
2007/7/4, Christian MICHON <christian.michon@gmail.com>:
>
> On 6/30/07, Blue Swirl <blauwirbel@gmail.com> wrote:
> > As the number of Sparc32 distributions keeps approaching zero, could
> > you consider porting DetaolB to non-x86 CPUs?
>
> ok, I documented myself, and I'll try on sparc32.
> any hint on patches, config files for the kernel ?
>
> will uclibc work well enough on sparc32 ?
>
> --
> Christian
> --
> http://detaolb.sourceforge.net/, a linux distribution for Qemu
> _______________________________________________
> uClibc mailing list
> uClibc@uclibc.org
> http://busybox.net/cgi-bin/mailman/listinfo/uclibc
>
[-- Attachment #2: Type: text/html, Size: 1861 bytes --]
next prev parent reply other threads:[~2007-07-04 19:50 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
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 [this message]
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=34115e380707041250v38fe88a6v63331ecb8e3b3f98@mail.gmail.com \
--to=chombourger@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).