Package Details: dtc-git 1.4.1.r54.g1ed45d4-1

Git Clone URL: (read-only, click to copy)
Package Base: dtc-git
Description: Device Tree Compiler
Upstream URL:
Licenses: GPL2
Conflicts: dtc
Provides: dtc
Replaces: dtc
Submitter: torpe23
Maintainer: anatolik
Last Packager: anatolik
Votes: 3
Popularity: 0.000000
First Submitted: 2013-02-21 13:51 (UTC)
Last Updated: 2016-09-12 20:00 (UTC)

Dependencies (1)

Required by (52)

Sources (1)

Latest Comments

1 2 Next › Last »

hak8or commented on 2017-10-06 00:33 (UTC)

This seems to be broken due to compilation errors for shadowing a global declaration.

Nachoc commented on 2017-09-02 19:56 (UTC)


swiftgeek commented on 2017-08-16 02:02 (UTC) (edited on 2017-08-16 03:30 (UTC) by swiftgeek)

Fails to build, log: at least adding SETUP_PREFIX="$pkgdir/usr" to make install will be needed

N3rdle commented on 2015-08-22 19:37 (UTC)

is the dtc-patched package no more? i had to modify this PKGBUILD in the following way to compile device tree files on my BBB: --- PKGBUILD 2015-08-22 19:35:56.970179485 +0000 +++ PKGBUILD.patched 2015-08-22 19:29:26.947460465 +0000 @@ -4,7 +4,7 @@ pkgrel=1 pkgver=1.4.1.r16.ge5e6df7 pkgdesc='Device Tree Compiler' -arch=(i686 x86_64) +arch=(armv7h i686 x86_64) license=(GPL2) makedepends=(git) conflicts=(dtc) @@ -21,6 +21,7 @@ build() { cd dtc + git pull --no-edit dt-overlays5 make }

anatolik commented on 2014-11-11 01:45 (UTC)

Is this package still makes sense? Are these patches still not in git?

anatolik commented on 2014-11-11 01:44 (UTC)

Is this package still makes sense? Are these patches still not in git?

anatolik commented on 2014-11-08 03:06 (UTC)

1) remove leading 'v' from the versio 2) add conflicts=(dtc) provides=(dtc) replaces=(dtc)

torpe23 commented on 2014-10-13 12:30 (UTC)

anatolik: the PKGBUILD now respects the VCS guidelines.

anatolik commented on 2014-10-12 19:41 (UTC)

Your package uses out-of-date VCS package format. See that represents correct dtc-git package.

torpe23 commented on 2014-10-11 10:57 (UTC)

@FredBezies: Thanks! It's fixed ;)