search for: gracelessly

Recent BK kernels break the klibc build, because of proliferating use of u8, u16, and friends. The particular offender in this case is include/asm/system.h, which uses u8 in the new alt_instr struct. This patch "fixes" the breakage, albeit gracelessly. I'm agnostic on whether it's the Right Thing. It might be saner to simply have a series of definitions, of the form: typedef __u8 u8; However, this is prone to creeping breakage as the kernel leaks more data types into klibc's view. <b -------------- next part -------------- -...

I have build asterisk from latest CVS HEAD-05/09/05 with H323 support as described in README file. Open H.323 version v1.17.1 and PWLib v1.9.0 on Mandrake Linux 10.2 kernel-2.6.11 I tested it with following phones: -- XLite (SIP softphone) -- QMix SIP IP phone (PA168F) -- SJPhone (H323 softphone) -- QMix H323 IP phone (PA168F) -- FireFly (IAX2 softphone) Everything works fine except a problem

> On Jul 13, 2017, at 10:43 AM, Bert Gunter <bgunter.4567 at gmail.com> wrote: > > poly(NIR, degree = 2) will work if NIR is a matrix, not a data.frame. > The degree argument apparently *must* be explicitly named if NIR is > not a numeric vector. AFAICS, this is unclear or unstated in ?poly. I still get the same error with: library(pld) data(gasoline) gasTrain <-

poly(NIR, degree = 2) will work if NIR is a matrix, not a data.frame. The degree argument apparently *must* be explicitly named if NIR is not a numeric vector. AFAICS, this is unclear or unstated in ?poly. -- Bert Bert Gunter "The trouble with having an open mind is that people keep coming along and sticking things into it." -- Opus (aka Berkeley Breathed in his "Bloom