From: Lorenzo Salvadore <developer@lorenzosalvadore.it>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "ibuclaw@gdcproject.org" <ibuclaw@gdcproject.org>,
"andreast@gcc.gnu.org" <andreast@gcc.gnu.org>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: Ping: [PATCH] d: Update __FreeBSD_version values [PR107469]
Date: Sun, 27 Nov 2022 08:23:48 +0000 [thread overview]
Message-ID: <T0QtTZGf19D386SvbBgjizFaWhAV-Qcgsi35abZ4dAJ_DxJDFanoWYZsIcZDOXqQ8t6a-wOjItc3fC5YX5qwWyb788NNgzZXb-Fx4ydr284=@lorenzosalvadore.it> (raw)
In-Reply-To: <OP472vRO_13s3y8PI5nplVOCz6jhAMLTrsiRNglJYpsVepytiMkTHLMJAgzi83RBq0Lbv9VU0QNCuLNKiTUtVPJebd8pQPSAvXgzU7QL35k=@lorenzosalvadore.it>
Hello,
Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605685.html
I would like to remind that Gerald Pfeifer already volunteered to commit this patch
when it is approved. However the patch has not been approved yet.
Thanks,
Lorenzo Salvadore
------- Original Message -------
On Friday, November 11th, 2022 at 12:07 AM, Lorenzo Salvadore <developer@lorenzosalvadore.it> wrote:
> Update __FreeBSD_version values for the latest FreeBSD supported
> versions. In particular, add __FreeBSD_version for FreeBSD 14, which is
> necessary to compile libphobos successfully on FreeBSD 14.
>
> The patch has already been applied successfully in the official FreeBSD
> ports tree for the ports lang/gcc11 and lang/gcc11-devel. Please see the
> following commits:
>
> https://cgit.freebsd.org/ports/commit/?id=f61fb49b2e76fd4f7a5b7a11510b5109206c19f2
> https://cgit.freebsd.org/ports/commit/?id=57936dba89ea208e5dbc1bd2d7fda3d29a1838b3
>
> libphobos/ChangeLog:
>
> 2022-11-10 Lorenzo Salvadore developer@lorenzosalvadore.it
>
>
> PR d/107469.
> * libdruntime/core/sys/freebsd/config.d: Update __FreeBSD_version.
>
> ---
> libphobos/libdruntime/core/sys/freebsd/config.d | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/libphobos/libdruntime/core/sys/freebsd/config.d b/libphobos/libdruntime/core/sys/freebsd/config.d
> index 5e3129e2422..9d502e52e32 100644
> --- a/libphobos/libdruntime/core/sys/freebsd/config.d
> +++ b/libphobos/libdruntime/core/sys/freebsd/config.d
> @@ -14,8 +14,9 @@ public import core.sys.posix.config;
> // NOTE: When adding newer versions of FreeBSD, verify all current versioned
> // bindings are still compatible with the release.
>
> - version (FreeBSD_13) enum __FreeBSD_version = 1300000;
> -else version (FreeBSD_12) enum __FreeBSD_version = 1202000;
> + version (FreeBSD_14) enum __FreeBSD_version = 1400000;
> +else version (FreeBSD_13) enum __FreeBSD_version = 1301000;
> +else version (FreeBSD_12) enum __FreeBSD_version = 1203000;
> else version (FreeBSD_11) enum __FreeBSD_version = 1104000;
> else version (FreeBSD_10) enum __FreeBSD_version = 1004000;
> else version (FreeBSD_9) enum __FreeBSD_version = 903000;
> --
> 2.38.0
next prev parent reply other threads:[~2022-11-27 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 23:07 Lorenzo Salvadore
2022-11-27 8:23 ` Lorenzo Salvadore [this message]
2022-12-14 13:55 ` Ping^2: " Lorenzo Salvadore
2022-12-24 0:10 ` Gerald Pfeifer
2023-01-10 16:10 ` Ping^3: " Lorenzo Salvadore
2023-01-23 14:45 ` Iain Buclaw
2023-01-28 8:48 ` Lorenzo Salvadore
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='T0QtTZGf19D386SvbBgjizFaWhAV-Qcgsi35abZ4dAJ_DxJDFanoWYZsIcZDOXqQ8t6a-wOjItc3fC5YX5qwWyb788NNgzZXb-Fx4ydr284=@lorenzosalvadore.it' \
--to=developer@lorenzosalvadore.it \
--cc=andreast@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=ibuclaw@gdcproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).