On Mon, Aug 21, 2023 at 12:46 PM Mark Hatle
<[email protected]> wrote:
>
> I was trying to build the kconfig-frontends recipe locally the other day and 
> ran
> into a problem where it reported unsafe "/usr/include" path.
>
> This seems to have been triggered because I actually had a 
> /usr/include/ncursesw
> on one of my host systems.  Other systems I had didn't have this directory and
> no issue was reported.
>
>
> I tracked this down to
>
> https://gitlab.com/ymorin/kconfig-frontends/-/blob/master/configure.ac?ref_type=heads#L349
>
> Lines 349 and 350.  I changed to them to
> '-I=...' in both cases and it appears to have solved the problem I was having.
>
>
> Has anyone else seen this issue, and is my possible fix above reasonable in 
> this
> case?  If so I'll generate a patch to do just that and send it to the list.

I have not seen this exact issue but similar issues have been spotted
in many packages, usually
just removing the absolute path has helped in some cases. Changing to
=/include/path works
with sysroot enabled compilers and may not work with old compilers or
sysroot disabled configurations
maybe using includedir autoconf variable could be more portable IDK.

>
> --Mark
>
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#104514): 
https://lists.openembedded.org/g/openembedded-devel/message/104514
Mute This Topic: https://lists.openembedded.org/mt/100880280/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to