I am confused about libffi. Some programs cannot find the header files (ffi.h and targetffi.h). I have installed dev-libs/libffi and virtual/libffi. I noticed that gcc is compiled with (-libffi). I am very thin ice here but wouldn't it be nice to have a eselect tool for ffi to "point" out where ffi is located. I mean now since the "package" is virtual. Reproducible: Always
(In reply to comment #0) > I am confused about libffi. Some programs cannot find the header files (ffi.h > and targetffi.h). I have installed dev-libs/libffi and virtual/libffi. I > noticed that gcc is compiled with (-libffi). You need to use pkg-config. Any package that is using libffi but is not using pkg-config is broken. Example: $ pkg-config --cflags-only-I libffi -I/usr/lib64/libffi-3.0.9/include > I am very thin ice here but wouldn't it be nice to have a eselect tool for ffi > to "point" out where ffi is located. I mean now since the "package" is virtual. Unrequired. The virtual is there only because of historical reasons when libffi got unmaintained, and we had to use the copy from gcc. And also if it becomes unmaintained again in future, we won't have to update X number of packages, we just update the virtual to point to gcc's libffi.
(In reply to comment #1) > (In reply to comment #0) > > I am confused about libffi. Some programs cannot find the header files (ffi.h > > and targetffi.h). I have installed dev-libs/libffi and virtual/libffi. I > > noticed that gcc is compiled with (-libffi). > > You need to use pkg-config. Any package that is using libffi but is not using > pkg-config is broken. Example: > > $ pkg-config --cflags-only-I libffi > -I/usr/lib64/libffi-3.0.9/include > > > I am very thin ice here but wouldn't it be nice to have a eselect tool for ffi > > to "point" out where ffi is located. I mean now since the "package" is virtual. > > Unrequired. The virtual is there only because of historical reasons when libffi > got unmaintained, and we had to use the copy from gcc. And also if it becomes > unmaintained again in future, we won't have to update X number of packages, we > just update the virtual to point to gcc's libffi. > Thank you for your help, explanation and time. Have a great day.
