Package Details: faust-git 2:2.5.29.r9657.69b5a04c9-1

Git Clone URL: https://aur.archlinux.org/faust-git.git (read-only)
Package Base: faust-git
Description: A functional programming language for realtime audio signal processing.
Upstream URL: http://faust.grame.fr/
Licenses: GPL
Conflicts: faust
Provides: faust, faust2-git
Submitter: smoge
Maintainer: pure-aur
Last Packager: pure-aur
Votes: 9
Popularity: 0.211469
First Submitted: 2010-12-24 20:56
Last Updated: 2018-03-27 22:38

Required by (13)

Sources (1)

Latest Comments

daniel.appelt commented on 2018-05-19 17:53

Same problem here - only GCC is newer now. It seems to be related to make target "world". If I go into the downloaded build directory and issue a simple "make", compilation works just fine.

helldrak commented on 2018-05-13 04:38

It’s been more than two weeks since my latest bug report and SpotlightKid comment. I’m still locked with the same error (latest Manjaro rolling release). Is everything OK ? If you need more information, feel free to ask for another report.

SpotlightKid commented on 2018-04-28 00:42

Same error here. I first thought this was due to using ccache, but I disabled it in /etc/makepkg.conf and then got the same error as helldrak ("/usr/bin/cc" is not able to compile a simple test program). I'm also on Manjaro.

helldrak commented on 2018-04-26 09:56

Hi everyone,

Since the latest Manjaro rolling release I can’t compile faust-git anymore – makepkg -siC outputs the following parts :

CMake Error at /usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:186 (configure_file):
  configure_file Problem configuring file
Call Stack (most recent call first):
  CMakeLists.txt:2 (project)

-- The C compiler identification is GNU 7.3.1
-- The CXX compiler identification is GNU 7.3.1
CMake Error at /usr/share/cmake-3.10/Modules/CMakeDetermineCXXCompiler.cmake:190 (configure_file):
  configure_file Problem configuring file
Call Stack (most recent call first):
  CMakeLists.txt:2 (project)

-- Check for working C compiler: /usr/bin/cc -- broken
CMake Error at /usr/share/cmake-3.10/Modules/CMakeTestCCompiler.cmake:52 (message):
  The C compiler
    "/usr/bin/cc"
  is not able to compile a simple test program.
  It fails with the following output:
    Change Dir: /home/tcip/.aurBuilds/faust-git/src/faust-git/build/faustdir/CMakeFiles/CMakeTmp
    Run Build Command:"/usr/bin/make" "cmTC_79ab7/fast"
    make[2] : on entre dans le répertoire « /home/tcip/.aurBuilds/faust-git/src/faust-git/build/faustdir/CMakeFiles/CMakeTmp »
    make[2]: *** Aucune règle pour fabriquer la cible « cmTC_79ab7/fast ». Arrêt.
    make[2] : on quitte le répertoire « /home/tcip/.aurBuilds/faust-git/src/faust-git/build/faustdir/CMakeFiles/CMakeTmp »
Call Stack (most recent call first):
  CMakeLists.txt:2 (project)

I’ve checked the CMakeOutput.log and C/CXX compilers are all marked as succeeded and produced "a.out".

Any idea of what went wrong – any dependency broken on Faust side or is it my system (although all others AUR compiles well) ?

Thanks for your tremendous work and looking forward to Faust again ! All the best,

aggraef commented on 2018-01-24 10:26

@dvzrv, the explanation there is rather terse. E.g., what does git config submodule.mysubmodule.url $srcdir/mysubmodule do, why is this needed?

If you know how to do this properly, can you send me a patch please?

dvzrv commented on 2018-01-24 10:06

@agraef: You need to properly reference the submodules of the main git repository [1].

[1] https://wiki.archlinux.org/index.php/VCS_package_guidelines#Git_Submodules

aggraef commented on 2018-01-18 00:53

I think I'll keep the 2 epoch, it's faust2 after all. :)

Eschwartz commented on 2018-01-18 00:28

No problem. ;)

Keep in mind for the future, though, that adding an epoch starts at 1, since the default (no epoch) is treated as equivalent to an epoch of 0.

If you want to risk people having installed the epoch=2 version in the last 15 minutes, you could even downgrade that, but I'm not entirely sure that is a good idea, strictly speaking... an epoch=2 isn't all that much uglier than any epoch at all.

aggraef commented on 2018-01-18 00:12

Done. @Eschwartz, thanks for pointing this out!

Eschwartz commented on 2018-01-17 22:14

Please add an epoch as it is specifically designed for the case where a package changes its numbering scheme in an incompatible manner.

All comments