Yes, I know ... must wait your message

Discussion:

Houder

2018-12-01 14:31:16 UTC

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

Corinna Vinschen

2018-12-01 15:05:30 UTC

Permalink

Post by Houder
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...

Corinna

--
Corinna Vinschen
Cygwin Maintainer

Houder

2018-12-01 15:52:42 UTC

Permalink

Post by Corinna Vinschen

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)

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

Houder

2018-12-01 15:55:13 UTC

Permalink

Post by Houder
Hi Corinna,
Hard work pays off ... (you did it again).

THANK YOU !!!!!

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

Corinna Vinschen

2018-12-01 16:09:12 UTC

Permalink

Post by Houder

Post by Corinna Vinschen

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

Houder

2018-12-01 16:44:41 UTC

Permalink

Post by Corinna Vinschen

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]

Post by Corinna Vinschen
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