From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: Build of prelink_git.bb fails
Date: Thu, 03 Feb 2011 14:43:28 +0000 [thread overview]
Message-ID: <1296744208.1544.9277.camel@rex> (raw)
In-Reply-To: <4D4ABA30.4020505@windriver.com>
On Thu, 2011-02-03 at 08:22 -0600, Mark Hatle wrote:
> Something is wrong with your host system. Nothing has changed with the prelink
> integration since late December.
>
> The failure seems to indicate a broken latex, tetex and/or tex2pdf installation.
Nothing changed in prelink but we did add some doc tools of various
kinds which might have triggered this.
Wolfgang - can you share a list of other native packages which have been
built? You can see this by looking for do_populate_sysroot* stamps in
the tmp/stamps/<native system>/ directory.
Cheers,
Richard
next prev parent reply other threads:[~2011-02-03 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 14:15 Build of prelink_git.bb fails Wolfgang Denk
2011-02-03 14:22 ` Mark Hatle
2011-02-03 14:43 ` Richard Purdie [this message]
2011-02-03 14:47 ` Wolfgang Denk
2011-02-03 14:45 ` Wolfgang Denk
2011-02-03 16:15 ` Mark Hatle
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=1296744208.1544.9277.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=mark.hatle@windriver.com \
--cc=poky@yoctoproject.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