From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: guile-devel@gnu.org
Subject: Re: building guile natively under openenbedded fails constantly
Date: Wed, 18 Nov 2009 07:48:26 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911180747550.11313@localhost> (raw)
In-Reply-To: <alpine.LFD.2.00.0911180741470.11064@localhost>
On Wed, 18 Nov 2009, Robert P. J. Day wrote:
>
> a huge favour, if i might. i'm using openembedded to build a linux
> image for an embedded system, and the only thing between me and a
> successful build is that the "guile-native" target won't compile.
> i've tried both versions 1.8.6 and 1.8.7, and both fail identically.
here's the full log file:
http://pastebin.com/d34bbaec4
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
prev parent reply other threads:[~2009-11-18 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 12:45 building guile natively under openenbedded fails constantly Robert P. J. Day
2009-11-18 12:48 ` Robert P. J. Day [this message]
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
List information: https://www.gnu.org/software/guile/
* 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.0911180747550.11313@localhost \
--to=rpjday@crashcourse.ca \
--cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).