On 03/10/2017 11:23 AM, Joseph Myers wrote:
On Fri, 10 Mar 2017, Daniel Santos wrote:
3. Wouldn't it be better to move this logic up into DejaGnu and restrict gcc
to using a black-box interface for modifying the environment?
GCC is meant to work with a wide range of different DejaGnu versions.
On Fri, 10 Mar 2017, Daniel Santos wrote:
> 3. Wouldn't it be better to move this logic up into DejaGnu and restrict gcc
> to using a black-box interface for modifying the environment?
GCC is meant to work with a wide range of different DejaGnu versions.
There would be a long gap between adding
On 10 March 2017 at 06:39, Daniel Santos wrote:
> Hello,
>
> I've been trying to get some clean test results on Cygwin and have
> encountered a number of problems. I've opened a report for the one I'm most
> concerned with (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79867). When an
> executable
Hello,
I've been trying to get some clean test results on Cygwin and have
encountered a number of problems. I've opened a report for the one I'm
most concerned with
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79867). When an executable
is being loaded, Windows searches for dlls based upon
