On 25/07/10 08:08, Clyde Reed wrote: > > I am running into the following configuration warning regarding cpuid.h. > I'm assuming I need to ensure the configuratin warning is removed up > before I go forward--
Why? > checking for unistd.h... (cached) no > > checking cpuid.h usability... no > > checking cpuid.h presence... yes > > configure: WARNING: cpuid.h: present but cannot be compiled > > configure: WARNING: cpuid.h: check for missing prerequisite headers? > > configure: WARNING: cpuid.h: see the Autoconf documentation > > configure: WARNING: cpuid.h: section "Present But Cannot Be Compiled" > > configure: WARNING: cpuid.h: proceeding with the preprocessor's result > > configure: WARNING: cpuid.h: in the future, the compiler will take > precedence > Does this warning cause any problems? > What am I missing in the book to end up with the configuration warning > message regarding cpuid.h? Can you point me in the right direction to > find the answer to resolve what I'm doing wrong? > Maybe you're being to sensitive? Warnings are not errors. I would suggest that you keep going 'til you hit an error. Don't ignore errors. I generally ignore warnings unless something doesn't work. Andy -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
