On 08.04.2025 09:56, Roger Pau Monné wrote:
> On Mon, Apr 07, 2025 at 04:04:18PM +0200, Jan Beulich wrote:
>> On 01.04.2025 15:26, Roger Pau Monné wrote:
>>> nxcompat should be enabled by default I think? I can of course make
>>> it explicit by adding to the PE link command line.
>>
>> --nxcompat
On Mon, Apr 07, 2025 at 04:04:18PM +0200, Jan Beulich wrote:
> On 01.04.2025 15:26, Roger Pau Monné wrote:
> > nxcompat should be enabled by default I think? I can of course make
> > it explicit by adding to the PE link command line.
>
> --nxcompat wasn't the default originally, then was made the
On 01.04.2025 15:26, Roger Pau Monné wrote:
> nxcompat should be enabled by default I think? I can of course make
> it explicit by adding to the PE link command line.
--nxcompat wasn't the default originally, then was made the default for MinGW
(and by mistake for everything else as well), then i
On 01.04.2025 15:26, Roger Pau Monné wrote:
> On Tue, Apr 01, 2025 at 03:13:52PM +0200, Jan Beulich wrote:
>> On 01.04.2025 15:08, Roger Pau Monne wrote:
>>> Hello,
>>>
>>> The following series aim to remove the presence of any write and execute
>>> section in the PE Xen image. This is required to
On Tue, Apr 01, 2025 at 03:13:52PM +0200, Jan Beulich wrote:
> On 01.04.2025 15:08, Roger Pau Monne wrote:
> > Hello,
> >
> > The following series aim to remove the presence of any write and execute
> > section in the PE Xen image. This is required to support the NX
> > compatible flag in the PE
On 01.04.2025 15:08, Roger Pau Monne wrote:
> Hello,
>
> The following series aim to remove the presence of any write and execute
> section in the PE Xen image. This is required to support the NX
> compatible flag in the PE header. By the end of the series the
> resulting PE image has no reloca
