# @everywhere using FFTW produces "Package FFTW not found in current path"

**URL:** https://discourse.julialang.org/t/everywhere-using-fftw-produces-package-fftw-not-found-in-current-path/26342
**Category:** Julia at Scale
**Tags:** question
**Created:** [July 14, 2019, 1:11pm UTC](https://discourse.julialang.org/t/everywhere-using-fftw-produces-package-fftw-not-found-in-current-path/26342 "2019-07-14T13:11:36Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![lwabeke](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lwabeke/32/4005_2.png) [@lwabeke](https://discourse.julialang.org/u/lwabeke)
#### Post date: [July 15, 2019, 8:53am UTC](https://discourse.julialang.org/t/everywhere-using-fftw-produces-package-fftw-not-found-in-current-path/26342/2 "2019-07-15T08:53:57Z")

</div>

Sorry for suggesting the obvious, but have you tried:  
@everywhere Pkg.add(“FFTW”)  
@everywhere Pkg.add(“SpecialFunctions”)

I just now tried and on my system, the using FFTW worked without complains. The using SpecialFunctions complained, but worked after the distributed install (I would guess you typically don’t even need a distributed install and a single local Pkg.add should work, unless your running this on some cluster setup).

Maybe a

```julia
@everywhere Pkg.status() 

```

will give some additional information, although it isn’t easy to decode the output due to arriving async.

---

_[View the full topic](https://discourse.julialang.org/t/everywhere-using-fftw-produces-package-fftw-not-found-in-current-path/26342)._