Package Details: splashy-full c2c9cc2-1

Git Clone URL: https://aur.archlinux.org/splashy-full.git (read-only)
Package Base: splashy-full
Description: A boot splashing system
Upstream URL: http://anonscm.debian.org/gitweb/?p=splashy/splashy;a=summary
Licenses: GPL
Provides: splashy
Submitter: None
Maintainer: jorge_barroso
Last Packager: jorge_barroso
Votes: 115
Popularity: 0.000043
First Submitted: 2009-07-03 17:05
Last Updated: 2015-06-15 19:23

Required by (0)

Sources (8)

  • automake.patch
  • configure.ac.patch
  • initcpio_hook
  • initcpio_install
  • splash-initscripts
  • splash.conf
  • splashy-functions
  • splashy

Latest Comments

arkeiro commented on 2015-04-28 21:15

I can't compile splashy-full:

...
...
...
Makefile:611: recipe for target 'xml_parser.lo' failed
make[2]: *** [xml_parser.lo] Error 1
make[2]: Leaving directory '/tmp/yaourt-tmp-jribeiro/aur-splashy-full/src/splashy/src'
Makefile:528: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/yaourt-tmp-jribeiro/aur-splashy-full/src/splashy'
Makefile:409: recipe for target 'all' failed
make: *** [all] Error 2
==> ERRO: Uma falha ocorreu em build().
A cancelar...
==> ERROR: Makepkg was unable to build splashy-full.

arkeiro commented on 2015-04-26 22:00

I get this message: ***Error***: You must have automake >= 1.9 installed
But...
$ pacman -Q |grep omake
automake 1.15-1

15.1 > 9, is true

How can I fix this?

carstene1ns commented on 2014-03-21 01:11

As said the source url is wrong. Try my uploaded PKGBUILD instead.
(Or better: do not use splashy at all, it is not systemd-ready!)

kaede commented on 2014-02-17 11:42

Same like davidrapan.

Cloning into 'splashy'...
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

carstene1ns commented on 2014-01-11 11:04

I have fixed the PKGBUILD so it compiles again, however please note that splashy requires SysV-Init and is not systemd-ready. It will likely not work!
https://gist.github.com/carstene1ns/c968774bb64ce4ac26d6

davidrapan commented on 2014-01-07 00:44

Hi guys!

Please can someone look at my error while compiling ?

Thread: https://bbs.archlinux.org/viewtopic.php?pid=1367882#p1367882

Problem:
[code]
==> Extracting sources...
==> Starting build()...
-> Cloning initial copy of splashy...
Cloning into 'splashy'...
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
==> ERROR: A failure occurred in build().
Aborting...
[/code]

ZHoob2004 commented on 2013-10-02 19:04

As a quick fix to the automake issue, I just installed automake1.10 from the aur and ran alias automake=automake1.10 before doing makepkg and it built with no issues. automake1.10 doesn't replace automake, so it could be configured as a dependency and the command changed in the PKGBUILD as a solution to this update headache.

But then it had trouble with directfb 1.7 vs 1.6 when I tried to run mkinitcpio, so I'm going to be trying to use plymouth instead since it's working fine so far.

ZHoob2004 commented on 2013-10-02 18:53

As a quick fix to the automake issue, I just installed automake1.10 from the aur and ran alias automake=automake1.10 before doing makepkg and it built with no issues. automake1.10 doesn't replace automake, so it could be configured as a dependency and the command changed in the PKGBUILD as a solution to this update headache.

denspirit commented on 2013-09-06 15:43

automake version seems to be hardcoded in autogen.sh script from sources.
automake1.10.patch was indended to fix these errors,but needs to be updated with each release of automake in repos.
I don't know how (have never written a PKGBUILD myself yet) , but maybe we can retrieve the version of automake present in system and give it to sed script,instead of patch.
ED: there is also similar stuff in initcpio_install, where we are forced to use 1.6-0 directfb version.

denspirit commented on 2013-09-06 15:04

automake version seems to be hardcoded in autogen.sh script from sources.
automake1.10.patch was indended to fix these errors,but needs to be updated with each release of automake in repos.
I don't know how (have never written a PKGBUILD myself yet) , but maybe we can retrieve the version of automake present in system and give it to sed script,instead of patch.

All comments