Skip to content
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

FFTW build fail on ARMv7 #90

Closed
RGerzaguet opened this issue Feb 13, 2019 · 4 comments
Closed

FFTW build fail on ARMv7 #90

RGerzaguet opened this issue Feb 13, 2019 · 4 comments

Comments

@RGerzaguet
Copy link

Hello,

I have currently an issue when building FFTW module in Julia on a ARMv7 (with Yocto embedded linux).
I get the following output:

(v1.0) pkg> build FFTW
  Building Conda  `~/.julia/packages/Conda/CpuvI/deps/build.log`
  Building FFTW ─ `~/.julia/packages/FFTW/p7sLQ/deps/build.log`
┌ Error: Error building `FFTW`: 
│ ┌ Warning: platform_key() is deprecated, use platform_key_abi() from now on
│ │   caller = ip:0x0
│ └ @ Core :-1
│ ┌ Warning: Could not extract the platform key of https://github.com/JuliaMath/FFTWBuilder/releases/download/v3.3.8+1/FFTW.arm-linux-gnueabihf.tar.gz; continuing...
│ └ @ BinaryProvider ~/.julia/packages/BinaryProvider/4F5Hq/src/Prefix.jl:185
│ ERROR: LoadError: LoadError: Could not unpack /home/root/.julia/packages/FFTW/p7sLQ/deps/usr/downloads/FFTW.arm-linux-gnueabihf.tar.gz into /home/root/.julia/packages/FFTW/p7sLQ/deps/usr
│ Stacktrace:
│  [1] error(::String) at ./error.jl:33
│  [2] #unpack#94(::Bool, ::Function, ::String, ::String) at /home/root/.julia/packages/BinaryProvider/4F5Hq/src/PlatformEngines.jl:660
│  [3] #unpack at ./tuple.jl:0 [inlined]
│  [4] #install#129(::Prefix, ::String, ::Bool, ::Bool, ::Bool, ::Function, ::String, ::String) at /home/root/.julia/packages/BinaryProvider/4F5Hq/src/Prefix.jl:347
│  [5] (::getfield(BinaryProvider, Symbol("#kw##install")))(::NamedTuple{(:prefix, :force, :verbose),Tuple{Prefix,Bool,Bool}}, ::typeof(install), ::String, ::String) at ./tuple.jl:0
│  [6] top-level scope at /home/root/.julia/packages/FFTW/p7sLQ/deps/build_fftw.jl:37
│  [7] include at ./boot.jl:317 [inlined]
│  [8] include_relative(::Module, ::String) at ./loading.jl:1044
│  [9] include(::Module, ::String) at ./sysimg.jl:29
│  [10] include(::String) at ./client.jl:392
│  [11] top-level scope at /home/root/.julia/packages/FFTW/p7sLQ/deps/build.jl:48
│  [12] include at ./boot.jl:317 [inlined]
│  [13] include_relative(::Module, ::String) at ./loading.jl:1044
│  [14] include(::Module, ::String) at ./sysimg.jl:29
│  [15] include(::String) at ./client.jl:392
│  [16] top-level scope at none:0in expression starting at /home/root/.julia/packages/FFTW/p7sLQ/deps/build_fftw.jl:33in expression starting at /home/root/.julia/packages/FFTW/p7sLQ/deps/build.jl:19
│ tar: unrecognized option '--directory=/home/root/.julia/packages/FFTW/p7sLQ/deps/usr'
│ BusyBox v1.23.1 (2016-01-07 07:47:07 PST) multi-call binary.
│ 
│ Usage: tar -[cxtZzJjahmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
└ @ Pkg.Operations /buildworker/worker/package_linuxarmv7l/build/usr/share/julia/stdlib/v1.0/Pkg/src/Operations.jl:1097

Any clue to address this ?
Thank you in advance,
BR

@ararslan
Copy link
Member

It looks like the generated tar command is incorrect on your system. What is the output of tar --version?

@RGerzaguet
Copy link
Author

Thank you very much for your quick answer.
Seems that tar has been built by busy box, which takes different parameters as inputs

root@ettus-e3xx-sg3-rose1:~/Receiver# tar --h
tar: unrecognized option '--h'
BusyBox v1.23.1 (2016-01-07 07:47:07 PST) multi-call binary.

Usage: tar -[cxtZzJjahmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...

Any clue to address that ?
Thanks again !
BR

@ararslan
Copy link
Member

I don't think there's anything that the FFTW package can do differently to address this, unfortunately. Could you open this issue on the BinaryProvider repository, providing some details about your system as well?

@RGerzaguet
Copy link
Author

Hello again,
Sorry for my (very very) late reply. Indeed it was due to an issue from BinaryProvider, solved by now.
Sorry for the noise and thank you deeply for the support !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants