From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/mosquitto: allow to build as static lib
Date: Thu, 01 Aug 2019 19:25:42 +0200 [thread overview]
Message-ID: <874l30x0fd.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <b1957631-ca8b-38ab-9b24-5549e8e13e23@railnova.eu> (Titouan Christophe's message of "Thu, 1 Aug 2019 19:09:50 +0200")
>>>>> "Titouan" == Titouan Christophe <titouan.christophe@railnova.eu> writes:
> Hello Peter,
> Thank you for reviewing this series !
> On 8/1/19 12:41 PM, Peter Korsgaard wrote:
>>>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>
>> Hi,
>>
>> >> +ifeq ($(BR2_STATIC_LIBS),y)
>> >> +MOSQUITTO_MAKE_OPTS += WITH_STATIC_LIBRARIES=yes WITH_SHARED_LIBRARIES=no
>> >> +else
>> >> +MOSQUITTO_MAKE_OPTS += WITH_STATIC_LIBRARIES=no WITH_SHARED_LIBRARIES=yes
>> >> +endif
>>
>> > We actually have 3 variants:
>>
>> > - static only (BR2_STATIC_LIBS)
>> > - shared only (BR2_SHARED_LIBS)
>> > - shared and static (BR2_SHARED_STATIC_LIBS)
>>
>> > So I reworked it to take that into consideration and committed, thanks.
>>
>> Sorry, I will have to take that back. I did a test compilation with a
>> completely static (BR2_STATIC_LIBS) setup, which failed:
> Could you share the defconfig you have used to obtain that result ?
It was afaik just the default arm variant with BR2_STATIC_LIBS enabled.
> When I run test-pkg with BR2_PACKAGE_MOSQUITTO=y (and
> BR2_PACKAGE_MOSQUITTO_BROKER defaults to y), I see:
> """br-arm-full-static [5/6]: OK""".
Hmm, very odd. With current git HEAD and this patch 1/3 applied and the
following config:
BR2_arm=y
BR2_STATIC_LIBS=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-arm-full-static-2019.02-rc1.tar.bz2"
BR2_TOOLCHAIN_EXTERNAL_GCC_7=y
BR2_TOOLCHAIN_EXTERNAL_HEADERS_4_4=y
BR2_TOOLCHAIN_EXTERNAL_LOCALE=y
# BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set
BR2_TOOLCHAIN_EXTERNAL_CXX=y
BR2_PACKAGE_MOSQUITTO=y
(E.G. support/config-fragments/autobuild/br-arm-full-static.config + mosquitto)
I get the expected failure:
In file included from security.c:25:0:
lib_load.h:23:11: fatal error: dlfcn.h: No such file or directory
# include <dlfcn.h>
^~~~~~~~~
compilation terminated.
Makefile:189: recipe for target 'security.o' failed
br-arm-full-static-2019.02-rc1.tar.bz2 does not contain a dlfcn.h file,
so that makes sense.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-08-01 17:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 10:06 [Buildroot] [PATCH 0/3] Update package mosquitto Titouan Christophe
2019-07-18 10:06 ` [Buildroot] [PATCH 1/3] package/mosquitto: allow to build as static lib Titouan Christophe
2019-08-01 10:23 ` Peter Korsgaard
2019-08-01 10:41 ` Peter Korsgaard
2019-08-01 17:09 ` Titouan Christophe
2019-08-01 17:25 ` Peter Korsgaard [this message]
2019-08-02 13:18 ` Titouan Christophe
2019-08-02 15:58 ` Peter Korsgaard
2019-07-18 10:06 ` [Buildroot] [PATCH 2/3] package/mosquitto: Switch systemd unit to Type=notify and depend on network Titouan Christophe
2019-08-01 10:27 ` Peter Korsgaard
2019-08-02 8:51 ` Titouan Christophe
2019-07-18 10:06 ` [Buildroot] [PATCH 3/3] package/mosquitto: bump to v1.6.3 Titouan Christophe
2019-08-01 10:48 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2019-08-03 9:38 [Buildroot] [PATCH v2 0/3] Update package mosquitto Titouan Christophe
2019-08-03 9:38 ` [Buildroot] [PATCH 1/3] package/mosquitto: allow to build as static lib Titouan Christophe
2019-08-03 11:13 ` Peter Korsgaard
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=874l30x0fd.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox