All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	Denis Kenzior <denkenz@gmail.com>
Subject: Re: [PATCH BlueZ] build: Fix build with latest tree
Date: Thu, 18 Mar 2021 10:12:03 +0100	[thread overview]
Message-ID: <FB99CA80-BBDB-437B-BDD0-5FA0DF67FD7E@holtmann.org> (raw)
In-Reply-To: <CABBYNZ+-VHu-GAb7g6XF15V3fm9XzrvXV6c_V6Uj1-1SgivQ2Q@mail.gmail.com>

Hi Luiz,

>>>> Latest ell tree has introduced useful.h and main-private.h which are
>>>> required to build:
>>>> 
>>>> ell/cert-crypto.c:35:10: fatal error: useful.h: No such file or
>>>> directory
>>>>  35 | #include "useful.h"
>>>>        |          ^~~~~~~~~~
>>>> ...
>>>> ---
>>>> Makefile.am | 4 +++-
>>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>> 
>>>> diff --git a/Makefile.am b/Makefile.am
>>>> index ff0df2196..7fce2e7c0 100644
>>>> --- a/Makefile.am
>>>> +++ b/Makefile.am
>>>> @@ -135,7 +135,9 @@ ell_headers = ell/util.h \
>>>>                      ell/asn1-private.h \
>>>>                      ell/cert-private.h \
>>>>                      ell/pem-private.h \
>>>> -                     ell/uuid.h
>>>> +                     ell/uuid.h \
>>>> +                     ell/useful.h \
>>>> +                     ell/main-private.h
>>>> 
>>> 
>>> this is the wrong fix. It will break in the tarballs. ELL will not install ell/useful.h ever. So every tarball needs to ensure that ell/useful.h is included. Which means you need to follow the fix from iwd here.
>> 
>> Are you talking about this:
>> 
>> https://git.kernel.org/pub/scm/network/wireless/iwd.git/commit/?id=ed05585063f2e6d8f2fcd5f008b861062ac7a429
>> 
>> Shall we use the same mechanism to link the headers?
> 
> I tried with distcheck to see what would be included in the tarball,
> both useful.h and main-private.h do appear to be included, perhaps you
> are saying that when we use non-built-in/shared ell
> (--enable-external-ell) those headers are not installed, but I guess
> in that case we don't need the private header as we won't be using the
> built-in sources, or I'm missing something. That said perhaps this is
> different in case of iwd as it seems to be using useful.h directly:
> 
> https://git.kernel.org/pub/scm/network/wireless/iwd.git/commit/?id=17cf4da72613e80d08d51401399d02683ba8664b

for the build case --enable-external-ell you need need ell/useful.h linked or provided in the tarball. All other headers are not needed in that case. See my iwd commit that does exactly that.

Regards

Marcel


      reply	other threads:[~2021-03-18  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 20:58 [PATCH BlueZ] build: Fix build with latest tree Luiz Augusto von Dentz
2021-03-16 21:33 ` [BlueZ] " bluez.test.bot
2021-03-17  8:38 ` [PATCH BlueZ] " Marcel Holtmann
2021-03-17 18:29   ` Luiz Augusto von Dentz
2021-03-17 20:42     ` Luiz Augusto von Dentz
2021-03-18  9:12       ` Marcel Holtmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FB99CA80-BBDB-437B-BDD0-5FA0DF67FD7E@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=denkenz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.