From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] WiringPi - problem adding package to my buildroot
Date: Tue, 24 Nov 2015 20:45:46 +0100 [thread overview]
Message-ID: <20151124204546.2039bf73@gmx.net> (raw)
In-Reply-To: <CACvocV5bQo_YG05=ujYEJHygDQCw6_XZDLJ9zdCLO4tGCSswtg@mail.gmail.com>
Hello Giovanni,
On Tue, 24 Nov 2015 19:17:43 +0100, "astrolite ." <ciclonite@gmail.com> wrote:
> Hi all,
> After sucessfully added pigpio package to buildroot, i'm tried to add
> wiringPi package.
> But i've a problem that not understand..
>
> These are my files :
> Config.in
>
> config BR2_PACKAGE_WIRINGPI
> bool "wiringPi"
> help
> wiringPi libraries
>
> wiringPi.mk
>
> WIRINGPI_VERSION = 488e3729e44721b79ba655429f453f7396157c22
> WIRINGPI_INSTALL_TARGET = YES
> WIRINGPI_INSTALL_STAGING = YES
> WIRINGPI_AUTORECONF = YES
> WIRINGPI_SITE = $(call github,ciclonite,pigpio,$(LIBPIGPIO_VERSION))
Forgot to ask: Why a fork from the original sources? Whats wrong
with the original WiringPi buildsystem?
Regards,
Peter
>
>
> when i launch make :
>
> make
> /usr/bin/make -j1 HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++"
> silentoldconfig
> make[1]: Entering directory
> `/root/qt-pi2-pigpio-wiringpi/buildroot-qt-dev/buildroot-2015.05'
> BR2_DEFCONFIG=''
> KCONFIG_AUTOCONFIG=/root/qt-pi2-pigpio-wiringpi/buildroot-qt-dev/buildroot-2015.05/output/build/buildroot-config/auto.conf
> KCONFIG_AUTOHEADER=/root/qt-pi2-pigpio-wiringpi/buildroot-qt-dev/buildroot-2015.05/output/build/buildroot-config/autoconf.h
> KCONFIG_TRISTATE=/root/qt-pi2-pigpio-wiringpi/buildroot-qt-dev/buildroot-2015.05/output/build/buildroot-config/tristate.config
> BR2_CONFIG=/root/qt-pi2-pigpio-wiringpi/buildroot-qt-dev/buildroot-2015.05/.config
> BR2_EXTERNAL=support/dummy-external SKIP_LEGACY=
> /root/qt-pi2-pigpio-wiringpi/buildroot-qt-dev/buildroot-2015.05/output/build/buildroot-config/conf
> --silentoldconfig Config.in
> make[1]: Leaving directory
> `/root/qt-pi2-pigpio-wiringpi/buildroot-qt-dev/buildroot-2015.05'
> >>> host-gawk 4.1.2 Patching
>
> Applying 0001-no-versioned.patch using patch:
> patching file Makefile.in
> Reversed (or previously applied) patch detected! Skipping patch.
> 2 out of 2 hunks ignored -- saving rejects to file Makefile.in.rej
> Patch failed! Please fix 0001-no-versioned.patch!
> make: ***
> [/root/qt-pi2-pigpio-wiringpi/buildroot-qt-dev/buildroot-2015.05/output/build/host-gawk-4.1.2/.stamp_patched]
> Error 1
>
> Someone can help me to find out the problem?
> Thanks,
> Giovanni
next prev parent reply other threads:[~2015-11-24 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 18:17 [Buildroot] WiringPi - problem adding package to my buildroot astrolite .
2015-11-24 19:40 ` Peter Seiderer
2015-11-25 15:30 ` astrolite .
2015-11-25 16:54 ` Peter Seiderer
2015-11-24 19:45 ` Peter Seiderer [this message]
2015-11-25 9:47 ` astrolite .
2015-11-25 16:59 ` Peter Seiderer
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=20151124204546.2039bf73@gmx.net \
--to=ps.report@gmx.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