-
Notifications
You must be signed in to change notification settings - Fork 86
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
fft module tries to fetch from now invalid source #231
Comments
Thanks for bringing this to our attention. I had in the past tried to use a 2015 version of the Github version ffts:dfab21f, however it requires additional patches for |
Quick update: the version from the Github repository doesn't build with autoconf/configure/make, even when moving the
|
I would say option #1 unless there is a very good reason to use the bleeding edge github source?
…On March 11, 2019 10:48:58 PM GMT+01:00, "Matthias Görges" ***@***.***> wrote:
Quick update: the version from the Github repository doesn't build with
autoconf/configure/make, even when moving the `ftts.h` file in the
right place and fixing the library includes - see an [issue
#68](anthonix/ffts#68) which says to use
`cmake` only. I did try the
[linkotec](https://github.com/linkotec/ffts) fork, but that doesn't
help either.
Options are:
1. Host the `ffts-0.7.tar.gz` file in the LN website, as we do for
`libgd`
1. Upgrade but use `cmake` to compile, which might not be available on
all platforms. Also don't know how to cross-compile with it.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#231 (comment)
|
Commit 6317028 does restore the ability to compile for the time being. |
Cool, thank you. Runs perfectly now. |
Using the 'fft' module makes lambdanative try to fetch the library that module is based upon (ffts) from http://anthonix.com/ffts/releases/ffts-0.7.tar.gz which is not a valid source any longer.
https://github.com/anthonix/ffts seems to be the currently available source.
The text was updated successfully, but these errors were encountered: