|
From: Daniel T. <dt...@vo...> - 2007-11-12 15:25:48
|
kd2bd wrote: >> Possibly the header files for the wrong libc are being accessed? That >> would explain both the initial compiler errors and the later execution= >> inconsistencies. >=20 > Possibly due to upgrading the kernel source, placing it under /usr/src,= and > keeping a symbolic link between the system header file directory and th= e > new kernel header file directory? >=20 > (*Sigh*... Now hanging head in shame...) >=20 > If that's the cause, it's the first time that practice has ever caused = a > problem. >=20 > But I suppose there's a first time for everything... :-( >=20 Perhaps if the header files for your current libc weren't installed so it ran down the include path to the kernel headers? I'm hard pressed to come up with a scenario where it would compile at all and get the wrong headers, myself, but it always pays to check out the stuff that's obvious by the errors even if it's wildly improbable. --=20 Daniel Taylor VP Operations Vocal Laboratories, Inc. dt...@vo... http://www.vocalabs.com/ (952)941-6580x203 |