I messed around with information I could find on the web. I did the same
things, but in different order, on two different SL6.5 installs on two
different virtual machines. It worked on one and not the other. This was
within the last couple weeks. Akemi Yagi, I believe it was, offered some
potential solutions.

Maybe by now if you search the web about it better data can be found. But
you surely can look at back messages on this list, somewhere, I bet.

{^_^}   Joanne

On 2014/02/27 22:42, Mahmood Naderan wrote:
> So is this a good solution
>
> ln -s /usr/src/kernels/2.6.32-279.5.1.el6.x86_64/include/linux/autoconf.h
> /usr/include/linux/autoconf.h
>
> ?
> Regards,
> Mahmood
>
>
> On Friday, February 28, 2014 10:09 AM, jdow <[log in to unmask]> wrote:
> Because it's not in "/usr/include/linux/autoconf.h". Somehow you and I need
> to learn how to convince the compiler that it should look in the "/usr/src"
> hierarchy to find the includes rather than the standard "/usr/include"
> hierarchy. Frustrating, isn't it?
>
> {^_^}  Joanne
>
> On 2014/02/27 21:13, Mahmood Naderan wrote:
>  > Hi
>  > I am trying to install Virtualbox 4.3.8 on my SL6.3. The installation seems
> to be OK
>  >
>  > |# rpm -ivh VirtualBox-4.3-4.3.8_92456_el6-1.x86_64.rpm
>  > warning: VirtualBox-4.3-4.3.8_92456_el6-1.x86_64.rpm: Header V4 DSA/SHA1
>  > Signature, key ID 98ab5139: NOKEY
>  > Preparing...                ########################################### [100%]
>  >    1:VirtualBox-4.3        ########################################### [100%]
>  >
>  > Creating group 'vboxusers'. VM users must be member of that group!
>  >
>  > No precompiled module for this kernel found -- trying to build one. Messages
>  > emitted during module compilation will be logged to /var/log/vbox-install.log.
>  >
>  > Stopping VirtualBox kernel modules [ OK  ]
>  > Recompiling VirtualBox kernel modules [  OK  ]
>  > Starting VirtualBox kernel modules [  OK  ]|
>  >
>  > However the log file at /var/log contains multiple messages like this
>  >
>  >    |ld -r -m elf_x86_64 -T
>  >    /usr/src/kernels/2.6.32-279.5.1.el6.x86_64/scripts/module-common.lds
>  >    --build-id -o /tmp/vbox.0/vboxnetadp.ko /tmp/vbox.0/vboxnetadp.o
>  >    /tmp/vbox.0/vboxnetadp.mod.o
>  >    make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0
>  >    CONFIG_MODULE_SIG= -C /lib/modules/2.6.32-279.5.1.el6.x86_64/build modules
>  >    test -e include/linux/autoconf.h -a -e include/config/auto.conf || (      \
>  >        echo;                        \
>  >        echo "  ERROR: Kernel configuration is invalid.";      \
>  >        echo "        include/linux/autoconf.h or include/config/auto.conf are
>  >    missing.";  \
>  >        echo "        Run 'make oldconfig && make prepare' on kernel src to fix
>  >    it.";  \
>  >        echo;                        \
>  >        /bin/false)
>  >    mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*|
>  >
>  >
>  >
>  > Actually the autoconf.h file exists in the source path
>  >
>  > |# find /usr/ -name autoconf.h
>  > /usr/src/kernels/2.6.32-279.5.1.el6.x86_64/include/linux/autoconf.h
>  >
>  > |So why should I receive such messages
>  >
>  >
>  > Regards,
>  > Mahmood
>
>