Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#24 configure: Cannot specify kernel constraints on command line

v1.0 (example)
closed
Ghais Issa
5
2008-06-28
2008-06-03
Craig Phillips
No

There are a few problems with the configure script. We need to be able to build these tools across a variety of platforms using our own build environment. However, there is no way to specify the environment to configure.

e.g. in configure script:

line 2195: getOsVersion() uses uname -r
Assumes the running kernel is the kernel being built against. This is incorrect. The kernel built against is defined within our environment.

expected flag to configure:

--kernel-version=2.6.22

line 26547: MODULES_DIR
Assumes again that the running kernel is the kernel being built against and also that the modules are located in the system modules directory rather than that specified on the command line:

expected flag to configure:

--kernel-modules-dir=/home/someuser/src/someenvironment/lib/modules

Discussion

  • Ghais Issa
    Ghais Issa
    2008-06-03

    • assigned_to: nobody --> gissa
     
  • ECL
    ECL
    2008-06-28

    Logged In: YES
    user_id=18318
    Originator: NO

    Should be fixed in the latest refresh.

     
  • ECL
    ECL
    2008-06-28

    • status: open --> closed
     
  • Logged In: YES
    user_id=760540
    Originator: NO

    Even if configure was called with with-kernel-release option, modules has build from "uname -r" sourcetree.

    VM_UNAME variable in modules/linux/*/Makefile are "hardcoded" to:
    ./modules/linux/vmblock/Makefile:29:VM_UNAME = $(shell uname -r)

     
  • Adar Dembo
    Adar Dembo
    2008-07-29

     
    Attachments
  • Adar Dembo
    Adar Dembo
    2008-07-29

    Logged In: YES
    user_id=1867590
    Originator: NO

    Thanks for the follow-up. Ghais has been working on a patch to fix this new problem. I've attached it to this bug report. Apply it to your open-vm-tools tree and run "autoreconf --install" (make sure you have your distro's autoconf package and its dependencies installed) to rebuild the build system. After that, --with-kernel-release at configure time should work properly.
    File Added: configure.ac.patch

     
  • Adar Dembo
    Adar Dembo
    2008-07-29

     
    Attachments
  • Adar Dembo
    Adar Dembo
    2008-07-29

    Logged In: YES
    user_id=1867590
    Originator: NO

    File Added: Makefile.am.patch