| Git Clone URL: | https://aur.archlinux.org/radium.git (read-only, click to copy) |
|---|---|
| Package Base: | radium |
| Description: | A graphical music editor. A next generation tracker. |
| Upstream URL: | https://users.notam02.no/~kjetism/radium |
| Licenses: | GPL2 |
| Groups: | pro-audio |
| Submitter: | speps |
| Maintainer: | yustin (Carotino) |
| Last Packager: | yustin |
| Votes: | 19 |
| Popularity: | 0.000193 |
| First Submitted: | 2013-05-22 03:41 (UTC) |
| Last Updated: | 2024-03-18 12:29 (UTC) |
@sylsau
I had an error concerning faust which was not installed on my system, so I installed it.
faust should have been build during the compile? Radium includes patched faust so I would not recommend having another faust binary in your path.
Try the new PKGBUILD for 5.9.48 version I just pushed. It includes a needed build-fix. I'd recommend building in a clean chroot to rule out your environment interfering.
It failed to build on my part.
I used @Teteros curl command to get proper llvm binairies.
First, I had an error concerning faust which was not installed on my system, so I installed it.
Then I got this: https://pastebin.com/1jsMxSP7
I've tried to remedy the error, but to no avail.
For your convenience (llvm can take really long to build), I have binaries for the LLVM version required for this package on gist.~~
Quick way to get this dependency before installing radium:
curl -OL https://gist.github.com/Teteros/f6560b1a6d0deb835e3f40c2f5e8ee58/archive/master.tar.gz && tar xvzf master.tar.gz && sudo pacman -U *-master/llvm40-*.tar.xz
If your pacman.conf requires all packages to be signed, you can add my key for this package to your keyrings with:
curl -sS https://github.com/Teteros.gpg | gpg --import # for .gnupg keyring
curl -sS https://github.com/Teteros.gpg | sudo pacman-key --add - # for pacman keyring
sudo pacman-key --lsign-key teteros # to trust key in pacman store
I'm also getting those. I also recently got a notification about someone adopting a package submitted and still maintained entirely by myself. Probably gonna report it as a bug soon, but not today since it's already very late.
While I'm at it, it's true that I've been kinda busy and it's been tricky enough for me to keep track of my own packages. It's getting better though, so I hope I can also start looking after radium again soon. Thanks to Teteros for joining the effort and keeping the package maintained in the last few weeks!
Hm, did you also receive several "package disowned" notifications for this recently? Some kinda bug or what?
Hello,
I finally managed to compile the package (probably thanks to the new update)
But now it crashes when I try to run it
Following my intuition (idk why) I tried to run it in root and it kinda works
I tried comparing the logs (god why ?) and nothing really caught my attention excepted the sample rate warning so I changed it and it still not run.
I also tried changing the rights, by changing owner, then directly chmod 777, still crashing.
So now I have no idea what to try next so if any of you have an idea for me I'd be glad reading it, meanwhile I'm going to keep searching.
Btw is there a way that the scanning / testing that happens at start crashes on some plugin stuff (vst/ladspa etc..)
Log for giggles: https://pastebin.com/HkBPBbGw
Some day I'll manage to run this software (one way or another)
@aropupu You're not alone on that one, I've heard from another user also having the same problem.
Unfortunately I could not reproduce this even on a clean chroot build.
s7.tar.gz in the build should extract during ./build_linux.sh step (Makefile.Qt):
bin/packages/s7/s7.c: bin/packages/s7.tar.gz
cd bin/packages && rm -fr s7 && tar xvzf s7.tar.gz && touch s7/s7.c
Inspecting my build log (makepkg -L) reveals s7.tar.gz was indeed extracted:
$ grep "s7.tar.gz\|^s7/" radium-5.8.2-1-x86_64-build.log
cd bin/packages && rm -fr s7 && tar xvzf s7.tar.gz && touch s7/s7.c
s7/
s7/profile.scm
s7/old-number-tests.scm
s7/write.scm
s7/s7.html
[...]
You can add this to your PKGBUILD before msg2 "Building radium" line:
msg2 "Extracting s7.tar.gz"
tar xvzf bin/packages/s7.tar.gz -C bin/packages
Okay, so after toiling around a bit: Although the package does contain the required s7 scheme interpreter files as bin/packages/s7.tar.gz, this archive never gets extracted in the build process. Manually unpacking the archive to the directory it's at solved the problem and the whole thing now compiles.
So, should this package compile now or not? my build fails with:
embedded_scheme/scheme.cpp:21:10: fatal error: s7.h: No such file or directory
#include "s7.h"
^~~~~~
compilation terminated.
make: *** [Makefile:2330: scheme.o] Error 1
Great! You should have push access now.
Pinned Comments