Package Details: distccd-alarm-armv7h

Git Clone URL: (read-only, click to copy)
Package Base: distccd-alarm
Description: Official toolchain for Arch ARM builds via distcc on x86_64 volunteers
Upstream URL:
Licenses: GPL
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 33
Popularity: 0.001709
First Submitted: 2017-09-14 21:47 (UTC)
Last Updated: 2022-05-05 18:20 (UTC)

Latest Comments

graysky commented on 2020-08-24 20:22 (UTC)

Just run makepkg -s and then run pacman -U ...armv7h.pkg.tar.zst and you're done.

dkaea353 commented on 2020-08-24 17:54 (UTC)

Could you please make it so that it is easier to pick which architectures to install? For example, I only want armv7h installed and have to comment several lines in the PKGBUILD so the other archs aren't installed too. (Or is there some easier way of doing this that I'm missing?)

graysky commented on 2020-08-23 23:09 (UTC)

@dviktor - looks like upstream pushed 10.2.0 but they do not use versioned dirs so that is why the checksums are off. I will bump, thanks for the heads-up.

dviktor commented on 2020-08-23 22:50 (UTC)

it complains about incorrect checksums. can you please recheck?

dviktor commented on 2020-08-23 22:50 (UTC)

it complains about incorrect checksums. can you please recheck?

graysky commented on 2020-08-21 09:04 (UTC)

@hotaru - Thank you, fixed in

hotaru commented on 2020-08-21 00:56 (UTC)

error: failed to commit transaction (conflicting files)
/usr/lib/sysusers.d/distccd.conf exists in both 'distccd-alarm-armv7h' and 'distccd-alarm-armv8'
/usr/lib/sysusers.d/distccd.conf exists in both 'distccd-alarm-armv7h' and 'distccd-alarm-armv5'
/usr/lib/sysusers.d/distccd.conf exists in both 'distccd-alarm-armv7h' and 'distccd-alarm-armv6h'
/usr/lib/sysusers.d/distccd.conf exists in both 'distccd-alarm-armv8' and 'distccd-alarm-armv5'
/usr/lib/sysusers.d/distccd.conf exists in both 'distccd-alarm-armv8' and 'distccd-alarm-armv6h'
/usr/lib/sysusers.d/distccd.conf exists in both 'distccd-alarm-armv5' and 'distccd-alarm-armv6h'

petronny commented on 2019-08-29 08:19 (UTC)

    # make readme.install
    sed -e "s/@VERS@/${_subarchs[$i]}/g" \
      -e "s/@PORT@/${_port[$i]}/g" \
      < >../"${_subarchs[$i]}".install

won't work in a chroot build. Please change the last line to

      < >${startdir}/"${_subarchs[$i]}".install

kprkpr commented on 2019-08-22 07:49 (UTC)

This package is superseeded with distccd-alarm-armv7h

It install some more things, but important are in /opt/* Thanks

Svenstaro commented on 2019-08-18 23:51 (UTC)

I flagged this out of date for 8.2.1 but you should probably actually use which is really 8.3.0 (though it's unversioned?). This gets rid of a problem I had with glibc 2.29.

kprkpr commented on 2019-08-01 06:55 (UTC)

For me md5 checksum is working.. Please try again

fmorgner commented on 2019-07-22 08:23 (UTC)

There is an issue with the md5 checksums for 'x-tools6h.tar.xz'. Please update them.

Flat commented on 2019-07-05 00:24 (UTC)

8.3.0-1 works fine. Thank you.

graysky commented on 2019-07-04 20:49 (UTC)

Please try 8.3.0-1

Flat commented on 2019-07-04 20:24 (UTC)

Looks like the x-tools archives have changed and the md5sums do not currently match.

graysky commented on 2018-10-25 19:41 (UTC)

@muesli4 - What are you talking about wrt uncommenting? Are you building with makepkg or with an AUR helper?

muesli4 commented on 2018-10-25 08:29 (UTC)

Doesn't work at all. First I had to uncomment the BUILDDIR variable, otherwise it wouldn't find files.

Then makepkg finished building the package with error messages that files are missing (but apparently still succesful).

When I tried building with it I get something like this in the log:

distccd[25549] (dcc_execvp) ERROR: failed to exec armv7l-unknown-linux-gnueabihf-g++: No such file or directory

kprkpr commented on 2018-09-02 10:26 (UTC)

+petronny Thanks for pointing me, and sorry for delay

Updated to 8.2.0 and now in /opt :)

graysky commented on 2018-08-28 20:34 (UTC)

@petronny - That change won't do anything as just creates a user message. The script you referenced is for building x86_64 on x86_64. This toolchain is for using x86_64 as a slave machine for an armxxx master.

I have no idea what you're wanting to achieve with your other post. I recommend against using AUR helpers in general.

petronny commented on 2018-08-28 10:32 (UTC)

Hi thanks for providing these packages.
8.2.0 is out, please upgrade them.

And how about placing the files into /opt rather than /usr ?

petronny commented on 2018-08-28 10:04 (UTC) (edited on 2018-08-28 10:07 (UTC) by petronny)

Thanks for providing these packages.
Could you help me solve a problem I get when I'm trying to build a armv7h version of unzip?
I list steps to re-produce my problem as follow:

  1. yaourt -Syua
    sudo reboot
  2. Build distccd-alarm-armv7h with extra-x86_84-build and install it with pacman -U
    sudo systemctl start distccd-armv7h
  3. Copy the original /etc/makepkg.conf to ~/makepkg-armv7h.conf.
    Change CARCH to armv7h.
    Remove -march=x86-64 -mtune=generic from CFLAGS and CXXFLAGS.
    Change !distcc to armv7h in BUILDENV.
    Set DISTCC_HOSTS to localhost:3635.
  4. yaourt -G unzip
    cd unzip
    Add armv7h to arch in PKGBUILD.
  5. makepkg --config ~/makepkg-armv7h.conf -Cf

I'm sure that distcc is working and everything are built with the arm gcc.
It will produce different outputs than the native gcc.

The problem is

cc -o unzip  -Lbzip2 unzip.o crc32.o  crypt.o envargs.o explode.o extract.o fileio.o globals.o inflate.o list.o match.o process.o ttyio.o ubz2err.o unreduce.o unshrink.o zipinfo.o unix.o -lbz2 -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now
/usr/bin/ld: unzip.o: relocations in generic ELF (EM: 40)
/usr/bin/ld: unzip.o: relocations in generic ELF (EM: 40)
/usr/bin/ld: unzip.o: relocations in generic ELF (EM: 40)
/usr/bin/ld: unzip.o: error adding symbols: file in wrong format
collect2: Error:ld returned 1
distcc[5349] ERROR: compile (null) on localhost failed

It's still using the native ld rather than the arm one.
I can't figure out why this happens. Please help.

petronny commented on 2018-08-28 09:08 (UTC)

Please change

< >../"${_subarchs[$i]}".install

to < > ${startdir}/"${_subarchs[$i]}".install.

This will make the package working with the official packaging tool extra-x86_84-build.

pa314159 commented on 2018-06-04 23:08 (UTC) (edited on 2018-06-04 23:09 (UTC) by pa314159)

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 (UTC)

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 (UTC)

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

sehraf commented on 2018-05-25 19:11 (UTC)

@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 (UTC)

@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 (UTC)

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 )

kprkpr commented on 2018-05-14 14:42 (UTC)

+mickael9 The link works again, but I will update with versioned one, that seems better option now

mickael9 commented on 2018-05-09 18:17 (UTC)

The download links are dead, they seem to be versioned now:

graysky commented on 2017-12-12 08:13 (UTC)

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

rcf commented on 2017-12-12 04:01 (UTC) (edited on 2017-12-12 04:01 (UTC) by rcf)

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

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

graysky commented on 2017-11-09 23:42 (UTC) (edited on 2017-11-09 23:45 (UTC) by graysky)

@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 (UTC)

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

graysky commented on 2017-09-17 14:22 (UTC) (edited on 2017-09-17 14:23 (UTC) by graysky)

@WarheadsSE - Fixed the spelling typo. I didn't push a PR to you for a few reasons: 1) You write out to /usr/local which violates the packaging standards[1]. 2) Your configs contain specific variables not unique to all systems/LANS (ie --allow and --port lines for each subarch). 3) My improvised method to keep book on the toolchain version might offend a real developer. 4) I assumed (perhaps incorrectly) that the changes in 1 and 2 were part of the Arch ARM build system or something similar so you would just reject the PR. I am happy to send one though if you wish. 1.

WarheadsSE commented on 2017-09-17 14:11 (UTC)

Silly question: why not MR these changes to my original repo? Also, the English word is `Contributor`

graysky commented on 2017-09-15 20:02 (UTC) (edited on 2017-09-15 20:15 (UTC) by graysky)

Thanks for the feedback, all. I got the md5sum issue sorted... upstream simply did not create a corresponding directory for the 7.2.0-1 release it seems. From now on, I will record the date stamp in the tarball to avoid confusion. Please try this release.

lonaowna commented on 2017-09-15 12:49 (UTC)

Upstream link is broken, should be

gyscos commented on 2017-09-15 02:55 (UTC)

I confirm the md5s are incorrect. Current PKGBUILD downloads file from this link: The files there have these md5s: 1e289a79b68c6f1d4403ca767b426f5f x-tools-7.1.1-2.tar.xz c4619cc2542a6bf0df5005fcb2334af7 x-tools6h-7.1.1-2.tar.xz 930e6469480395e028b4eb4000659fde x-tools7h-7.1.1-2.tar.xz d1a7cb480f1090ce6a5a370cd5cec4cd x-tools8-7.1.1-2.tar.xz

graysky commented on 2017-09-14 23:48 (UTC) (edited on 2017-09-14 23:51 (UTC) by graysky)

Must be something on your end. The md5sums match those on their wiki[1]: ARMv5te soft (1ade1ced844961a39e1e539fb04c1d65) ARMv6l hard (bfe68188dae1512690d9981ff0ee7460) ARMv7l hard (2ae08024566bd62249d4a83ee8d90124) ARMv8 (79c3880c29bc8994d2136af553ca4d6d) 1. EDIT: I will say that download speeds now are horrible with some time outs. Recommend you delete the source tarballs and try again later.

commented on 2017-09-14 23:18 (UTC)

I'm getting checksum errors on all of the x-tools*xz files.

kprkpr commented on 2016-07-13 16:07 (UTC)

Thanks XorA, fixed :)

XorA commented on 2016-07-13 15:49 (UTC)

Simple typo breaks this - tar -Jxf "$srcdir/x-tools7h.tar.xz" -C "$pkgdir/usr/x-tools" + tar -Jxf "$srcdir/x-tools8.tar.xz" -C "$pkgdir/usr/x-tools"