FS#31118 - [libffi] has a non-standard directory for includes
Attached to Project:
Arch Linux
Opened by Shawn Rutledge (ecloud) - Monday, 13 August 2012, 13:51 GMT
Last edited by Stéphane Gaudreault (stephane) - Sunday, 09 September 2012, 00:58 GMT
Opened by Shawn Rutledge (ecloud) - Monday, 13 August 2012, 13:51 GMT
Last edited by Stéphane Gaudreault (stephane) - Sunday, 09 September 2012, 00:58 GMT
|
Details
core/libffi 3.0.11-1 puts the headers into
/usr/lib/libffi-3.0.11/include, but this is not like most
other packages, and actually makes it tricky to compile
Wayland. It would make more sense to have
/usr/include/libffi/. Some other distros reportedly have
fixed this in their libffi packages (Ubuntu etc.)
|
This task depends upon
Closed by Stéphane Gaudreault (stephane)
Sunday, 09 September 2012, 00:58 GMT
Reason for closing: Not a bug
Additional comments about closing: Wayland should use pkg-config libffi --cflags.
Sunday, 09 September 2012, 00:58 GMT
Reason for closing: Not a bug
Additional comments about closing: Wayland should use pkg-config libffi --cflags.
Reason why libffi installs these files in /usr/lib/../include is because these include files are architecture-specific. The same applies to gcc, which puts architecture-specific includes in /usr/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/include/