> Er, this is probably the wrong fix. It sounds like the kernel 'callout' > structure is ending up visible in userland, which it shouldn't. It wasn't clear to me if it was clashing with the internal typedef or something else - the namespace issues with gcc are a little unclear to me here (at least it's not VMS C, with a global member name space :). In any case, we can certainly revert the change if it transpires that the pollution came from elsewhere and for now, at least, -current is working again. clock.c includes a butt-load of system headers through am_defs.h and I can't immediately tell if the callout stuff is being exposed inappropriately or not. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Today -current broken on build CHOI Junho
- RE: Today -current broken on build Tony Johnson
- Re: Today -current broken on build Mike Smith
- Re: Today -current broken on build Kris Kennaway
- Re: Today -current broken on build Jordan Hubbard
- Re: Today -current broken on build Warner Losh
- Re: Today -current broken on build Michael Harnois
- Re: Today -current broken on build Jordan Hubbard
- Re: Today -current broken on build Mike Smith
- Re: Today -current broken on bu... Brian F. Feldman
- Re: Today -current broken on bu... Jordan Hubbard
- Re: Today -current broken on bu... David O'Brien
- Re: Today -current broken o... Michael Harnois
- Re: Today -current broken on bu... David O'Brien
- Re: Today -current broken on build CHOI Junho
- Re: Today -current broken on build Jun Kuriyama
- Re: Today -current broken on build Mike Smith
- Re: Today -current broken on build David O'Brien