From: Corinna Vinschen <vinschen@redhat.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org, Reuben Thomas <rrt@sc3d.org>
Subject: Re: [PATCH] Do not decorate symbols as dllexport on Cygwin
Date: Mon, 6 Feb 2023 21:43:27 +0100 [thread overview]
Message-ID: <Y+Fmb56fK7PN8Ndo@calimero.vinschen.de> (raw)
In-Reply-To: <3099885.Repjz8aVax@nimes>
On Feb 6 21:38, Bruno Haible wrote:
> Corinna Vinschen wrote:
> > I just ran the setlocale_null-mt-* tests with gnulib from git master
> > under Cygwin with my newlib patch, and the tests succeeded. I checked
> > that configure is doing the right thing and config.h contains the right
> > settings:
> >
> > $ ./configure
> > [...]
> > checking whether setlocale (LC_ALL, NULL) is multithread-safe... yes
> > checking whether setlocale (category, NULL) is multithread-safe... yes
> > [...]
> > $ grep SETLOCALE_NULL config.h
> > #define GNULIB_TEST_SETLOCALE_NULL 1
> > #define SETLOCALE_NULL_ALL_MTSAFE 1
> > #define SETLOCALE_NULL_ONE_MTSAFE 1
> > $ grep SETLOCALE_NULL gltests/config.h
> > #define GNULIB_TEST_SETLOCALE_NULL 1
> > #define SETLOCALE_NULL_ALL_MTSAFE 1
> > #define SETLOCALE_NULL_ONE_MTSAFE 1
>
> Excellent! Thank you.
>
> The lasts remaining steps, to resolve the issue, are (as far as I see it):
> 1. 'recode' is updated to a current gnulib and publish a corresponding
> tarball. (Hi Reuben :) )
> 2. Then the Cygwin program packagers build this tarball on a Cygwin of
> version ≥ 3.4.6.
Incidentally I'm the maintainer of the recode package in the Cygwin distro
and I built 3.7.12 (as in Fedora 37) with -Wl,--export-all-symbols, which
also does the trick for now.
Thanks,
Corinna
next prev parent reply other threads:[~2023-02-06 20:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 19:43 [PATCH] Do not decorate symbols as dllexport on Cygwin Corinna Vinschen
2023-02-05 20:41 ` Bruno Haible
2023-02-05 20:48 ` Bruno Haible
2023-02-05 21:22 ` Corinna Vinschen
2023-02-06 15:08 ` Corinna Vinschen
2023-02-06 16:36 ` Bruno Haible
2023-02-06 17:37 ` Bruno Haible
2023-02-06 20:04 ` Corinna Vinschen
2023-02-06 20:38 ` Bruno Haible
2023-02-06 20:43 ` Corinna Vinschen [this message]
2023-02-06 20:50 ` Reuben Thomas
2023-02-07 13:22 ` Corinna Vinschen
2023-02-07 15:22 ` Corinna Vinschen
2023-02-10 14:11 ` Reuben Thomas
2023-02-10 14:21 ` Bruno Haible
2023-02-11 11:36 ` Reuben Thomas
2023-02-11 12:06 ` Corinna Vinschen
2023-02-11 12:29 ` Reuben Thomas
2023-02-11 12:40 ` Corinna Vinschen
2023-02-17 9:30 ` Reuben Thomas
2023-02-17 9:58 ` Corinna Vinschen
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+Fmb56fK7PN8Ndo@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=rrt@sc3d.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).