-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
configure fails: could not determine faust version #135
Comments
Is that the latest release or is that from git repository?
If it is the latest release, please checkout from git. btw. I've just added faust 2.68.1 to the good versions in the wscript, so you could build guitarix now with that version. |
This is the 0.44.1 release + this patch:
|
You should probably make a release because more people will be having this problem once they install the latest faust. |
The latest master revision 80f94b3 still fails:
|
That is a really strange error. It looks like we can't fetch the version output string from faust (faust --version). I never see that before. I've implemented a fix for it now, however, that means you cant use faust for build guitarix. Still, you didn't need to use faust for that anyway. |
If faust isn't needed - why does configure look for it then? |
Nope, it is a developer tool. We use faust to develop guitarix, but guitarix comes with all needed sources to build the binary's without using faust. Hence the configure option --no-faust. You only need faust when you plan to work on the included faust sources. |
How can I install this? it's not in the distro, the port fails.
but it's there:
|
maybe 'local' is not in your PATH variable. |
Why would an include folder be in my path? These should be determined by
the config script, and that is what is failing. This has got to be the
lamest answer I’ve gotten on github.
I think I’m done using amateur open source software. Ubuntu Studio stopped
working, now FreeBSD has dropped guitarix from their distro. Windows may
have its issues, but dependability is not one of them. Life is too short to
screw around with open source - I don’t mind paying for stuff that actually
works.
…On Tue, Nov 21, 2023 at 7:52 PM Hermann ***@***.***> wrote:
maybe 'local' is not in your PATH variable.
Such library's should be installed in /usr/ to avoid such trouble.
—
Reply to this email directly, view it on GitHub
<#135 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJUE4TUJM3FWHSFYP453BLYFVZH7AVCNFSM6AAAAAA6OL47NCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRSGA2DMOBVHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Bruce Davidson
|
Good luck |
I shouldn’t rag on you just because I’m frustrated. You don’t deserve that. |
I didn't understand how that would be related to the fftw3 header not found. However I'm glad you find a solution. |
The issue with fftw3 is these lines:
```
conf.check(header_name='fftw3.h', mandatory=1)
conf.check_cfg(package='fftw3f', args=['--cflags','--libs','fftw3f >=
3.3.8'], uselib_store='FFTW3', mandatory=1)
```
It’s checking for the header, and then checking where it is? I’m not
familiar enough with waf convention to understand why that is done - 45
years in IT and I’ve never run into waf until I retired :(. In any case,
this may be a linux idiom that doesn’t work on unix. Unfortunately,
unix-like doesn’t imply unix-compatibility - don’t get me started on that.
So if I comment over the header check, that will work on unix, but there
are many more such ‘idioms’ that fail, and I keep commenting them out; this
is the ‘rabbit hole’ I refer to.
The port process compensates for this - it uses some monkey shines to fake
out the build process to think it’s compatible. Except for that
‘conf.gxload('faust')’.
Thanks for the tip on the —nofaust flag.
…On Sun, Nov 26, 2023 at 11:12 PM Hermann ***@***.***> wrote:
I didn't understand how that would be related to the fftw3 header not
found. However I'm glad you find a solution.
A more general solution may be the use of the --no-faust configure flag,
as that will skip all faust tests anyway.
—
Reply to this email directly, view it on GitHub
<#135 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJUE4UPHOO3KYPUQPW3EODYGQ4ONAVCNFSM6AAAAAA6OL47NCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRXGI2DSOJSGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Bruce Davidson
|
Strange is that this have worked for years with BSD, or, no one have tell me that it didn't work and they just implement a workaround without tell me about. So, I can't fix it. |
Many things build just fine on unix straight off github. But over time
linux and unix diverge more and more. Waf is fine - i'm just grumbling :)
Vst3 would be very nice - I'll check it out!
…On Mon, Nov 27, 2023 at 7:04 AM Hermann ***@***.***> wrote:
Strange is that this have worked for years with BSD, or, no one have tell
me that it didn't work and they just implement a workaround without tell me
about. So, I can't fix it.
However, you are right, the waf system is a bit antiquated, but given how
old guitarix is, that may be no wonder.
This day's I'm working on a new port of guitarix to make it a vst3 plug.
That one use plain make.
It may be of some interest for you, you could find it here:
https://github.com/brummer10/guitarix.vst
I would like to know if that gives you any issues when you try to build it
under BSD, if so, well, we are in the early day's of development, so maybe
we could sort it out early.
—
Reply to this email directly, view it on GitHub
<#135 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJUE4SC4TRDIMZYHF6U55LYGSTXLAVCNFSM6AAAAAA6OL47NCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRYGAYTAMRZHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Bruce Davidson
|
Hi there! Any updates for the FreeBSD port? Can I help on something? |
Hi |
Version: 0.44.1
faust-2.68.1
Python-3.9
FreeBSD 13.2
The text was updated successfully, but these errors were encountered: