From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: headache on build repeatibility: octave vs BLODA ?
Date: Wed, 29 Jan 2020 09:44:00 -0000 [thread overview]
Message-ID: <20200129094427.GI3549@calimero.vinschen.de> (raw)
In-Reply-To: <85ddac25-0b4a-5e01-7885-0d2855c37a45@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1594 bytes --]
On Jan 28 07:41, Marco Atzeri wrote:
> Am 27.01.2020 um 12:33 schrieb Takashi Yano:
> > On Mon, 27 Jan 2020 07:45:08 +0100
> > Marco Atzeri wrote:
> > > Can you and Takashi provide me your cygcheck.out so that I can look on
> > > possible difference that could influence the build behaviour.
> >
> > Attached.
> >
>
> Thanks Takashi,
>
> I duplicated your installation from scratch on my W10 Home
> and it fails again in the same place.
>
> So I am now almost sure that the recent MS updates changed/broke
> something in W10 Home. :-((
>
> Assuming it does not break German systems and left immune
> Japanese ones :-?
>
> I will try to install the same in a W10 Pro and if that
> does not segfault I can try the lengthy process to compare
> the object/dll/exec files to see where is the difference.
>
>
> Corinna,
> there are specific code differences in Cygwin DLL between
> W10 Home and Pro ?
Sorry for the late reply, Marco.
No, there are no code differences in Cygwin based on "Home" vs. "Pro"
vs. "Enterprise" editions. Differences are mainly based on Windows
versions, as in W10 1803, W10 1809, etc. Other differences in code
execution are based on workstation vs. server (evaluating scheduling
timing from registry) or stand-alone vs. domain machine (passwd/group
stuff). Of course, even small differences in your setup (Windows
permissions, etc.) may lead to very different code execution.
If you suspect a Cygwin bug, it would be helpful to see an strace
of the crash.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-01-29 9:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 16:55 Marco Atzeri
2020-01-25 18:15 ` Brian Inglis
2020-01-27 6:54 ` Marco Atzeri
2020-01-25 20:36 ` Achim Gratz
2020-01-26 6:58 ` Marco Atzeri
2020-01-26 8:05 ` ASSI
2020-01-26 8:38 ` Marco Atzeri
2020-01-27 6:45 ` Marco Atzeri
2020-01-27 11:33 ` Takashi Yano
2020-01-28 6:41 ` Marco Atzeri
2020-01-28 14:55 ` Takashi Yano
2020-01-29 9:44 ` Corinna Vinschen [this message]
2020-01-29 12:19 ` Marco Atzeri
2020-01-29 13:46 ` Takashi Yano
2020-01-29 15:11 ` Takashi Yano
2020-01-29 15:32 ` Corinna Vinschen
2020-01-29 15:34 ` Corinna Vinschen
2020-01-29 16:08 ` Takashi Yano
2020-01-29 17:57 ` Corinna Vinschen
2020-01-30 21:05 ` Brian Inglis
2020-01-30 21:34 ` Marco Atzeri
2020-01-28 17:26 ` ASSI
2020-01-28 20:04 ` Marco Atzeri
2020-01-28 20:21 ` Achim Gratz
2020-01-26 2:42 ` Takashi Yano
2020-01-26 5:11 ` Takashi Yano
2020-01-26 10:24 ` Marco Atzeri
2020-01-26 10:31 ` Takashi Yano
2020-01-29 0:03 ` Hans-Bernhard Bröker
2020-01-29 0:39 ` Hans-Bernhard Bröker
2020-01-29 5:10 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200129094427.GI3549@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).