From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Build failure module-init-tools-cross_3.2.2.bb on Fedora 12 x86_64
Date: Sun, 24 Jan 2010 12:36:38 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001241235020.2367@localhost> (raw)
In-Reply-To: <1F9F6029-E5F8-4B85-967C-7FB2C110CFCE@mac.com>
On Sun, 24 Jan 2010, Elvis Dowson wrote:
> Hi Martin,
> Yes, just found that solution. I'm installing
> glibc-static right now.
>
> http://old.nabble.com/Error-Compiling-Gumstix-Image-On-Fedora-12-x86_64-td26776355.html#a26776355
>
> Anyway, I'm updating my setup notes for Fedora 12 x86 64-bit, so it
> will help others doing this.
once upon a time, i wrote much the same:
http://www.crashcourse.ca/wiki/index.php/Angstrom
perhaps we should exchange notes to come up with a single complete
set.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2010-01-24 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 15:29 Build failure module-init-tools-cross_3.2.2.bb on Fedora 12 x86_64 Elvis Dowson
2010-01-24 15:37 ` Elvis Dowson
2010-01-24 15:43 ` Martin Jansa
2010-01-24 15:45 ` Robert P. J. Day
2010-01-24 15:47 ` Elvis Dowson
2010-01-24 17:36 ` Robert P. J. Day [this message]
2010-01-24 18:54 ` Technote Overo-031: How to setup a development environment for the Overo platform using a Fedora-12 x86 64-bit VMware image Elvis Dowson
2010-01-24 16:46 ` Build failure module-init-tools-cross_3.2.2.bb on Fedora 12 x86_64 Robert P. J. Day
2010-01-24 18:46 ` Elvis Dowson
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=alpine.LFD.2.00.1001241235020.2367@localhost \
--to=rpjday@crashcourse.ca \
--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.