From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10391] New: WiringPi retrieves wrong (old) version
Date: Wed, 11 Oct 2017 11:21:43 +0000 [thread overview]
Message-ID: <bug-10391-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10391
Bug ID: 10391
Summary: WiringPi retrieves wrong (old) version
Product: buildroot
Version: 2017.08
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: srg.venema at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
WiringPi latest version is 2.44. Doing a manual git clone on
git://git.drogon.net/wiringPi does retrieve the latest 2.44 version, however
the buildroot packages retrieves 2.42, which does *NOT* work with newer
kernels.
Repeatable by doing:
[buildroot at build buildroot]$ make wiringpi-source
>>> wiringpi 2.44 Downloading
Doing shallow clone
Initialized empty Git repository in
/home/buildroot/buildroot-2017.08/output/build/.wiringpi-2.44.tar.gz.DZuokV/wiringpi-2.44/.git/
remote: Counting objects: 383, done.
remote: Compressing objects: 100% (333/333), done.
remote: Total 383 (delta 210), reused 56 (delta 16)
Receiving objects: 100% (383/383), 232.00 KiB, done.
Resolving deltas: 100% (210/210), done.
warning: Remote branch 2.44 not found in upstream origin, using HEAD instead
Could not fetch special ref '2.44'; assuming it is not special.
wiringpi-2.44.tar.gz: OK (sha256:
464c98ed54f5c0ad6611e270be3491c4598a32b7e86b208255862a301c564955)
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-10-11 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 11:21 bugzilla at busybox.net [this message]
2017-10-11 11:23 ` [Buildroot] [Bug 10391] WiringPi retrieves wrong (old) version bugzilla at busybox.net
2017-10-11 11:28 ` bugzilla at busybox.net
2017-10-11 11:29 ` bugzilla at busybox.net
2017-10-11 13:06 ` bugzilla at busybox.net
2017-10-11 13:28 ` bugzilla at busybox.net
2017-10-11 14:23 ` bugzilla at busybox.net
2017-10-11 14:44 ` bugzilla at busybox.net
2017-10-31 20:59 ` 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-10391-163@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 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.