Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] WiringPi - problem adding package to my buildroot
Date: Wed, 25 Nov 2015 17:54:25 +0100	[thread overview]
Message-ID: <20151125175425.7bab60cc@gmx.net> (raw)
In-Reply-To: <CACvocV5KQjCEcXXx9h8pLcJpZ6QvbMBooyMxL+kg4tjHxZG7bA@mail.gmail.com>

Hello,

On Wed, 25 Nov 2015 16:30:09 +0100, "astrolite ." <ciclonite@gmail.com> wrote:

> Hi Peter,
> 
> 
> but build failed with
> >         config.status: error: cannot find input file: `Makefile.in'
> >
> > in the base directory, maybe a autoreconf/configure/make in the
> > subdirectory wiringPi works?
> 
> 
> Sorry but i cannot find where is the problem.
> There a version of wiringPi that i integrate directly on buildroot-2015-5?
> 
> Thanks and sorry for disturb.

Try this patch [1] against buildroot, adding wiringPi support to buildroot
using the original wiringPi source from git://git.drogon.net/wiringPi
(did not test it against buildroot-2015-5, but worked for me with current git
master: gpio command runs on rpi hardaware)...

Regards,
Peter

[1] https://patchwork.ozlabs.org/patch/548287/

  reply	other threads:[~2015-11-25 16:54 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 [this message]
2015-11-24 19:45 ` Peter Seiderer
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=20151125175425.7bab60cc@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