All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: cmake-native trouble making
Date: Wed, 08 Sep 2010 11:42:05 -0700	[thread overview]
Message-ID: <4C87D8FD.9050709@mentor.com> (raw)
In-Reply-To: <lytym0e69l.fsf@ensc-virt.intern.sigma-chemnitz.de>

Enrico Scholz wrote:
> Jaap de Jong <jaap.dejong@nedap.com> writes:
> 
>> $ bitbake cmake-native
>> ////
>> | [ 87%] Building CXX object
>> Source/CMakeFiles/CPackLib.dir/CPack/cmCPackNSISGenerator.o
>> | /usr/bin/ld: cannot find -ltinfo
>> | collect2: ld returned 1 exit status
>> | make[2]: *** [bin/ccmake] Error 1
>> | make[1]: *** [Source/CMakeFiles/ccmake.dir/all] Error 2
>> | make[1]: *** Waiting for unfinished jobs....
>> ////
>>
>> Is cmake-native_2.8.2.bb missing this line:
>>
>>     RDEPENDS = "ncurses-terminfo"
> 
> no, 'DEPENDS = "ncurses-native"'; BUT:
> 
> * it will cause problems on (host)distributions which do not have libtinfo
>   (e.g. RHEL5) and have ncurses-native in their ASSUME_PROVIDED

Isn't the whole point of ASSUME_PROVIDED that user be aware?

> 
> * some hours ago I added a libtermcap.so compatibility symlink to
>   ncurses(-native) so that 5ea3047995421d99f7f3537cb8f9ae23f3185a9f
>   might not be needed anymore

Um, is there a reason this wasn't just done as a ln within the recipe?

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2010-09-08 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08  8:07 cmake-native trouble making Jaap de Jong
2010-09-08 13:04 ` Enrico Scholz
2010-09-08 18:42   ` Tom Rini [this message]
2010-09-08 20:03     ` Enrico Scholz
2010-09-08 20:20       ` Tom Rini

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=4C87D8FD.9050709@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.