[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGNsrLBf7fecd+-7WrAAsxRQFzSswNCTBWmwNTre-1ChYdRmpg@mail.gmail.com>
Date: Fri, 30 Jun 2017 08:53:15 +0300
From: Fathi Boudra <fathi.boudra@...aro.org>
To: Bamvor Zhang Jian <bamvor.zhangjian@...aro.org>
Cc: Michael Ellerman <mpe@...erman.id.au>,
linux-kselftest@...r.kernel.org, Shuah Khan <shuah@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] selftests: gpio: use pkg-config to determine libmount CFLAGS/LDLIBS
On 30 June 2017 at 05:20, Bamvor Zhang Jian <bamvor.zhangjian@...aro.org> wrote:
> On 29 June 2017 at 19:39, Fathi Boudra <fathi.boudra@...aro.org> wrote:
>> On 29 June 2017 at 12:01, Michael Ellerman <mpe@...erman.id.au> wrote:
>>> Fathi Boudra <fathi.boudra@...aro.org> writes:
>>>
>>>> Fix hardcoded and misplaced libmount headers. Use pkg-config instead to
>>>> figure out CFLAGS/LDLIBS, fixing also their value for cross-compilation.
>>>
>>> Can you explain how it fixes the values for cross-compilation?
>>
>> When pkg-config is invoked in a cross-build environment, it will
>> return your sysroot headers path instead of the hardcoded
>> -I/usr/include/libmount
>>
>> For example in my oe environment, when I invoke "pkg-config --cflags
>> mount", it returns:
>> -I/build/tmp-rpb-glibc/sysroots/hikey/usr/include/libmount
> I suppose we could also pass the extra CFLAGS and LDFLAGS directly to
> make it work. correct?
or use the appropriate tool for getting CFLAGS/LDFLAGS instead of:
1. hardcoding it and potentially get them wrong
2. expecting the user will have to take extra steps, while he can just run make
> Regards
>
> Bamvor
>>
>>> cheers
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
>>> the body of a message to majordomo@...r.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists