Package Details: distccd-alarm-armv5 8.1.0-1

Git Clone URL: (read-only)
Package Base: distccd-alarm
Description: Toolchain for Arch ARM builds via distcc on x86_64 slaves
Upstream URL:
Licenses: GPL
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 8
Popularity: 0.826017
First Submitted: 2017-09-14 21:47
Last Updated: 2018-05-12 11:26

Latest Comments

pa314159 commented on 2018-06-04 23:08

Build fails with

==> Creating package "distccd-alarm-armv5"...

-> Generating .PKGINFO file...

-> Generating .BUILDINFO file...

-> Adding install file...

cp: cannot stat '...../armv5.install': No such file or directory

==> ERROR: Failed to add install file to package.

sehraf commented on 2018-05-25 22:11

You can tell makepkg to build everything under a specific path (/tmp/makepkg/ in my case). When doing so the build process fails because if incorrect paths inside the PKGBUILD file.

graysky commented on 2018-05-25 19:28

@sehraf - Perhaps I misunderstood... I am unfamiliar building as you describe.

sehraf commented on 2018-05-25 19:11

@graysky, thx for the answer though i don't see how it is related to my question. My problem is that the path' used are wrong. (the root thing is no problem)

graysky commented on 2018-05-20 10:58

@sehraf - I can't help you with that... even building with makepkg results in a $srcdir that cannot be removed without root privileges due to settings in the upstream tarballs.

sehraf commented on 2018-05-20 10:56

The PKGBUILD is broken when using a separated build directory:

from /etc/makepkg.conf

-- Specify a directory for package building.


When building i get the following error (using yaourt or pacaur): cp: cannot stat '/tmp/yaourt-tmp-user/aur-distccd-alarm-armv7h/armv5.install': No such file or directory

This is the directory where yaourt places the PKGBUILD (/tmp/yaourt-tmp-user/aur-distccd-alarm-armv7h/PKGBUILD) (same goes for pacaur /home/user/.cache/pacaur/distccd-alarm/PKGBUILD)

But the file in question is located in /tmp/makepkg/distccd-alarm/armv5.install since this is where the build process is done.

This might also related: i get these errors: "distccd[540] (dcc_check_compiler_whitelist) CRITICAL! armv7l-unknown-linux-gnueabihf-g++ not in /usr/lib/distcc whitelist." I saw your post here and i don't have these sym links on my system (i built the package by removing the install="$1.install" entry :P )

graysky commented on 2017-12-12 08:13

@rcf - Yes, it looks like they repacked without bumping the pkgver or pkgrel :/

rcf commented on 2017-12-12 04:01

The MD5s have changed (as seen on the wiki):

md5sums=('9cfadee932063e8341c14036c5c10e90' '12ae25e2529387fe7a038c24429bad81' 'b2abddab4c216150b3be8854d6b4afd6' 'ceed447e8789f7579e7b99a394c02a82' '48b71f968488a4322a715d633eb6879e' '7e664f8ce386f467f1a7381c9ac3c06f')

graysky commented on 2017-11-09 23:42

@FallenSnow - Builds fine for me... just slow downloads from upstream. I will say that I have always experienced problems removing ./src due to some permissions within the upstream files... removing it requires root.

FallenSnow commented on 2017-11-09 17:09

I'm getting a bunch of `Can't unlink already-existing object errors`. Don't know if this is something on my side or not...

==> Extracting sources...
-> Extracting x-tools-7.2.0-1-20170910.tar.xz with bsdtar
x-tools/arm-unknown-linux-gnueabi/build.log.bz2: Can't unlink already-existing object
x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/include/c++/7.2.0/ccomplex: Can't unlink already-existing object
x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/include/c++/7.2.0/future: Can't unlink already-existing object
x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/include/c++/7.2.0/codecvt: Can't unlink already-existing object
x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/include/c++/7.2.0/ios: Can't unlink already-existing object
x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/include/c++/7.2.0/typeinfo: Can't unlink already-existing object

All comments