From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9711] Recent libCEC version bump seems to break kodi package
Date: Sun, 05 Mar 2017 15:22:25 +0000 [thread overview]
Message-ID: <bug-9711-163-Brmk81AgvT@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9711-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9711
--- Comment #2 from RiZom-91 <rizom91@openaliasbox.org> ---
Hum... There is something I'm missing with buildroot... Here is what I did.
1) clone the GitHub repo
2) did some minor changes and commit each change to my local repo
3) add kodi, kodi-cec packages, commit
4) make -> error with libCEC
5) revert libCEC version bump
6) make -> ok
7) did some changes in the devices_table_dev.txt
8) rm -Rf the output folder
9) make -> error with libCEC
10) revert the revert commit to get back to the original configuration (and get
the error message by the way)
11) make -> OK now
Could someone explain to me what I did wrong please ? Maybe the 'rm -Rf" part ?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-03-05 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 14:20 [Buildroot] [Bug 9711] New: Recent libCEC version bump seems to break kodi package bugzilla at busybox.net
2017-03-05 15:00 ` [Buildroot] [Bug 9711] " bugzilla at busybox.net
2017-03-05 15:22 ` bugzilla at busybox.net [this message]
2017-03-05 15:29 ` bugzilla at busybox.net
2017-03-05 15:33 ` bugzilla at busybox.net
2017-03-05 15:43 ` bugzilla at busybox.net
2017-03-05 15:51 ` bugzilla at busybox.net
2017-03-06 7:03 ` bugzilla at busybox.net
2017-03-06 8:07 ` bugzilla at busybox.net
2017-03-06 18:14 ` bugzilla at busybox.net
2017-03-06 18:49 ` bugzilla at busybox.net
2017-03-06 19:34 ` bugzilla at busybox.net
2017-03-25 13:45 ` bugzilla at busybox.net
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=bug-9711-163-Brmk81AgvT@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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