Tracker item #2071988, was opened at 2008-08-24 20:22
Message generated for change (Comment added) made by dimstar
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2071988&group_id=204462
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Dominique Leuenberger (dimstar)
Assigned to: Nobody/Anonymous (nobody)
Summary: Module vmci does not compile
Initial Comment:
Im trying to spin up new rpms for open-vm-tools (opensuse).
The configure uses --without-kernel-modules (as the build actually happens in a
controlled virtual environment, not running the target kernel).
the modules themself are after built using
#make modules
for module in %{vm_modules}; do
pushd modules/linux/$module
make -C /usr/src/linux-obj/%{_target_cpu}/$flavor modules M=$PWD
VM_CCVER=$(gcc -dumpversion) SRCROOT=$PWD
popd
done
vm_modules contains a list of modules to be built: "vmblock vmhgfs ... vmci"
this works (and did for long time now) for all modules, but on vmci it fails
with the following errors:
+ for module in vmblock vmhgfs vmmemctl vmsync vmxnet vsock vmci
+ pushd modules/linux/vmci
/usr/src/packages/BUILD/obj/debug/modules/linux/vmci
/usr/src/packages/BUILD/obj/debug /usr/src/packages/BUILD
++ gcc -dumpversion
+ make -C /usr/src/linux-obj/i586/debug modules
M=/usr/src/packages/BUILD/obj/debug/modules/linux/vmci VM_CCVER=4.3
SRCROOT=/usr/src/packages/BUILD/obj/debug/modules/linux/vmci
make: Entering directory `/usr/src/linux-2.6.27-rc3-2-obj/i386/debug'
make -C ../../../linux-2.6.27-rc3-2
O=/usr/src/linux-2.6.27-rc3-2-obj/i386/debug/. modules
Using standalone build system.
/usr/src/packages/BUILD/obj/debug/modules/linux/vmci/autoconf/geninclude.c:19:28:
error: linux/autoconf.h: No such file or directory
/usr/src/linux-2.6.27-rc3-2/scripts/Makefile.build:46: *** CFLAGS was changed
in "/usr/src/packages/BUILD/obj/debug/modules/linux/vmci/Makefile". Fix it to
use EXTRA_CFLAGS. Stop.
make[2]: *** [_module_/usr/src/packages/BUILD/obj/debug/modules/linux/vmci]
Error 2
make[1]: *** [sub-make] Error 2
make: *** [all] Error 2
make: Leaving directory `/usr/src/linux-2.6.27-rc3-2-obj/i386/debug'
error: Bad exit status from /var/tmp/rpm-tmp.23557 (%build)
I would anticipate if somebody could have a look into this. Most likely a small
thing which I miss. The Makefile seems to be an exact copy of the one from
vmxnet, except to the drivers name... so I really miss something.
Thank you
----------------------------------------------------------------------
>Comment By: Dominique Leuenberger (dimstar)
Date: 2008-08-25 09:29
Message:
Logged In: YES
user_id=263934
Originator: YES
I'm not using the GIT tree. For the RPMs, I always use the officially
released tarballs (so in tis case 2008-08-08).
- File permissions are as in the tarball... will have to check further
wether there is a problem or not
- Environment: the script goes through a FOR loop, compiling all the
different modules. I can try to adjust the order of them, in case this
should matter. But this would be weird.
The kernel tree is sane (all modules are built against this tree, of the
entire distribution... and the problem does not only happen in one version
of the distro... so assuming that all the trees are broken sounds rude
against the distro maintainers (I know you did not mean it like that... )
So I'll change the order of the modules, having vsock and vmci before the
others... let's see what happens... I'll report back later today).
----------------------------------------------------------------------
Comment By: Adar Dembo (adembo)
Date: 2008-08-25 08:40
Message:
Logged In: YES
user_id=1867590
Originator: NO
I really don't know what the problem might be. As you said, the Makefiles
are virtually identical: the only difference being the name of the driver.
Could you do some basic sanity checks:
- Make sure you haven't modified files in git, and that git's view of the
source is healthy (assuming you're using git).
- Make sure the file permissions are correct.
- Make sure you haven't set any environment variables that might affect
things.
- Make sure your kernel tree is sane.
When exactly did this start? With 2008.08.08? Or some time later?
----------------------------------------------------------------------
Comment By: Dominique Leuenberger (dimstar)
Date: 2008-08-24 20:35
Message:
Logged In: YES
user_id=263934
Originator: YES
compared to the compilation of vmxnet, the following line is different:
vmxnet: Using 2.6.x kernel build system.
vmci (and also vsock): Using standalone build system.
Maybe it helps.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2071988&group_id=204462
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
open-vm-tools-devel mailing list
open-vm-tools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
