From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cpp /usr/include/threads.h fails; modfl segfaults
Date: Mon, 31 Aug 2020 09:33:57 +0200 [thread overview]
Message-ID: <20200831073357.GT3272@calimero.vinschen.de> (raw)
In-Reply-To: <vriumu2cvt1c.fsf@mail.aol.com>
On Aug 30 15:21, airplanemath--- via Cygwin wrote:
> Corinna Vinschen writes:
> > On Aug 29 08:52, airplanemath via Cygwin wrote:
> >> Hello,
> >>
> >> I have two reports. A brief description of the system:
> >> $ uname -a | sed "s/${HOSTNAME}/\${HOSTNAME}/g"
> >> CYGWIN_NT-10.0 ${HOSTNAME} 3.1.7(0.340/5/3) 2020-08-22 17:48 x86_64 Cygwin
> >>
> >> The first report:
> >> [...]
> > I added [C11 threads] functions as wrappers around pthread functionality, code
> > taken from FreeBSD. I ran the glibc testsuite on them, and after fixing
> > the bugs in the glibc testsuite (d'oh), the tests ran successfully.
> >
> The header makes it through the preprocessor for me now. Thank you.
> [...]
> > This is a bug in the assembler code taken from Mingw-w64. The bug has
> > been fixed upstream, so I just pulled in the upstream fixes.
>
> The test program now finishes without segfaulting, and gives the
> expected answer. Thanks again.
> >
> > Thus, both of the above problems should be fixed now. I created a
> > developer snapshot and uploaed it to https://cygwin.com/snapshots/ You
> > need to grab the full tar file and install at least the following files
> > to your installation after backing up the original files from 3.1.7:
> >
> > usr/bin/cygwin1.dll (this is pre-release 3.2.0)
> > usr/lib/libcygwin.a
> > usr/include/limits.h
> > usr/include/pthread.h
> > usr/include/machine/_threads.h
> >
> Is it okay to leave these in place to be overwritten by 3.2.0, or should
> I move the old versions back?
It's ok to leave them in place, just keep in mind that executables
built with this version and using the new symbols won't run under
3.1.7 (e. g., on a collegue's machine).
> > Thanks for the report.
> >
> Thanks for the prompt response.
You're welcome. And thanks for testing!
Corinna
--
Corinna Vinschen
Cygwin Maintainer
next prev parent reply other threads:[~2020-08-31 7:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <02b16d2e-9d51-de58-807b-3b31b2565b59.ref@aol.com>
2020-08-29 12:52 ` airplanemath
2020-08-29 17:57 ` Ken Brown
2020-08-29 21:41 ` [QUAR] " Eliot Moss
2020-08-30 16:11 ` Ken Brown
2020-08-30 18:21 ` Eliot Moss
2020-08-30 1:21 ` airplanemath
2020-08-30 2:56 ` Ken Brown
2020-08-30 6:23 ` ASSI
2020-08-30 20:07 ` Brian Inglis
2020-08-30 13:00 ` Corinna Vinschen
2020-08-30 19:21 ` airplanemath
2020-08-31 7:33 ` Corinna Vinschen [this message]
2020-08-30 20:39 ` Brian Inglis
2020-08-31 7:35 ` Corinna Vinschen
2020-08-31 15:37 ` Brian Inglis
2020-08-31 18:45 ` Corinna Vinschen
2020-08-31 19:24 ` Brian Inglis
2020-08-31 19:41 ` Corinna Vinschen
2020-09-01 17:28 ` Brian Inglis
2020-09-02 7:54 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200831073357.GT3272@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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 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).