Hi, Perhaps someone who knows can confirm that I've got this right:
The executables in a Cygwin download can be much older than the download date, where "much" > 3 years. This suggests that executables are only rebuilt when their own sources change. Previously built executables can continue to be bundled into downloadable packages, even if the version of gcc in the download is much newer. Therefore, it is not reasonable to attempt to rebuild the executables in a download using the sources and gcc in the same download, and expect an *exact* reconstruction. (And that's before thinking about the compilation date strings that end up in the executables, or the CFLAGS arguments to the various configure scripts which also aren't necessarily obvious.) If I know an exact rebuild isn't possible, I won't try to achieve it before kludging the source :-) TIA, Alan Carter ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/