From: superaorta@gmail.com
To: openembedded-devel@lists.openembedded.org
Subject: Re: comedi / angstrom
Date: Tue, 15 Jun 2010 09:06:00 +0100 [thread overview]
Message-ID: <201006150906.00827.superaorta@gmail.com> (raw)
In-Reply-To: <AANLkTimDzDDrBFuMU3HmMSBPblt5bK0HmCOnDbGruvPc@mail.gmail.com>
On Tuesday 15 June 2010 08:22:22 Frans Meulenbroeks wrote:
> 2010/6/15 <superaorta@gmail.com>:
> > I would like to build comedi (www.comedi.org) for my beagle board. From
> > the instructions for comedi, "you will need to havea correctly configured
> > Linux kernel source tree".
> >
> > I have built comedi on many platforms without trouble but I'm completely
> > lost in Angstrom - I have the kernel source (2.6.29 from kernel.org) but
> > I don't
>
> If you are lost in Angstrom better mail to the angstrom mailing list :-)
>
> > know where to find the config files. I have done this on and x86 host:
> > http://www.angstrom-distribution.org/building-angstrom
> >
> > I don't fancy building comedi using bitbake because I have not the
> > slightest
>
> if you do not want to use bitbake the openembedded mailing list does
> not seem to be the proper place to ask questions, as all of oe uses
> bitbake.
>
> > idea how to adapt it to this purpose. The easiest thing seems to me is to
> > find the correctly configures kernel source and config files and install
> > them on the beagleboard then build comedi locally.
>
> bitbake virtual/kernel will build a kernel for you, you might be lucky
> copying over that kernel.
>
Any chance you could offer some useful advice, maybe tell me something helpful
or something that I don't already know? Like I said, I have a running kernel,
I just want the source tree and the config files. Comedi is slightly less
than trivial to build out of place and the easiest solution is to get the
kernel source and config files and build it in situ.
next prev parent reply other threads:[~2010-06-15 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 7:15 comedi / angstrom superaorta
2010-06-15 7:22 ` Frans Meulenbroeks
2010-06-15 8:06 ` superaorta [this message]
2010-06-15 8:17 ` Martyn Welch
2010-06-15 9:02 ` superaorta
2010-06-15 9:33 ` Martyn Welch
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=201006150906.00827.superaorta@gmail.com \
--to=superaorta@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox