| View previous topic :: View next topic |
| Author |
Message |
CaptainBlood
Advocate
Joined: 24 Jan 2010
Posts: 3881
|
 Posted: Mon Oct 28, 2019 4:41 am Post subject: Writing ebuild: issue path solving system #include <> |
 |
|
Trying to update ebuild to prevent: | Code: | | #include <librsvg/rsvg.h> |
to fails as system implements: | Code: | | /usr/include/librsvg-2.0/librsvg/rsvg.h |
I tried to patch the reference to the include, which works, but this referenced include file references: | Code: | | #include <glib-object.h> |
which failed as system implements: | Code: | | /usr/include/glib-2.0/glib-object.h |
Please remember that both referenced files are already in /usr/include.
First issue is source to system reference.
Second issue is system reference to system reference.
As I'm writing, I start to wonder is there any possibily to patch an 'include search path functionnality' from a ebuild perspective? Or maybe to inherit something in ebuild.
Thks 4 ur attention.
Last edited by CaptainBlood on Wed Oct 30, 2019 5:03 am; edited 1 time in total |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22697
|
| Posted: Tue Oct 29, 2019 2:02 am Post subject: |
|
|
| The upstream build system should have added an appropriate -isystem path to handle this. Usually, this will be determined by asking pkg-config about the location for the supporting package. |
|
| Back to top |
|
|
CaptainBlood
Advocate
Joined: 24 Jan 2010
Posts: 3881
|
| Posted: Wed Oct 30, 2019 5:10 am Post subject: |
|
|
Thks,
You confirmed the conclusion I was brought up after investigation.
AFAIR a Makefile seemed to call pkg-info in this respect, but I couldn't understand why it is not taken into account.
Thks 4 ur attention, interest & support. |
|
| Back to top |
|
|
|
Portage & Programming
