On Mon, Oct 02, 2000 at 02:24:12PM -0700, Mike Smith wrote:
>
> The build was silently broken by AMD including previously.
> It wasn't exposed until recently. The correct fix was still to not
> include anywhere in AMD (or anywhere else in userland for
> that matter).
Yes I know. I was tr
The build was silently broken by AMD including previously.
It wasn't exposed until recently. The correct fix was still to not
include anywhere in AMD (or anywhere else in userland for
that matter).
> On Sun, Oct 01, 2000 at 12:14:25PM -0700, Mike Smith wrote:
> > Er, this is probably the
On Sun, Oct 01, 2000 at 12:14:25PM -0700, Mike Smith wrote:
> Er, this is probably the wrong fix. It sounds like the kernel 'callout'
> structure is ending up visible in userland, which it shouldn't.
The build was broken by the inclusion of in
sys/sys/mbuf.h rev 1.56. includes sys/sys/proc.h
> "WL" == Warner Losh <[EMAIL PROTECTED]> writes:
WL> this is an *UN*acceptible attitude. CHOI-san is reporting a
-san is Japanese word, and I am Korean. Due to historical reason, most
Korean do not want to be treated as Japanese and most of them will be
angry. Please don't call me 'CHO
This is better than watching the soaps. I'll be waiting anxiously for
the next installment. ;<)
On Sun, 1 Oct 2000 12:47:16 -0700, "David O'Brien" <[EMAIL PROTECTED]> said:
> On Sun, Oct 01, 2000 at 12:14:25PM -0700, Mike Smith wrote:
>> > > I hate to spoil the moment ... but does anyone
On Sun, Oct 01, 2000 at 12:14:25PM -0700, Mike Smith wrote:
> > > I hate to spoil the moment ... but does anyone have an idea what the
> > > fix is? Nothing in the amd directory seems to have changed in the
> > > past couple of weeks, so it must be somewhere else, and I'm not bright
> > > enough
> 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 le
Mike Smith <[EMAIL PROTECTED]> wrote:
> > > I hate to spoil the moment ... but does anyone have an idea what the
> > > fix is? Nothing in the amd directory seems to have changed in the
> > > past couple of weeks, so it must be somewhere else, and I'm not bright
> > > enough to figure out where.
>
> > I hate to spoil the moment ... but does anyone have an idea what the
> > fix is? Nothing in the amd directory seems to have changed in the
> > past couple of weeks, so it must be somewhere else, and I'm not bright
> > enough to figure out where.
>
> Yeah, somebody forgot that typedefs and st
> I hate to spoil the moment ... but does anyone have an idea what the
> fix is? Nothing in the amd directory seems to have changed in the
> past couple of weeks, so it must be somewhere else, and I'm not bright
> enough to figure out where.
Yeah, somebody forgot that typedefs and structure name
On Sun, 01 Oct 2000 11:35:32 -0600, Warner Losh <[EMAIL PROTECTED]> said:
> Tony, this is an *UN*acceptible attitude. CHOI-san is reporting
> a problem. He didn't rail against anything, nor did he demand a
> fix. This is 100% acceptible. Your message, however, was rude
> and inapp
In message <[EMAIL PROTECTED]> "Tony Johnson" writes:
: Run 4.0 or piss off...
Tony,
this is an *UN*acceptible attitude. CHOI-san is reporting a
problem. He didn't rail against anything, nor did he demand a fix.
This is 100% acceptible. Your message, however, was rude and
inappropriate
At 1 Oct 2000 04:24:14 GMT,
CHOI Junho <[EMAIL PROTECTED]> wrote:
> I have cvsup'ed today, build stopped with the following error:
I got same one, reported by my nightly buildworld failure. I think
this happened between 9/30 00:00 JST and 10/1 00:00 JST...
--
Jun Kuriyama <[EMAIL PROTECTED]>
> Run 4.0 or piss off...
That's totally inappropriate. He's reporting a BUILD ERROR which is
an occasional fact of life in -current and should be reported so that
whomever broke AMD can go fix the build. He's also a developer of
FreeBSD and simply reporting this to the other developers.
I'm ge
On Sun, Oct 01, 2000 at 12:20:04AM -0500, Tony Johnson wrote:
> Run 4.0 or piss off...
Tony, I suggest you apologise to Mr Choi for this extremely insulting
message.
Kris
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECTED]>
To Unsubsc
> Run 4.0 or piss off...
Actually, no. This message contains useful diagnostic information, and
can be used to resolve the problem.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of CHOI Junho
> Sent: Saturday, September 30, 2000 11:22 PM
> To: [EM
Run 4.0 or piss off...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of CHOI Junho
Sent: Saturday, September 30, 2000 11:22 PM
To: [EMAIL PROTECTED]
Subject: Today -current broken on build
I have cvsup'ed today, build stopped with the following error:
17 matches
Mail list logo
