Jeremy Drake via Cygwin writes:
> Well, Microsoft's LINK.EXE and LLVM's LLD have already been using these
> new defaults for some time. But I was surprised how quickly my patch was
> accepted/merged.
That was not under dispute in any of the discussions I've seen on this
topic.
> To clarify, defa
On 2021/02/27 18:06, Matt via Cygwin wrote:
Hi maintainers,
Would it be possible to get an updated version of the bash package? The
latest version available for cygwin is 4.4.12-3 which was released in 2017.
There's been at least one major version of bash (5.0) released since then
in January 201
On Sun, 28 Feb 2021, ASSI wrote:
> > Is this still problematic for cygwin?
>
> Yes it is and I'm currently figuring out how to best get rid of it in
> order to be able to update binutils (why this was ever allowed in
> without an accompanying configure option is a mystery to me).
Well, Microsoft'
On Sun, 28 Feb 2021 19:48:28 +0100
Marco Atzeri wrote:
> On 20.02.2021 23:29, Takashi Yano wrote:
> > On Sat, 20 Feb 2021 22:01:38 +0100
> > Marco Atzeri wrote:
> >> MC using latest snapshot 32bit 2021-02-19 (and 2021-02-10)
> >>
> >> now fails at startup with
> >>
> >> Exception: STATUS_ACCESS_VIO
The binutils packages for Cygwin and MingW64 cross-compilation
toolchains have been updated to the upstream feature release 2.36.1.
This is a test release since there are several changes and new features
that either don't work or have not yet been fully tested on Cygwin. In
particular, the new
On 20.02.2021 23:29, Takashi Yano wrote:
On Sat, 20 Feb 2021 22:01:38 +0100
Marco Atzeri wrote:
MC using latest snapshot 32bit 2021-02-19 (and 2021-02-10)
now fails at startup with
Exception: STATUS_ACCESS_VIOLATION at eip=61083736
Thanks for the report. I found the cause of this issue.
I wi
Christoph Reiter via Cygwin writes:
> To clarify: I was referring to non-cygwin targets. I had assumed you
> meant that by "cross compilation toolchain".
Then maybe I don't understand what you meant when you said you've built
MSys2 packages with ASLR on. The MingW-W64 toolchains indeed target
Win
On Sun, Feb 28, 2021 at 3:22 PM ASSI wrote:
>
> Christoph Reiter via Cygwin writes:
> > MSYS2 builds all packages with ASLR since 6 months, so things look
> > good.
>
> That doesn't tell you all that much since you will have to wait for some
> unfavorable address space layout constellation to appe
Christoph Reiter via Cygwin writes:
> MSYS2 builds all packages with ASLR since 6 months, so things look
> good.
That doesn't tell you all that much since you will have to wait for some
unfavorable address space layout constellation to appear for the problem
to announce itself and then you need so
On Sun, Feb 28, 2021 at 1:16 PM ASSI wrote:
>
> Christoph Reiter via Cygwin writes:
> > binutils 2.36 now defaults to ASLR etc on Windows, so a cygwin compiled
> > linker
> > will give you:
> >
> >> peflags -v mydll.dll
> > mydll.dll: coff(0x2026[+executable_image,+line_nums_stripped,+bigaddr,+dl
Christoph Reiter via Cygwin writes:
> binutils 2.36 now defaults to ASLR etc on Windows, so a cygwin compiled linker
> will give you:
>
>> peflags -v mydll.dll
> mydll.dll: coff(0x2026[+executable_image,+line_nums_stripped,+bigaddr,+dll])
> pe(0x0160[+high-entropy-va,+dynamicbase,+nxcompat])
>
> Is
Hey,
binutils 2.36 now defaults to ASLR etc on Windows, so a cygwin compiled linker
will give you:
> peflags -v mydll.dll
mydll.dll: coff(0x2026[+executable_image,+line_nums_stripped,+bigaddr,+dll])
pe(0x0160[+high-entropy-va,+dynamicbase,+nxcompat])
Is this still problematic for cygwin?
The re
Hi,
I am new to the concept of configuring crosscompiler from GCC , can anyone
guide me on how to create/ Configure a cross compiler from GCC compiler for ARM
cortex M4F using Cygwin. I am using a windows 10 PC, my target is arm cortexM4F
TM4C129ENCPDT and I am using it as bareboard (no OS).
13 matches
Mail list logo
