From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: git head: build of rpm-native fails
Date: Tue, 15 Feb 2011 07:38:42 -0700 [thread overview]
Message-ID: <4D5A8FF2.2010200@mentor.com> (raw)
In-Reply-To: <AANLkTi=bPrL+J+sA6wR+BEK9GuLxbMJRohVAPie-_u_i@mail.gmail.com>
On 02/14/2011 11:48 PM, Frans Meulenbroeks wrote:
> Hi,
>
> Yesterday I tried whether I could cross compile a helloworld.rpm to
> try on a fedora-arm box, but I failed in building rpm-native.
> This issue was verified by Jay. His log:
> http://tinderbox.openembedded.net/public/logs/task/25555153.txt
>
> apparently this is the failing part is:
>
> file -C -m ./magic.mime
> ./magic.mime, 187: Warning: string extension `B' invalid
> ./magic.mime, 401: Warning: string extension `B' invalid
> ./magic.mime, 618: Warning: string extension `B' invalid
> ./magic.mime, 623: Warning: string extension `B' invalid
> ./magic.mime, 627: Warning: string extension `B' invalid
> ./magic.mime, 628: Warning: string extension `B' invalid
> ./magic.mime, 672: Warning: no need to escape `#'
> ./magic.mime, 674: Warning: no need to escape `#'
> file: could not find any magic files!
> make[4]: *** [magic.mime.mgc] Ошибка 1
> make[4]: *** Ожидание Ð·Ð°Ð²ÐµÑ€ÑˆÐµÐ½Ð¸Ñ Ð·Ð°Ð´Ð°Ð½Ð¸Ð¹..
>
> I tried the command in a devshell and there it also fails, but I have
> not really an idea what is wrong (and I don't know too much about RPM
> anyway)
> Suggestions? Fixes ?
rpm depends on having a specific version of file around and there's
probably a mis-match.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-02-15 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 6:48 git head: build of rpm-native fails Frans Meulenbroeks
2011-02-15 14:38 ` Tom Rini [this message]
2011-02-16 7:38 ` Frans Meulenbroeks
2011-02-18 19:29 ` Tom Rini
2011-02-19 2:25 ` Khem Raj
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=4D5A8FF2.2010200@mentor.com \
--to=tom_rini@mentor.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 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.