On 2019-08-18 08:51, Denis Excoffier wrote:
> In the GCC 10 Release Criteria, one can read
> (https://gcc.gnu.org/gcc-10/criteria.html) that cygwin is among the
> secondary platform list:
>> Secondary Platform List
>>
>> The secondary platforms are:
>> * aarch64-elf
>> * i686-apple-darwin
>> *
The following Perl distributions have been updated to their latest
version on CPAN, respectively:
x86/x86_64
--
perl-DBD-SQLite-1.64-1
perl-Scalar-List-Utils-1.52-1
perl-Unicode-Normalize-1.26-1 (test)
noarch
--
perl-DateTime-Calendar-Julian-0.101-1
perl-Mojolicious-8.23-1
The following Perl distributions have been updated to their latest
version on CPAN, respectively:
x86/x86_64
--
perl-DBD-SQLite-1.64-1
perl-Scalar-List-Utils-1.52-1
perl-Unicode-Normalize-1.26-1 (test)
noarch
--
perl-DateTime-Calendar-Julian-0.101-1
perl-Mojolicious-8.23-1
On 18/08/2019 13.57, Corinna Vinschen wrote:
Nope, Cygwin uses the Windows loader.
Then, how do you do the extra linking? What is producing the "Cygwin
runtime failure" message when loading/linking a DLL fails?
If the medium model is wasteful in clang, that's a clang
optimization
On 8/18/2019 8:08 AM, Achim Gratz wrote:
> Ken Brown writes:
>> If you can get to it within the next few days, that would be great. If not,
>> I
>> can just install it from CPAN temporarily for the purpose of building the
>> packed
>> archive.
>
> I've uploaded it as a test package for both
Hello,
In the GCC 10 Release Criteria, one can read
(https://gcc.gnu.org/gcc-10/criteria.html) that cygwin is among the secondary
platform list:
>
> Secondary Platform List
>
> The secondary platforms are:
> * aarch64-elf
> * i686-apple-darwin
> * i686-pc-cygwin
> * i686-mingw32
> *
Corinna Vinschen writes:
> There's no xlocale.h on Linux either. What do these packages do in
> that case?
I've dug a little bit deeper. The trouble is that perl.h has picked up
xlocale.h as the location of some of the interfaces it wants to use
during configuration, so that means you can't
On Aug 18 14:06, Achim Gratz wrote:
> Corinna Vinschen writes:
> > - Eliminate a header file name collision with on case
> > insensitive filesystems by reverting back to .
>
> What's the suggested way to deal with software that expects to be able
> to "#include "? I think I'll see that more
Ken Brown writes:
> If you can get to it within the next few days, that would be great. If not,
> I
> can just install it from CPAN temporarily for the purpose of building the
> packed
> archive.
I've uploaded it as a test package for both architectures.
perl-Unicode-Normalize-1.26-1
Corinna Vinschen writes:
> - Eliminate a header file name collision with on case
> insensitive filesystems by reverting back to .
What's the suggested way to deal with software that expects to be able
to "#include "? I think I'll see that more often than X11
applications that have their
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=7097b05eda2f8e9058eab4fda8dedacdfb7ffd7f
commit 7097b05eda2f8e9058eab4fda8dedacdfb7ffd7f
Author: Corinna Vinschen
Date: Fri Aug 16 16:36:06 2019 +0200
Cygwin: select: revamp non-polling code for signalfd
Rather than
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=b7399d5e6f8ad5b15cd725f66b3e49732393ef03
commit b7399d5e6f8ad5b15cd725f66b3e49732393ef03
Author: Corinna Vinschen
Date: Fri Aug 16 16:36:20 2019 +0200
Revert "Cygwin: fix potential SEGV in sigwaitinfo/signalfd scenario"
On Aug 18 01:43, Takashi Yano wrote:
> Hi Corinna,
>
> On Fri, 16 Aug 2019 16:48:11 +0200
> Corinna Vinschen wrote:
> > I now had an idea, but I'm not entirely sure if it's the right thing to
> > do. Can you please test this? It consists of two patches, one with the
> > revamped signalfd
On Aug 18 08:04, Agner Fog wrote:
> Thanks a lot for your help in clarifying this.
>
> When I complained here about the wasteful 64-bit addresses you said that it
> was an LLVM issue.
I never said anything like that. The issue is that your clang
linux->cygwin cross compiler uses the wrong
Version 12 of "engauge-digitizer" has been uploaded.
Interactively converts a bitmap graph or map into numbers.
Changes:
* More point styles
* Fix export issue with log scale data and small step values
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the
Version 12 of "engauge-digitizer" has been uploaded.
Interactively converts a bitmap graph or map into numbers.
Changes:
* More point styles
* Fix export issue with log scale data and small step values
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the
Thanks a lot for your help in clarifying this.
When I complained here about the wasteful 64-bit addresses you said that
it was an LLVM issue. When I complained to LLVM they said it was a
Cygwin issue, and that you were using the wrong memory model.
All this confusion is due to a terrible
17 matches
Mail list logo
