Package Details: xampp 7.4.11-1

Git Clone URL: (read-only, click to copy)
Package Base: xampp
Description: A stand-alone LAMPP distribution
Upstream URL:
Keywords: FTP HTML HTTP internet LAMPP MySQL PHP server web webserver
Licenses: GPL
Submitter: grufo
Maintainer: grufo (oguzkagan)
Last Packager: grufo
Votes: 20
Popularity: 0.57
First Submitted: 2017-03-26 15:47
Last Updated: 2020-10-16 15:07

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

grufo commented on 2019-11-14 13:36


It is a good practice to ask the package maintainer before filling an orphan request and take over. And it is a good practice to acknowledge people who have created and maintained the package for a long time.

This was the header of the PKGBUILD before you replaced it with only your name:

# Maintainer: grufo <madmurphy333 AT gmail DOT com>
# Contributor: Marcin (CTRL) Wieczorek <>
# Contributor: Julio González <juliolokoo at gmail dot com>
# Contributor: Jose Valecillos <valecillosjg (at) gmail (dot) com>
# Contributor: Thiago Perrotta <echo dGhpYWdvcGVycm90dGE5NUBnbWFpbC5jb20K | base64 -d >
# Contributor: alegotta <algottardi at disroot dot org>


Kalinda commented on 2019-11-13 18:11

@oguzkagan Thanks for the update, I shall follow your progress. If I find I can help I'll let you know, I'm still learning though.

oguzkagan commented on 2019-11-13 08:21

@Kalinda I am working on it. I changed proot to bitrock script. I have a trouble with link files. When I free time, I fix it. When I success, update the package. You can see changes at

Kalinda commented on 2019-11-13 01:35


I'm having the same problems as others here are - xampp won't build because proof always crashes. I want to add this package to my repo, so I spent some time digging into this further.

I understand (I think?) proot is used here to bind the /opt/lampp to the xampp package source dir in order to trick the .run file into "installing" inside that dir so all its files/folders can be taken and made into an Arch package.

I ran the proot bind command ahead of time and then tried to run the installer inside the proot environment, but it always errors and says it can't create the /opt/lampp folder. I am not sure why this is, but I get the error regardless of whether or not I perform the binding.

Is there any reason why this might be happening? Something to do with my setup, maybe, some settings I need to change? I'll keep poking around but any help would be greatly appreciated.


siddheshnan commented on 2019-08-11 03:56

==> Extracting package (this might take several minutes, don't give up!)... proot info: pid 19813: terminated with signal 11 ==> ERROR: A failure occurred in package(). Aborting... Error making: xampp

ezekielnin commented on 2019-05-20 22:57

Just for information and for people who want a working xampp (but without using aur) here a working procedure until we have a fix on the pkgbuild :

unknowed commented on 2019-04-13 14:06

==> Creating a temporary mysql user/group with fakeadd... ==> Extracting package (this might take several minutes, don't give up!)...

after 1 hours noting !!!

grufo commented on 2019-04-05 01:50


It's strange. In the current PKGBUILD, inside the prepare() function, there is a line,

# Against proot error `proot info: pid XXXX: terminated with signal 11`

which does exactly that. Doing

proot -0 -b "${pkgdir}/opt/lampp:/opt/lampp" etc....

should be exactly the same as doing

PROOT_NO_SECCOMP=1 proot -0 -b "${pkgdir}/opt/lampp:/opt/lampp" etc....

as you suggest. However this package is in need of a fix. Right now nobody can install XAMPP from a PKGBUILD.

pdizzle commented on 2019-04-04 21:31

I was getting an sha1sum fail on proot install ( and some directory issues. this PKGBUILD resolved:

changes lines 4,16,20

Also, terminate with signal 11 from proot during build. Changing line 80 of the xampp PKGBUILD from

proot -0 -b "${pkgdir}/opt/lampp:/opt/lampp" "${srcdir}/${pkgname}-linux-x64-${pkgver}" \


PROOT_NO_SECCOMP=1 proot -0 -b "${pkgdir}/opt/lampp:/opt/lampp" "${srcdir}/${pkgname}-linux-x64-${pkgver}" \

fixed the issue for me.

I still get the hanging forever as others have described, though.

chuber commented on 2019-04-02 14:03

Hey, is there a solution for the infinite "Extracting package (this might take several minutes, don't give up!)..." problem?

  • Christian