Package Details: radium 7.4.76-1

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.000002
First Submitted: 2013-05-22 03:41 (UTC)
Last Updated: 2024-06-07 06:47 (UTC)

Dependencies (50)

Required by (0)

Sources (3)

Pinned Comments

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 Next › Last »

Teteros commented on 2017-08-02 03:39 (UTC)

@j5lx Hello again, issues for this to compile on latest git have been resolved. You may upgrade the package when 4.9.13 is released. The required patches are on my gist: https://gist.github.com/Teteros/d1261ce765e383c0d0f6f25f026c93b4 Changes: 1) (Pull Req Merged, in master) LLVM 4.0.1 fix. https://github.com/kmatheussen/radium/commit/e5e80ca014bf44a75c7d30e5ce2f8b4971b5ad39 2) (Fixed, in master) Invalid Makefile target. https://github.com/kmatheussen/radium/issues/1054#issuecomment-319491630 3) (New patch, use-new-cxx11-abi.patch) See above issue. I believe for compatibility with new gcc versions Kjetil has explicitly set D_GLIBCXX_USE_CXX11_ABI=0 in CXXFLAGS which makes gcc use the old CXX ABI. However this causes the faust package to not compile for us because LLVM in Arch repos has been build with the new ABI as per default in GCC5+. I've set the existing flags =0 in this patch, but more may be need to be set in later builds. 4) (Updated, use-system-libxcb.patch and use-system-vstsdk.patch) Patches were rejected due to file changes in upstream. PKGBUILD Suggestion: Kjetil looked through our patches (!) and suggested the empty lib paths patch shouldn't be emptied like done in dont-empty-qt-library-paths.patch as the "else" clause becomes commented out. I suggest we instead go with the wrapper approach like done in radium's binary release. One way... Remove the empty-qt-library-paths.patch and unsource/remove patch in PKGBUILD Include my radium.sh from gist Change the install command in the PKGBUILD to install -Dm755 "${srcdir}/radium.sh" "${pkgdir}/usr/bin/radium" This will remove the need for that patch and will run radium with arguments using the radium lib in /opt and system qt5-plugins.

J5lx commented on 2017-07-15 17:22 (UTC)

IIRC faust is quite picky about the LLVM version, so it will only accept 4.0.0 but not 4.0.1, we used to adjust those checks ourselves every time LLVM got an update before Teteros contributed that patch to upstream (see https://aur.archlinux.org/cgit/aur.git/tree/faust-accept-current-clang.patch?h=radium&id=bbab74e41fc917c71131a26da54a3423e3a3add4). I’ll try to update the package soon™, but until then you should be able to work around that issue by compiling radium with llvm 4.0.0 which you can obtain from https://archive.archlinux.org/.

actionless commented on 2017-07-14 19:22 (UTC) (edited on 2017-07-14 19:22 (UTC) by actionless)

@Teteros your patch seems to be merged already but i stil have problems compiling it with LLVM 4: make[1]: Entering directory '/home/lie/.cache/pacaur/radium/src/radium-4.8.5/bin/packages/faust2' make -C compiler -f Makefile.unix prefix=/usr/local make[2]: Entering directory '/home/lie/.cache/pacaur/radium/src/radium-4.8.5/bin/packages/faust2/compiler' Makefile.unix:121: *** "Unknown LLVM version 4.0.1". Stop.

J5lx commented on 2017-05-09 13:03 (UTC)

Yeah I use integrated graphics (Intel). I agree that it should not make a difference in theory, but if it does in fact happen I think it can be called a bug, be it in Radium, Mesa, LLVM or somewhere else entirely. It might be a good idea to consult somebody with a deeper understanding of the inner workings involved.

Teteros commented on 2017-05-09 11:53 (UTC) (edited on 2017-05-09 12:33 (UTC) by Teteros)

Do you by any chance have a non-radeon card? When I removed 4.0 libs the radeon/mesa opengl driver stopped working, but radium could start, although it printed an error that opengl is not working which is right of course. I was thinking of reporting it, but in theory only llvm39 should conflict with llvm, the libs packages are fine without the conflict array as they only provide the extra libs, rather than overriding anything. Anyway the fix is merged already (!) and in upstream 4.8.0 release, check it out when you can. EDIT: Merged in master but not in 4.8.0 yet.

J5lx commented on 2017-05-09 11:14 (UTC)

I still don’t quite get why that error occurs for you but not for me, even though I also have installed both 3.9 and 4.0, but if there is in fact some kind of incompatibility between those two versions of llvm-libs you might want to report a bug to the project (i.e. https://bugs.archlinux.org/) (I’d rather not report it myself because I can’t reproduce it and I still don’t really understand what happens). As for the patch, I don’t have the time/calm to review it properly right now so it’ll probably land in a few days or once it gets merged.

Teteros commented on 2017-05-09 03:11 (UTC)

TL;DR I patched radium's bundled faust to work with llvm 4.0, either grab the patch from here: https://gist.github.com/Teteros/61dfd60f3d2a9216231b97630c0c2401 and add this to the PKGBUILD (and source array) patch -d bin/packages/faust2 -p0 < "${srcdir}/0001-LLVM-4.0-support.patch" or wait for my pull request to be merged: https://github.com/kmatheussen/radium/pull/970 Got the time to track this down, it appears the crash happens when you have llvm-libs from repo installed, which is the 4.0 version, this occurs because llvm39-libs does not seem to conflict with it, so I ended up with llvm39 and llvm39-libs installed (which is intented) as well as llvm-libs (4.0) Of course, this should work as ldd on radium shows it correctly links to libLLVM-3.9.so lib, but for some reason it crashes for me with the 4.0 lib package installed. I ended up patching radium's faust to work with llvm 4.0 as without it, some important libs like mesa would have to be recompiled to work with llvm39.

Teteros commented on 2017-04-29 08:44 (UTC) (edited on 2017-04-29 08:45 (UTC) by Teteros)

Still occurs with your package build unfortunately. I'll snapshot my current partition, and do a fresh install to eliminate some linking or lingering cache/config from possibly interfering. Though you'd think a chrooted build would help if that was the case.

J5lx commented on 2017-04-29 08:09 (UTC)

Personally I don’t experience that at all. So weird! For now I uploaded my own build of the package at https://repo.j5lx.eu/.radium/, could you try installing it and see whether the error occurs with that build as well?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 Next › Last »