Re: All clear [was Re: [1.7]: For the love of god, don't update!]

2009-04-07 Thread Dave Korn
Christopher Faylor wrote: > We don't programatically hexedit the static libraries. That was the > whole point of my speclib rewrite. The libraries are generated using > dlltool. Sorry, I tested the new one without reading it and didn't realise to what extent you had rewritten it. > If that's

Re: All clear [was Re: [1.7]: For the love of god, don't update!]

2009-04-07 Thread Christopher Faylor
On Tue, Apr 07, 2009 at 12:31:29PM +0100, Dave Korn wrote: >Corinna Vinschen wrote: >> On Apr 7 00:12, Dave Korn wrote: >>>Grepping through library symbols seems quite fragile when so many >>>standard C library functions are permitted to be implemented as macros. >> >>I assume they use nm rather t

Re: All clear [was Re: [1.7]: For the love of god, don't update!]

2009-04-07 Thread Dave Korn
Corinna Vinschen wrote: > On Apr 7 00:12, Dave Korn wrote: >> Grepping through library symbols seems quite >> fragile when so many standard C library functions are permitted to be >> implemented as macros. > > I assume they use nm rather than grep. Sorry, I was just using the term in the exte

Re: All clear [was Re: [1.7]: For the love of god, don't update!]

2009-04-07 Thread Corinna Vinschen
On Apr 7 00:12, Dave Korn wrote: > Christopher Faylor wrote: > > On Mon, Apr 06, 2009 at 08:08:33PM +0200, Corinna Vinschen wrote: > >> On Apr 6 13:33, Christopher Faylor wrote: > >>> On Mon, Apr 06, 2009 at 06:29:43PM +0200, Corinna Vinschen wrote: > Wouldn't it help if libc.a, libm.a etc.

Re: All clear [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Dave Korn
Christopher Faylor wrote: > On Mon, Apr 06, 2009 at 08:08:33PM +0200, Corinna Vinschen wrote: >> On Apr 6 13:33, Christopher Faylor wrote: >>> On Mon, Apr 06, 2009 at 06:29:43PM +0200, Corinna Vinschen wrote: Wouldn't it help if libc.a, libm.a etc. wouldn't export any symbols at all? I

Re: All clear [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Christopher Faylor
On Mon, Apr 06, 2009 at 08:08:33PM +0200, Corinna Vinschen wrote: >On Apr 6 13:33, Christopher Faylor wrote: >> On Mon, Apr 06, 2009 at 06:29:43PM +0200, Corinna Vinschen wrote: >> >Wouldn't it help if libc.a, libm.a etc. wouldn't export any symbols at >> >all? I mean, eventually there's libcygwi

Re: All clear [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Corinna Vinschen
On Apr 6 13:33, Christopher Faylor wrote: > On Mon, Apr 06, 2009 at 06:29:43PM +0200, Corinna Vinschen wrote: > >Wouldn't it help if libc.a, libm.a etc. wouldn't export any symbols at > >all? I mean, eventually there's libcygwin.a linked in which satisfies > >all of the requested symbols. What w

Re: All clear [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Christopher Faylor
On Mon, Apr 06, 2009 at 06:29:43PM +0200, Corinna Vinschen wrote: >Wouldn't it help if libc.a, libm.a etc. wouldn't export any symbols at >all? I mean, eventually there's libcygwin.a linked in which satisfies >all of the requested symbols. What would break if the secondary libs >pointing to cygwi

Re: All clear [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Corinna Vinschen
On Apr 6 16:48, Dave Korn wrote: > Christopher Faylor wrote: > > On Mon, Apr 06, 2009 at 03:21:26PM +0100, Dave Korn wrote: > >> ...Both exes have an IAT from kernel32 importing GetACP and Get > >> ModuleHandleA, and two single-entry IATs referencing _impure_ptr > >> (auto-import entries, pointing

Re: All clear [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Dave Korn
Christopher Faylor wrote: > On Mon, Apr 06, 2009 at 03:21:26PM +0100, Dave Korn wrote: >> So, that's why only some applications manifest this problem; it's only >> the ones that explicitly pass -lc in their LDFLAGS. > > So, given how limited the problem is, I don't think the alarmist Subject > was

Re: Reverting from 1.7.0-45 [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Dave Korn
Corinna Vinschen wrote: > On Apr 6 09:03, Charles Wilson wrote: >> Dave Korn wrote: >>> LOLWUT? It turns out something has gone horribly wrong in the >>> alternatives >>> department now: >>> [...] >> Actually, from Corinna's reply, it appears that, in addition to >> reverting *alternatives* be

Re: Reverting from 1.7.0-45 [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Dave Korn
Charles Wilson wrote: > So, IIUC, alternatives-1.3.30c-10 isn't *itself* actually broken, right? No, I didn't mean the package is broken, just that the alternatives themselves, i.e. the symlinks, were wrong. cheers, DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe

Re: All clear [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Christopher Faylor
On Mon, Apr 06, 2009 at 03:21:26PM +0100, Dave Korn wrote: >So, that's why only some applications manifest this problem; it's only >the ones that explicitly pass -lc in their LDFLAGS. So, given how limited the problem is, I don't think the alarmist Subject was really called for. Anyone reading th

All clear [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Dave Korn
Dave Korn wrote: > Hi all, > > [ re: ... don't update! ] > > Or at least, not without taking a backup of your Cygwin installation > first Right, panic over. If you do need to revert, it is possible, as long as you remember to take m4 and alternatives along for the ride. (Also any other

Re: Reverting from 1.7.0-45 [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Corinna Vinschen
On Apr 6 09:03, Charles Wilson wrote: > Dave Korn wrote: > > LOLWUT? It turns out something has gone horribly wrong in the > > alternatives > > department now: > > [...] > > Actually, from Corinna's reply, it appears that, in addition to > reverting *alternatives* because of the dependence th

Re: Reverting from 1.7.0-45 [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Corinna Vinschen
On Apr 6 09:06, Charles Wilson wrote: > Corinna Vinschen wrote: > > > However, just before the application's main() is called, the locale is > > set back to "C", see > > http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/dcrt0.cc.diff?r1=1.352&r2=1.353&cvsroot=src&f=h > > Hmm. "before main()

Re: Reverting from 1.7.0-45 [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Charles Wilson
Corinna Vinschen wrote: > However, just before the application's main() is called, the locale is > set back to "C", see > http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/dcrt0.cc.diff?r1=1.352&r2=1.353&cvsroot=src&f=h Hmm. "before main()" huh? Is that *before*, or *after*, C++ static init

Re: Reverting from 1.7.0-45 [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Charles Wilson
Dave Korn wrote: > LOLWUT? It turns out something has gone horribly wrong in the alternatives > department now: > > $ gcc > bash: gcc: command not found > > $ gcc.exe > bash: gcc.exe: command not found > > $ file /bin/gcc.exe > /bin/gcc.exe: broken symbolic link to `/etc/alternatives/gcc' >

Re: Reverting from 1.7.0-45 [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Corinna Vinschen
On Apr 6 05:56, Eric Blake wrote: > According to Dave Korn on 4/6/2009 3:08 AM: > > I wonder if m4 suddenly changed its behaviour as a result of now being > > locale sensitive, which had knock-on effects on autoconf and bison, which > > causes the trouble by doing something unexpected when gener

Re: Reverting from 1.7.0-45 [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Dave Korn on 4/6/2009 3:08 AM: > I wonder if m4 suddenly changed its behaviour as a result of now being > locale sensitive, which had knock-on effects on autoconf and bison, which > causes the trouble by doing something unexpected when g

Re: Reverting from 1.7.0-45 [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Dave Korn
Corinna Vinschen wrote: > This happens if the symlink has been created with Cygwin 1.7.0-45 > and you revert back to 1.7.0-44 or earlier. Yeh, it all went quiet for a while while I've been re-reading the recent release announcements. Thanks for the pointers. > I explained what I did to new sy

Re: Reverting from 1.7.0-45 [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Corinna Vinschen
On Apr 6 10:08, Dave Korn wrote: > Charles Wilson wrote: > > Dave Korn wrote: > > > >> Forgot to say... can I see your "cygcheck -cd"? I would have said "just > >> m4 > >> and cygwin", but maybe it's related to something else. > > > > Attached. FWIW, I had no problems building other things,

Reverting from 1.7.0-45 [was Re: [1.7]: For the love of god, don't update!]

2009-04-06 Thread Dave Korn
Charles Wilson wrote: > Dave Korn wrote: > >> Forgot to say... can I see your "cygcheck -cd"? I would have said "just m4 >> and cygwin", but maybe it's related to something else. > > Attached. FWIW, I had no problems building other things, like > yesterday's p7zip packages or today's alternat

AVG7 users beware false positives this morning [ was Re: [1.7]: For the love of god, don't update! ]

2009-04-06 Thread Dave Korn
Dave Korn wrote: > I'm about to use the time machine to install a completely fresh cygwin in a > vm. Maybe that'll get things moving again. Of ALL the times for AVG to suddenly start misdetecting "conftest.exe" as "Trojan Horse Generic2.ITN" ... this was not the best moment for it to pick. :

Re: [1.7]: For the love of god, don't update!

2009-04-06 Thread Dave Korn
Charles Wilson wrote: > Dave Korn wrote: > >> Forgot to say... can I see your "cygcheck -cd"? I would have said "just m4 >> and cygwin", but maybe it's related to something else. > > Attached. FWIW, I had no problems building other things, like > yesterday's p7zip packages or today's alternat

Re: [1.7]: For the love of god, don't update!

2009-04-05 Thread Charles Wilson
Dave Korn wrote: > Forgot to say... can I see your "cygcheck -cd"? I would have said "just m4 > and cygwin", but maybe it's related to something else. Attached. FWIW, I had no problems building other things, like yesterday's p7zip packages or today's alternatives packages. -- Chuck Cygwin P

Re: [1.7]: For the love of god, don't update!

2009-04-05 Thread Dave Korn
Dave Korn wrote: > Charles Wilson wrote: >> Dave Korn wrote: >> >>> Q2) Has anyone out there /not/ updated today, and also has a checkout of >>> CVS >>> binutils they could try building and testing? >>> >>> In either case:- >>> >>> If you get six fails, that's probably the bug I have here. >>

Re: [1.7]: For the love of god, don't update!

2009-04-05 Thread Dave Korn
Charles Wilson wrote: > Dave Korn wrote: > >> Q2) Has anyone out there /not/ updated today, and also has a checkout of CVS >> binutils they could try building and testing? >> >> In either case:- >> >> If you get six fails, that's probably the bug I have here. > > I got six fails. :-/ Tha

Re: [1.7]: For the love of god, don't update!

2009-04-05 Thread Charles Wilson
Dave Korn wrote: > Q2) Has anyone out there /not/ updated today, and also has a checkout of CVS > binutils they could try building and testing? > > In either case:- > > If you get six fails, that's probably the bug I have here. I got six fails. -- Chuck -- Unsubscribe info: http://c

[1.7]: For the love of god, don't update!

2009-04-05 Thread Dave Korn
Hi all, [ re: ... don't update! ] Or at least, not without taking a backup of your Cygwin installation first, at any rate the system-related parts (/bin /usr/lib /usr/include and who knows if maybe more?), at least until we figure out whether everyone else is going to have the same utter n