All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Philip Balister <philip@balister.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: UHD (from meta-oe) failure when rpm packaging selected
Date: Wed, 23 Jan 2013 09:47:24 -0600	[thread overview]
Message-ID: <5100060C.70501@windriver.com> (raw)
In-Reply-To: <50FFF460.5050108@balister.org>

On 1/23/13 8:32 AM, Philip Balister wrote:
> On 01/23/2013 09:18 AM, Mark Hatle wrote:
>> On 1/23/13 7:29 AM, Philip Balister wrote:
>>> The recipe builds fine with ipk only, but when you add rpm packaging the
>>> recipe fails to build with:
>>>
>>> so.5 libncurses.so.5
>>> Processing files: uhd-dbg-3.5.0-r3.0.armv7a_vfp_neon
>>> Finding  Provides:
>>> /home/balister/src/oe-core/build/tmp-eglibc/work/armv7a-vfp-neon-oe-linux-gnueabi/uhd/1_3.5.0-r3.0/uhd.provides
>>>
>>> Finding  Requires:
>>> /home/balister/src/oe-core/build/tmp-eglibc/work/armv7a-vfp-neon-oe-linux-gnueabi/uhd/1_3.5.0-r3.0/uhd.requires
>>>
>>> Processing files: uhd-dev-3.5.0-r3.0.armv7a_vfp_neon
>>> Finding  Provides:
>>> /home/balister/src/oe-core/build/tmp-eglibc/work/armv7a-vfp-neon-oe-linux-gnueabi/uhd/1_3.5.0-r3.0/uhd.provides
>>>
>>> error: line 719: Illegal char '-' in EVR:
>
> [balister@mini ~]$ wc -l
> thuvia/src/oe-core/build/tmp-eglibc/work/armv7a-vfp-neon-oe-linux-gnueabi/uhd/1_3.5.0-r3.0/uhd.spec
>
> 719
> thuvia/src/oe-core/build/tmp-eglibc/work/armv7a-vfp-neon-oe-linux-gnueabi/uhd/1_3.5.0-r3.0/uhd.spec
>
> The last line is blank.

The only other thing I can think of is that the uhd.provides or uhd.requires 
file are returning a line with an invalid character.. but it's rare that they 
return values with full version information.

Can you put the uhd.spec, uhd.provides and uhd.requires files somewhere I can 
look at them, I can probably spot the problem fairly quickly.

--Mark

> Philip
>
>>>
>>> error: Failed to find Provides:
>>>
>>>
>>> RPM build errors:
>>>       line 719: Illegal char '-' in EVR:
>>
>> The line above is from the generated spec file.  Look at
>> /home/balister/src/oe-core/build/tmp-eglibc/work/armv7a-vfp-neon-oe-linux-gnueabi/uhd/1_3.5.0-r3.0/uhd.spec
>> -- line 719 and see what it contains.
>>
>> In RPM there is a rule that the Epoch, Version and Release may not
>> contain a "-".  So a translation should have occurred to change it to
>> either a + or a _..  (I don't remember which at the moment.)
>>
>>>       Failed to find Provides:
>>> DEBUG: Python function do_package_rpm finished
>>>
>>> Any suggestions?
>>>
>>> Philip
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>>




      reply	other threads:[~2013-01-23 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 13:29 UHD (from meta-oe) failure when rpm packaging selected Philip Balister
2013-01-23 14:18 ` Mark Hatle
2013-01-23 14:32   ` Philip Balister
2013-01-23 15:47     ` Mark Hatle [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5100060C.70501@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philip@balister.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.