On Dec 20, 2021, at 16:58, David Bremner wrote:
> Tomi Ollila writes:
>
>> On Fri, Dec 17 2021, David Bremner wrote:
>>>
>>> Although I don't consider GNU standards normative for notmuch, there is
>>> some value in doing things a standard way. In particular the way notmuch
>>> uses {C,CPP,LD,CXX
Tomi Ollila writes:
> On Fri, Dec 17 2021, David Bremner wrote:
>>
>> Although I don't consider GNU standards normative for notmuch, there is
>> some value in doing things a standard way. In particular the way notmuch
>> uses {C,CPP,LD,CXX}FLAGS follows e.g. [1].
>
> Does it ?
>
> I initially tho
On Fri, Dec 17 2021, David Bremner wrote:
> Ryan Schmidt writes:
>
>> The notmuch build system puts -I and -L flags in the wrong order.
>>
>> Specifically, -I flags the user might specify in the CPPFLAGS
>> environment variable appear before the -I flags for the project's own
>> directories, resu
Ryan Schmidt writes:
> The notmuch build system puts -I and -L flags in the wrong order.
>
> Specifically, -I flags the user might specify in the CPPFLAGS
> environment variable appear before the -I flags for the project's own
> directories, resulting in build failure if a previous version of
> n
The notmuch build system puts -I and -L flags in the wrong order.
Specifically, -I flags the user might specify in the CPPFLAGS environment
variable appear before the -I flags for the project's own directories,
resulting in build failure if a previous version of notmuch (whose headers
differ su
