From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Luca Ceresoli <luca.ceresoli@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/agentpp: fix build with gcc 4.8
Date: Wed, 20 Sep 2023 21:32:29 +0200 [thread overview]
Message-ID: <20230920213229.7f6670e9@windsurf> (raw)
In-Reply-To: <20230918201623.2639458-1-fontaine.fabrice@gmail.com>
On Mon, 18 Sep 2023 22:16:23 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following build failure with gcc 4.8 raised since bump of snmppp
> to version 3.5.0 in commit e011fa0415883b9d44df616cfaf6956e1a11da88:
>
> configure: error: Cannot find suitable libsnmp++ library
>
> [...]
>
> configure:9496: checking if libsnmp++ can be linked with flags from pkg-config
> configure:9528: /home/buildroot/autobuild/run/instance-1/output-1/host/bin/arm-none-linux-gnueabi-g++ -o conftest -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -g0 -D_FORTIFY_SOURCE=1 -pthread -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_XOPEN_SOURCE=XPG6 conftest.cpp -L/home/buildroot/autobuild/run/instance-1/output-1/host/bin/../arm-buildroot-linux-gnueabi/sysroot/usr/lib -lsnmp++ >&5
> In file included from /home/buildroot/autobuild/run/instance-1/output-1/host/arm-buildroot-linux-gnueabi/sysroot/usr/include/snmp_pp/snmp_pp.h:71:0,
> from conftest.cpp:92:
> /home/buildroot/autobuild/run/instance-1/output-1/host/arm-buildroot-linux-gnueabi/sysroot/usr/include/snmp_pp/uxsnmp.h:628:35: error: 'nullptr' was not declared in this scope
> CSNMPMessage *snmp_message = nullptr);
> ^
>
> Fixes:
> - http://autobuild.buildroot.org/results/f272473e7b588f5390b183072935a0217290ee4e
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/agentpp/agentpp.mk | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks. That being said, I think ideally it should
be the agentpp build system that passes -std=c++11, rather than having
Buildroot need to know about this.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-20 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 20:16 [Buildroot] [PATCH 1/1] package/agentpp: fix build with gcc 4.8 Fabrice Fontaine
2023-09-19 7:02 ` Luca Ceresoli via buildroot
2023-09-20 19:32 ` Thomas Petazzoni via buildroot [this message]
2023-09-25 11:40 ` 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=20230920213229.7f6670e9@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=luca.ceresoli@bootlin.com \
--cc=thomas.petazzoni@bootlin.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.