From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Yes, I know ... must wait your message
Date: Sat, 01 Dec 2018 16:09:00 -0000 [thread overview]
Message-ID: <20181201160912.GT30649@calimero.vinschen.de> (raw)
In-Reply-To: <b3161f9ecea4b12dc785cdabedd03412@xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1791 bytes --]
On Dec 1 16:52, Houder wrote:
> On 2018-12-01 16:05, Corinna Vinschen wrote:
> > On Dec 1 15:31, Houder wrote:
> > > Hi Corinna,
> > >
> > > Hard work pays off ... (you did it again).
> > >
> > > 64 LANG = en_US.utf-8, LC_ALL =
> > > => LANG = en_US.utf-8
> > > PATH (64) = /usr/local/bin:/usr/bin:/drv/c/...
> > > LET OP: v2.12.0 of cygwin1.dll
> > > /ext/build/mknetrel/src/cygwin-snapshot-20181201-1/winsup/cygwin/cygheap.cc
> > > 64-%% uname -a
> > > CYGWIN_NT-6.1 Seven 2.12.0(0.330/5/3) x86_64 Cygwin
> >
> > Hmm, ok. First I thought this is a problem with the new clock, but in
> > fact the timestamp is generated at build time and I'm building on Linux.
> >
> > I can't reproduce this with a local build, so it must be something
> > in terms of the DLL being build for a snapshot DLL, hmm...
>
> Huh?
>
> Hi Corinna,
>
> I had to get out in a hurry ... so I did not see your reply to my clumsy
> message ...
>
> I was studying the text of your latest commit ... and thought: "Well, if
> that is the case ..."
>
> I changed over to the "snapshot page" and it changed in front of my eyes.
>
> So, in a hurry I downloaded the tarball, replaced the cygwin1.dll in my
> test setup and posted my finding ...
>
> Sorry. I wanted you to know that it worked on W7 ...
>
> No problems yet ...
>
> Henri
>
> P.S. are you referring to string? (plural). That is me! (.bash_profile)
I'm referring to the missing date in uname -a (aka uname -v).
Apparently this is a long-standing problem (2.5 yrs) in the script
creating the version information when building a snapshot. I uploaded
YA snapshot to https://cygwin.com/snapshots/ which should be back to a
valid date info.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-01 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 14:31 Houder
2018-12-01 15:05 ` Corinna Vinschen
2018-12-01 15:52 ` Houder
2018-12-01 15:55 ` Houder
2018-12-01 16:09 ` Corinna Vinschen [this message]
2018-12-01 16:44 ` Houder
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=20181201160912.GT30649@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).