Re: Yes, I know ... must wait your message

[Houder <houder at xs4all dot nl>]

On 2018-12-01 17:09, Corinna Vinschen wrote:
> 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?
[snip]

> 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.

Got it.

Repeated procedure ...

/ext/build/mknetrel/src/cygwin-snapshot-20181201-1/winsup/cygwin/cygheap.cc
64-%% uname -v
2018-12-01 16:02
64-%% uname -a
CYGWIN_NT-6.1 Seven 2.12.0s(0.330/5/3) 2018-12-01 16:02 x86_64 Cygwin
64-%%

Henri

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple