From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15997] Build Squid with GCC12.3 in Buildroot 2024.02 will fail
Date: Sat, 16 Mar 2024 13:49:01 +0000 [thread overview]
Message-ID: <bug-15997-163-0GUVP7o60p@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15997-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15997
--- Comment #2 from Peter Seiderer <ps.report@gmx.net> ---
Note: this one is the only g++ call of the squid build using the host compiler
'/usr/bin/g++' to build an internal tool
Which host system? Which host compiler ('/usr/bin/g++ --version')?
Compiles for me without failure using g++ 12.3.0, 13.2.1 and 14.0.1, but
e.g. the following fails with the same error you mention:
$ /usr/bin/g++ -std=c++11 -O2
-I/home/seiderer/Work/Buildroot/build_bug_15997_squid_001/host/include -o
cf_gen ./cf_gen.cc -I. -I../include/ -I../src
./cf_gen.cc: In function ‘int main(int, char**)’:
./cf_gen.cc:268:63: error: forming reference to void
268 | auto &newEntry = entries.emplace_back(name);
| ^
./cf_gen.cc:277:68: error: forming reference to void
277 | auto &newEntry = entries.emplace_back("comment");
|
Same with '-std=c++14', but '-std=c++17' works fine...
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-03-16 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 21:11 [Buildroot] [Bug 15997] New: Build Squid with GCC12.3 in Buildroot 2024.02 will fail bugzilla
2024-03-16 12:06 ` [Buildroot] [Bug 15997] " bugzilla
2024-03-16 13:49 ` bugzilla [this message]
2024-03-16 13:55 ` bugzilla
2024-03-16 16:16 ` bugzilla
2024-03-17 21:36 ` bugzilla
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=bug-15997-163-0GUVP7o60p@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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