Package Details: purr-data-git 2.19.0.r5002.58e47c1fb-1

Git Clone URL: https://aur.archlinux.org/purr-data-git.git (read-only, click to copy)
Package Base: purr-data-git
Description: Jonathan Wilkes' nw.js variant of Pd-L2Ork (git version)
Upstream URL: https://git.purrdata.net/jwilkes/purr-data
Licenses: BSD
Conflicts: purr-data
Provides: purr-data
Submitter: pure-aur
Maintainer: aggraef
Last Packager: aggraef
Votes: 2
Popularity: 0.000000
First Submitted: 2016-06-22 18:29 (UTC)
Last Updated: 2024-02-05 00:23 (UTC)

Latest Comments

1 2 Next › Last »

aggraef commented on 2020-07-20 04:17 (UTC)

@milk, sorry, I missed your message. I added the missing python2 build dependency now, so your problem should be fixed now.

milkii commented on 2020-01-18 06:52 (UTC) (edited on 2020-01-18 06:52 (UTC) by milkii)

Building in a clean environment, getting this:

...
checking whether yytext is a pointer... yes
checking for bison... bison -y
checking for python2... no
configure: error: python2 not found
make[3]: *** [Makefile:471: disis] Error 1
make[3]: Leaving directory '/home/pkguser/src/purr-data/src/purr-data/externals'
make[2]: *** [Makefile:209: externals_install] Error 2
make[2]: Leaving directory '/home/pkguser/src/purr-data/src/purr-data/packages'
make[1]: *** [Makefile:61: install] Error 2
make[1]: Leving directory '/home/pkguser/src/purr-data/src/purr-data/packages/linux_make'
./tar_em_up.sh: 337: command failed with exit code 2, exiting now.
./tar_em_up.sh: 337: make install prefix=$inst_dir
make: *** [Makefile:109: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

makechrootpkg can be used to detect missing dependencies.

aggraef commented on 2018-01-03 10:19 (UTC)

@morrisar47, I think I've fixed the compilation issue that you reported now. It was apparently an incompatibility of Gem with libmagick7 causing an incomplete build. I've fixed up the PKGBUILD so that it will always link Gem against libmagick6 now.

aggraef commented on 2017-12-14 05:16 (UTC)

And, as we speak 2.4.6 has landed. :) Currently building binaries, give it some 30 mins.

aggraef commented on 2017-12-14 04:59 (UTC)

Yeah, you only need the second repo mentioned there (the Pure repo) for the dependencies required to run the Pure and Faust extensions.

morrisar47 commented on 2017-12-14 04:39 (UTC)

Thank you, that got me up and running. I was close but picked the wrong repo to start.

aggraef commented on 2017-12-14 02:41 (UTC) (edited on 2017-12-14 02:44 (UTC) by aggraef)

Also note that if you follow the link that I first posted, you can find instructions on how to add the binary repository to your pacman.conf, so that you will receive updates of this package automatically whenever a new version becomes available. (Version 2.4.6 is already in the upstream git repo and will probably be released in the next few days if not hours.)

Briefly, this is what you add to your pacman.conf:

[l2ork-aur]

SigLevel = Never

Server = https://l2orkaur.bitbucket.io/$arch

Then you run sudo pacman -Sy and you should be set.

aggraef commented on 2017-12-14 02:17 (UTC)

This is the package you're looking for: https://bitbucket.org/l2orkaur/l2orkaur.bitbucket.org/raw/HEAD/x86_64/purr-data-2.4.5.r3757.ab28aed9-1-x86_64.pkg.tar.xz

morrisar47 commented on 2017-12-14 01:55 (UTC)

Thanks for the response. I have no problem with running a prebuit binary but I've looked at the site and am unable to determine which file is the correct one to download and then I'm not sure how to install it. I assume it's a pacman command once I've downloaded it. I'd appreciate it if you be a bit more specific.

aggraef commented on 2017-12-13 18:51 (UTC)

Builds fine over here, I just ran another test build to confirm this.

This package and some of the dependencies are notoriously difficult to build, though. If you can, please use the binary package repo at https://l2orkaur.bitbucket.io/ (that's the "stable" package purr-data, but it's up-to-date, updated yesterday). I'm running that package myself, so it's guaranteed to work.

If you really need to build from source then you'll have to look at the build log and see where it goes wrong, but that's no walk in the park.

1 2 Next › Last »