Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Tslib patch problem
Date: Fri, 4 Aug 2017 16:40:14 +0200	[thread overview]
Message-ID: <20170804164014.0bb15e3b@windsurf.lan> (raw)
In-Reply-To: <598438FF.7020702@wil.waw.pl>

Hello,

On Fri, 4 Aug 2017 11:06:07 +0200, Marcin Bara?ski wrote:

> buildroot for myd-sama5d3x board on ubuntu i get an error. Can you help
> me to get this work fine?
> 
> root at ubuntu:/opt/linux/Buildroot-at91/buildroot-at91# make

Where is your U-Boot coming from ? Atmel no longer has its own
Buildroot fork, they recommend to use the mainline Buildroot:

  http://www.at91.com/linux4sam/bin/view/Linux4SAM/BuildRootBuild#How_to_build_Buildroot_for_AT91

In addition, running Buildroot as root is not recommended.

> >>> tslib 412d99d Patching package//tslib  
> 
> Applying tslib_add_finddef_and_inputattach_utils.patch using patch:
> patching file tests/Makefile.am
> Hunk #1 FAILED at 12.
> Hunk #2 FAILED at 27.
> 2 out of 2 hunks FAILED -- saving rejects to file tests/Makefile.am.rej

The patch tslib_add_finddef_and_inputattach_utils.patch in
package/tslib doesn't apply. This patch doesn't exist in the official
Buildroot, so it's a problem on your side: you have added a patch that
doesn't apply.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2017-08-04 14:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5984335C.1030403@wil.waw.pl>
2017-08-04  9:06 ` [Buildroot] Tslib patch problem Marcin Barański
2017-08-04 14:40   ` Thomas Petazzoni [this message]

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=20170804164014.0bb15e3b@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --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