public inbox for developer@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Jonathan Perkin <jperkin@mnx.io>
To: illumos-developer <developer@lists.illumos.org>
Subject: Recent GCC improvements
Date: Wed, 22 May 2024 12:56:13 +0100	[thread overview]
Message-ID: <Zk3dXdrYhRAq1LLR@mnx.io> (raw)

Hi,

Rich encouraged me to ping the list about a couple of GCC fixes I've 
recently worked on.  I'm reasonably confident that they would be useful 
for other distributions to pick up, and perhaps eventually make their 
way upstream.

First, this fix for __STDC_VERSION__ being defined in C++ code:

   https://github.com/jperkin/notes/blob/main/gcc-cpp-stdc/README.md

This fixes at least one third-party package (scipy), and probably others 
that depend on cython.  I also have memories of fixing this manually in 
third party code in the past, so it's likely some other upstream issues 
are being masked.

Secondly, this fix for C++ locale support:

   https://github.com/jperkin/notes/blob/main/gcc-cpp-locale/README.md

This fixes crashes in mkvmerge when using anything other than a "C" 
locale, and likely other software written in C++ that uses similar 
interfaces.

For the second fix in particular it would be good if those familiar with 
the locale support in illumos could take a look at any support we're 
missing.  I noticed the lack of localeconv_l(), hence why LC_MONETARY 
and LC_NUMERIC are not yet supported, but there may be others.

Cheers,

-- 
Jonathan Perkin   -   mnx.io   -   pkgsrc.smartos.org
Open Source Complete Cloud   www.tritondatacenter.com

             reply	other threads:[~2024-05-22 11:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 11:56 Jonathan Perkin [this message]
2024-05-22 15:06 ` [developer] " Alan Coopersmith
2024-05-22 15:58 ` Robert Mustacchi
2024-05-22 16:21   ` Jonathan Perkin
2024-05-24 12:32 ` Jonathan Perkin

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=Zk3dXdrYhRAq1LLR@mnx.io \
    --to=jperkin@mnx.io \
    --cc=developer@lists.illumos.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 NNTP newsgroup(s).