GNU bug report logs - #50666
28.0.50; Fix native compilation on Cygwin

Previous Next

Full log

Message #67 received at 50666 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ken Brown <kbrown <at> cornell.edu>
Cc: Stromeko <at> nexgo.de, 50666 <at> debbugs.gnu.org, akrl <at> sdf.org
Subject: Re: bug#50666: 28.0.50; Fix native compilation on Cygwin
Date: Thu, 23 Sep 2021 20:29:20 +0300

> Cc: akrl <at> sdf.org, Stromeko <at> nexgo.de, 50666 <at> debbugs.gnu.org
> From: Ken Brown <kbrown <at> cornell.edu>
> Date: Thu, 23 Sep 2021 13:13:05 -0400
> 
> > My point is that maybe we should make that decision already, before
> > burning too much time and energy on it.
> 
> You might be right.  I wasn't aware of all the complications you mentioned above.

It took us most of the last year to realize how tricky this stuff is.
We are still learning ;-)

> We still need to do something for 64-bit Cygwin.  Even though address collisions 
> are unlikely they could still happen theoretically.  But there might be a much 
> easier solution that doesn't necessarily require rebasing.  For example, Achim 
> mentioned earlier the possibility of marking the eln as ASLR w/ high-entropy and
> large address aware.

Isn't that the default of the 64-bit GNU ld on Windows?  Or does
Cygwin configure Binutils differently from MinGW?

If not, we can use native-comp-driver-options, by giving it a non-nil
value for Cygwin, to force this.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.