open-vm-tools-devel Mailing List for open-vm-tools (Page 33)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Tracker item #2797776, was opened at 2009-05-28 01:45
Message generated for change (Settings changed) made by mvanzin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2797776&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: kernel modules
Group: v1.0 (example)
>Status: Closed
Resolution: Invalid
Priority: 5
Private: No
Submitted By: Reindl Harald (reindl_harald)
Assigned to: Nobody/Anonymous (nobody)
Summary: kernel-modules not longer building on fedora

Initial Comment:
Since april 2009 the open-vm-tools are not longer building on fedora 9 / fedora 10 
Since a long time i use the following script to build the kernel-modules for distributing after that to all other machines and it would be fine to get this working again because kernel 2.6.29 landed in updates-testing today

[root@buildserver:/scripts]$ cat /scripts/open-vm-tools/build.sh
#!/bin/bash

 tar -xzf open-vm-tools-*.gz
  cd open-vm-tools-*/modules/linux
  modsrc="/usr/lib/vmware-tools/modules/source"
  for x in `ls -d v*`
  do
     mv $x ${x}-only
     tar -cf $x.tar ${x}-only
     mv ${x}-only $x
     mv $modsrc/$x.tar $modsrc/$x.tar.orig
     mv $x.tar $modsrc
  done
  vmware-config-tools.pl

----------------------------------------------------------------------

>Comment By: Marcelo Vanzin (mvanzin)
Date: 2009-05-28 11:02

Message:
Reindl, not to get too held up in semantics, but you weren't building the
modules, you were re-packaging them. Once you re-package them, if you can't
build them it's probably an issue in *your* packaging steps, since we make
sure that if you build things using the open-vm-tools makefiles it will
build (and it does).

You're seeing issues because in the past two months I cleaned up all the
duplicate files in the open-vm-tools package. This means that a bunch of
headers and sources that used to be duplicated in all kernel modules'
directories are not there anymore and are instead re-used from other
places. This is a good thing because it helps us internally at VMware with
some projects we have in the mid-term. It also makes things better
organized.

So again, you're doing something that is not "standard building procedure"
as far as the package goes; so if things don't build for you now, you need
to fix your procedure and not the way around. Other people had problems
building the module too after these changes - and they fixed their packages
and now things work.

About the fgets() problem, we fixed it internally already, it's a simple
fix (just enclose it in an if () so that the compiler thinks you're using
the return value).

----------------------------------------------------------------------

Comment By: Dominique Leuenberger (dimstar)
Date: 2009-05-28 05:18

Message:
your tone is rude at best, and yet you expect help. Amazing.

Your issue is less with the open-vm-tools (you break them apart and try to
do something with them what they are not meant for).

Why don't you just take the original vmware-tools ones and apply the
existing patches???
It's not as they would not exist!

http://communities.vmware.com/thread/208963

OR:
Use the following script to build all the modules (we use this script on
openSUSE since first versions of open-vm-tools hit the download mirrors,
with only minor modifications long ago):

###
TOPDIR=$PWD
cd ..
mkdir -p obj
for flavor in %{flavors_to_build}; do
  rm -rf obj/$flavor
  cp -r %{name}-%{version}-%{svn_rev} obj/$flavor
  pushd obj/$flavor
  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) HEADER_DIR="/usr/src/linux-obj/$(uname
-i)/default/include" SRCROOT=$PWD OVT_SOURCE_DIR=$TOPDIR
    popd
  done
  popd
done
###

(this is part of the spec file posted recently on the open-vm-tools
maiinglist).
the 'for' with the flavors you can skip for your usecase. It will most
likely be 'default'

----------------------------------------------------------------------

Comment By: Reindl Harald (reindl_harald)
Date: 2009-05-28 04:54

Message:
> You need to file a bug against the Fedora rpmfusion packager (i.e.
myself), not upstream.
> For the record, I have an RPM of the latest open-vm-tools, but I'm
seeing
> massive regression (drag-n-drop not working, etc...). But i'm short on
> time, patches are always welcome.

Where does rpmfusion matter in my context?

I try to build the whole time by myself the same way i did before april
and i need only the newest kernel-modules
We are speaking from hi-performance web- and databaseservers living on an
vmware-esxi
drag-n-drop does not matter, i need vmxnet etc. on the
buildmachine/internel cacherepo and distribute them with rsync to the other
machines before distribute the kernel-updates to avoid downtime and
problems maybe not solveable without networking on the live-servers.

If i would have a rock-stable src.rpm which builds the newest versions for
vmci, vmemctl and vmxnet against the last kernel-updates i can distribute
this as optimiized httpd, php... from the buildmachine.

However - It's crazy to modify the open-vm-tools in a way that they makes
such problems
On VMware-Supported distributions they nobody needs and on guests where
you need them you can not use them any longer - WTF?

----------------------------------------------------------------------

Comment By: Denis Leroy (poolshark)
Date: 2009-05-28 04:39

Message:
You need to file a bug against the Fedora rpmfusion packager (i.e. myself),
not upstream.

For the record, I have an RPM of the latest open-vm-tools, but I'm seeing
massive regression (drag-n-drop not working, etc...). But i'm short on
time, patches are always welcome.

----------------------------------------------------------------------

Comment By: Reindl Harald (reindl_harald)
Date: 2009-05-28 03:35

Message:
Now i try to get compiled the kernel-modules and i would like to copy them
directly without install the other stuff
But it is not building - So give me please a working way to get the
kernel-modules built on recent fedora-versions or make the old way working
again

cc1: warnings being treated as errors
wiperPosix.c: In function 'Wiper_Init':
wiperPosix.c:1016: error: ignoring return value of 'fgets', declared with
attribute warn_unused_result
make[2]: *** [wiperPosix.lo] Fehler 1
make[2]: Leaving directory
`/usr/local/scripts/open-vm-tools/open-vm-tools-2009.05.22-167859/lib/wiper'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory
`/usr/local/scripts/open-vm-tools/open-vm-tools-2009.05.22-167859/lib'
make: *** [all-recursive] Fehler 1
#!/bin/bash

cd /scripts/open-vm-tools/open-vm-tools*/
export CFLAGS="-O6 -march=native -mtune=native -fopenmp -pipe
-fno-strict-aliasing -D_FORTIFY_SOURCE=2"
export CXXFLAGS="-O6 -march=native -mtune=native -fopenmp -pipe
-fno-strict-aliasing -D_FORTIFY_SOURCE=2"

./configure \
 --host=x86_64-redhat-linux-gnu \
 --build=x86_64-redhat-linux-gnu \
 --without-procps \
 --without-gtkmm \
 --without-gtk2 \
 --disable-unity \
 --disable-docs && make

----------------------------------------------------------------------

Comment By: Reindl Harald (reindl_harald)
Date: 2009-05-28 02:24

Message:
> The module directories don't contain all needed files anymore

WHY?
You make unuseable this for non c-programmers in many cases or hurt them
Since many months this works very well on round 20 guest-machines and

On the referenced mailing-list i find no clear solution to get this
working as it did 
before april 2009. 

> you should probably get them from VMware's Tools distribution that goes
with the products

If this would be so easy there would be NO NEED for open-vm-tools because
you need them
for distributions with really new kernels as not official supported
fedora-guests

----------------------------------------------------------------------

Comment By: Marcelo Vanzin (mvanzin)
Date: 2009-05-28 02:00

Message:
That won't work. The module directories don't contain all needed files
anymore - the shared files are reused from other locations. If you want the
tar packages you should probably get them from VMware's Tools distribution
that goes with the products, or try to adapt the instructions on the
following thread to create them from the open-vm-tools code:

https://sourceforge.net/mailarchive/forum.php?thread_name=200905181606.57759.olivier.lahaye%40cea.fr&forum_name=open-vm-tools-devel

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2797776&group_id=204462

2007	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (30)	Oct (50)	Nov (42)	Dec (17)
2008	Jan (36)	Feb (13)	Mar (74)	Apr (17)	May (62)	Jun (53)	Jul (32)	Aug (58)	Sep (44)	Oct (21)	Nov (35)	Dec (53)
2009	Jan (43)	Feb (58)	Mar (14)	Apr (16)	May (61)	Jun (49)	Jul (11)	Aug (22)	Sep (37)	Oct (12)	Nov (23)	Dec (10)
2010	Jan (21)	Feb (13)	Mar (5)	Apr (18)	May (14)	Jun (10)	Jul (1)	Aug	Sep (13)	Oct (8)	Nov (11)	Dec (14)
2011	Jan (13)	Feb (19)	Mar (16)	Apr (10)	May (22)	Jun (4)	Jul (63)	Aug (14)	Sep (10)	Oct (12)	Nov (10)	Dec (43)
2012	Jan (3)	Feb (4)	Mar (35)	Apr (1)	May (32)	Jun (8)	Jul (10)	Aug (6)	Sep (3)	Oct (25)	Nov (14)	Dec (4)
2013	Jan (12)	Feb (6)	Mar (15)	Apr (24)	May (9)	Jun (2)	Jul	Aug (4)	Sep	Oct (8)	Nov (3)	Dec
2014	Jan (5)	Feb	Mar (4)	Apr (2)	May (4)	Jun	Jul (4)	Aug	Sep	Oct	Nov	Dec (3)
2015	Jan	Feb (5)	Mar	Apr (1)	May (3)	Jun (1)	Jul (2)	Aug (5)	Sep	Oct	Nov (2)	Dec
2017	Jan	Feb (1)	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

open-vm-tools-devel Mailing List for open-vm-tools (Page 33)

open-vm-tools-devel — List for open-vm-tools developer discussions.