All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: cmake build failure
Date: Fri, 04 Mar 2011 07:03:40 -0500	[thread overview]
Message-ID: <4D70D51C.5000608@balister.org> (raw)

I tried building cmake (not cmake-native) last night and it failed 
because it couldn't find LibArchive. This used to work. The build 
failure was confirmed in #oe.

In the future, please do not add a recipe and delete the old one in the 
same commit. It makes it much harder for people to diagnose problems 
since I need to mess around to get the old and new recipes in my tree at 
the same time. I'd really prefer not to see people delete recipes as 
soon as they add new ones, especially for cases like this when most 
people use the native version, and not the one for the target.

Sorry I can't paste the log right now, getting ready to board a plane 
for vacation :)

Philip



             reply	other threads:[~2011-03-04 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 12:03 Philip Balister [this message]
2011-03-09 21:15 ` cmake build failure Otavio Salvador
  -- strict thread matches above, loose matches on Subject: below --
2011-10-11 15:13 Cmake " Philip Balister
2011-10-11 15:23 ` Koen Kooi

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=4D70D51C.5000608@balister.org \
    --to=philip@balister.org \
    --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.