From: Mikael Rosbacke <mikael@rosbacke.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: uclibc support for x86
Date: Wed, 26 Nov 2008 13:27:29 +0100 [thread overview]
Message-ID: <1227702449.6790.9.camel@akaza1> (raw)
In-Reply-To: <19c1b8a90811251552w125189b5wc43cbb595d6fc3dc@mail.gmail.com>
I did:
rm -rf tmp
bitbake console-image
with this in my local.conf:
BBFILES = "/home/mikaelr/oe/openembedded/packages/*/*.bb"
CCACHE=""
DISTRO = "angstrom-2008.1"
MACHINE = "x86"
ANGSTROM_MODE = "uclibc"
BB_NUMBER_THREADS = "3"
IMAGE_FSTYPES += "tar.bz2"
There was 1 additional issue, as reported before. I had to insert:
'#include <limits.h>' in:
tmp/work/x86-angstrom-linux-uclibc/linux-2.6.21-r12/linux-2.6.21/scripts/mod/sumversion.c
and restart the build process. This is the same for a glibc build and
should be unrelated to the uclibc change.
After the build finished, I made a bootable CF card and booted a SiS550
based system (x86 compatible). I got to the Angstrom login prompt.
With my initial test ucLibc seems to work so far.
tnx,
--- Mikael R
tis 2008-11-25 klockan 15:52 -0800 skrev Khem Raj:
> Looks sane to me. Have you tried to build a distro with this change ?
>
> Thx
>
> -Khem
>
> On Tue, Nov 25, 2008 at 7:46 AM, Mikael Rosbacke <mikael@rosbacke.org> wrote:
> > Hello!
> >
> > Seems I'm the only one crazy enough to try to run a uClibc based
> > distribution on x86. (I can see the response, What's the point?)
> >
> > Anyway, it turns out uClibc is currently lacking support for x86.
> > I've added the folder openembedded/packages/uclibc/uclibc-0.9.30/x86
> > and created the file uClibc.machine in this folder. (See attachment)
> >
> > Is there some way to get this into the git tree? Should I file a bug
> > report or could some maintainer give feedback on things to fix before
> > inclusion? I've tried to keep the config file in style with similar
> > config files for other machines.
> >
> > Thanks in advance,
> >
> >
> > --- Mikael Rosbacke
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> >
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2008-11-26 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 15:46 uclibc support for x86 Mikael Rosbacke
2008-11-25 23:52 ` Khem Raj
2008-11-26 12:27 ` Mikael Rosbacke [this message]
2008-11-26 15:20 ` Leon Woestenberg
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=1227702449.6790.9.camel@akaza1 \
--to=mikael@rosbacke.org \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.