This is the mail archive of the cygwin-patches mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Feb 12 10:53, Yaakov Selkowitz wrote: > On 2016-02-12 03:33, Corinna Vinschen wrote: > >On Feb 11 20:38, Yaakov Selkowitz wrote: > >> winsup/cygwin/ > >> * child_info.h (CURR_CHILD_INFO_MAGIC): Update. > > > >This needs an explanation. CHILD_INFO_MAGIC is still 0x30ea98f6U > >for me. > > Hmmm, in that case it's either one of the patches I just sent or it's gcc-5. > How would either of those affect this? Off the top of my head, I don't know. Usually only a change to child_info.h should affect CHILD_INFO_MAGIC. Unless the preprocessed output of gcc differs for some reason. You might want to compare the output of gcc4 vs. gcc5 when called from cygmagic. In general it doesn't make sense if an identical structure definition results in different checksums dependent on the compiler. If push comes to shove we have to change the cygmagic script to make sure the output fed to cksum is independent on the compiler used (which I though it is, oh well). Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
Attachment:
signature.asc
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |