From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Michael Nosthoff" <buildroot@heine.tech>
Cc: Samuel Martin <s.martin49@gmail.com>,
Michael Nosthoff via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/sqlitecpp: new package
Date: Wed, 10 Jul 2024 22:06:20 +0200 [thread overview]
Message-ID: <20240710220620.6ae4b41f@windsurf> (raw)
In-Reply-To: <27bb6-668eac00-5-6e811900@44543821>
Hello,
On Wed, 10 Jul 2024 17:42:28 +0200
"Michael Nosthoff" <buildroot@heine.tech> wrote:
> > We need a gcc version check. Which version depends on which C++11
> > features are used. Some packages need gcc 4.7, some gcc 4.8, some gcc
> > 4.9:
>
> then I will prepare a patch for this package.
OK. Make sure to figure out exactly which gcc version is needed :-)
> that's what I feared. Do you have some advice on how to test with gcc
> 4.7/4.7/4.9? The oldest toolchain on bootlin I can find is gcc 5.4.
> Is there any other toolchain located somewhere with an older gcc?
You can find a collection of old toolchains
at http://autobuild.buildroot.net/toolchains/tarballs/ for example.
But not sure they are sufficiently old in fact :/
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-10 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 8:13 [Buildroot] [PATCH] package/sqlitecpp: new package Michael Nosthoff via buildroot
2024-07-10 8:48 ` Thomas Petazzoni via buildroot
2024-07-10 9:16 ` Michael Nosthoff via buildroot
2024-07-10 14:39 ` Thomas Petazzoni via buildroot
2024-07-10 15:42 ` Michael Nosthoff via buildroot
2024-07-10 20:06 ` Thomas Petazzoni via buildroot [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=20240710220620.6ae4b41f@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@heine.tech \
--cc=s.martin49@gmail.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.