| View previous topic :: View next topic |
| Author |
Message |
audiodef
Watchman
Joined: 06 Jul 2005
Posts: 6639
Location: The soundosphere
|
 Posted: Sun Dec 02, 2012 7:08 pm Post subject: FFTW update seems to break env vars |
 |
|
This month's update on one of my machines included fftw-3.3.2 -> fftw-3.3.3. After this happened, any program requiring fftw fails exactly like this:
| Code: |
checking for fftw3f... no
configure: error: Package requirements (fftw3f >= 3.0.0) were not met:
No package 'fftw3f' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables fftw3f_CFLAGS
and fftw3f_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
|
This happens with multiple programs, such as Rosegarden and Whysynth.
However:
| Code: |
locate fftw3f
/usr/lib32/libfftw3f.so
/usr/lib32/libfftw3f.so.3
/usr/lib32/libfftw3f.so.3.2.4
/usr/lib64/libfftw3f.so.3
/usr/lib64/libfftw3f.so.3.3.2
|
I think this is the standard path, and I don't see what happened to blow fftw up. Downgrading back to 3.3.2 does not fix the problem.
Posted here because I don't think this is about unsupported software or multimedia, but about portage happenings.
_________________
decibel Linux: https://decibellinux.org
Github: https://github.com/Gentoo-Music-and-Audio-Technology
Facebook: https://www.facebook.com/decibellinux
Discord: https://discord.gg/73XV24dNPN |
|
| Back to top |
|
 |
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Sun Dec 02, 2012 8:26 pm Post subject: |
|
|
| What pkgconfig files does sci-libs/fftw install ? |
|
| Back to top |
|
|
leo.the_zoo
Apprentice
Joined: 04 Jul 2005
Posts: 160
Location: Poland
|
| Posted: Mon Dec 03, 2012 12:08 am Post subject: |
|
|
I've just solved a similar problem with ambertools-12 and fftw. The problem is caused by the changes in autotools-utils.eclass (and similar changes in cmake utils causing e.g. emerge pykde4 to fail).
Every ebuild that generates several directories, e.g. for compiling the same package with different precision and using AUTOTOOLS_BUILD_DIR or CMAKE_BUILD_DIR variable will not install what it should, because all builds will be performed in the same trajectory and only the latest build will be installed. This will make only a fraction of *.pc files to be installed and in case of fftw these are files specifying the location of long double precision builds, hence pkg-config fftw3 --libs will fail.
To prevent that problem, you have to change these variables (AUTOTOOLS_BUILD_DIR or CMAKE_BUILD_DIR) to BUILD_DIR and everything should work fine again.
I only wonder why someone pushed changes breaking some ebuilds without finding and amending affected files... |
|
| Back to top |
|
|
stefantalpalaru
n00b
Joined: 11 Jan 2009
Posts: 24
Location: Italy
|
| Posted: Mon Dec 03, 2012 11:10 am Post subject: |
|
|
Thanks for the fix!
Can you open an issue on bugzilla so the developers get a chance to fix it sometime this year? |
|
| Back to top |
|
|
leo.the_zoo
Apprentice
Joined: 04 Jul 2005
Posts: 160
Location: Poland
|
| Posted: Mon Dec 03, 2012 2:09 pm Post subject: |
|
|
I just posted a bug report.
The entire investigation was not on my part but the developer who posted the solution regarding pykde4 on Bugzilla. Thanks to him I found out what's wrong in this case.
UPDATE: now eclasses were updated and accept both old and new variables, although if your ebuild happens to be using the old ones, you should see a warning, but the package will be built properly. |
|
| Back to top |
|
|
|
Portage & Programming
