Menu
▾
▴
open-vm-tools-devel — List for open-vm-tools developer discussions.
You can subscribe to this list here.
| 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
|
|
From: Stanislav <ste...@ci...> - 2012-03-16 06:43:31
|
On 3/16/2012 9:42 AM, Dmitry Torokhov wrote: > On Thu, Mar 15, 2012 at 08:53:43PM +0400, Stanislav wrote: >> Thanks a lot. >> >> Next simple question from my side. I wanted to use scripts before >> and after snapshot creation, but see that there is no RPC messages >> from ESX(WS) to VMTools(and no any actions in the scripts). Does it >> work fine for others? Maybe there are some tricks? >> > What scripts/snapshots are you talking about? Are you trying to set up > VCB or just regular VM snapshots? > > Thanks, > Dmitry > I'm talking about regular VM snapshot, scripts: /usr/sbin/pre-freeze-script and /usr/sbin/post-thaw-script -- Stas |
|
From: Dmitry T. <dt...@vm...> - 2012-03-16 05:43:00
|
On Thu, Mar 15, 2012 at 08:53:43PM +0400, Stanislav wrote: > Thanks a lot. > > Next simple question from my side. I wanted to use scripts before > and after snapshot creation, but see that there is no RPC messages > from ESX(WS) to VMTools(and no any actions in the scripts). Does it > work fine for others? Maybe there are some tricks? > What scripts/snapshots are you talking about? Are you trying to set up VCB or just regular VM snapshots? Thanks, Dmitry |
|
From: Stanislav <ste...@ci...> - 2012-03-15 16:53:56
|
Thanks a lot. Next simple question from my side. I wanted to use scripts before and after snapshot creation, but see that there is no RPC messages from ESX(WS) to VMTools(and no any actions in the scripts). Does it work fine for others? Maybe there are some tricks? On 3/15/2012 8:15 PM, Dmitry Torokhov wrote: > Hi Stanislav, > > On Thursday, March 15, 2012 07:16:14 PM Stanislav wrote: >> Hi there, >> >> I see in the code "/* Check to see if we're going above our limit. See bug >> 605821. */". Where can I find information about this bug? > Because open-vm-tools originate from the same code base as our VMware Tools > that are shipped with the platforms you may find some references to our > internal bug tracking system in the sources. Unfortunately access to this > system is restricted to employees of VMware. > > Thanks, > Dmitry > > -- Stas |
|
From: Dmitry T. <dt...@vm...> - 2012-03-15 16:15:50
|
Hi Stanislav, On Thursday, March 15, 2012 07:16:14 PM Stanislav wrote: > Hi there, > > I see in the code "/* Check to see if we're going above our limit. See bug > 605821. */". Where can I find information about this bug? Because open-vm-tools originate from the same code base as our VMware Tools that are shipped with the platforms you may find some references to our internal bug tracking system in the sources. Unfortunately access to this system is restricted to employees of VMware. Thanks, Dmitry |
|
From: Stanislav <ste...@ci...> - 2012-03-15 15:16:31
|
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi there,<br>
<br>
I see in the code "/* Check to see if we're going above our limit.
See bug <b>605821</b>. */". Where can I find information about this
bug?<br>
<pre class="moz-signature" cols="72">--
Stas</pre>
</body>
</html>
|
|
From: SourceForge.net <no...@so...> - 2012-03-15 01:02:22
|
Tracker item #3485535, was opened at 2012-02-07 16:25 Message generated for change (Comment added) made by adroit You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3485535&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: guestd Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Troy Bowman (adroit) Assigned to: Nobody/Anonymous (nobody) Summary: vmtoolsd quiesce for snapshot and multiple root mtab entries Initial Comment: I don't know if the previous "quiescing fails on ubuntu" bug has anything to do with this, but here is what I am seeing on Gentoo. A feature of the 2.6 kernel is that rootfs is inherent and gets overmounted by the real root later in the boot process. From: /usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt "Rootfs is a special instance of ramfs (or tmpfs, if that's enabled), which is always present in 2.6 systems. You can't unmount rootfs for approximately the same reason you can't kill the init process; rather than having special code to check for and handle an empty list, it's smaller and simpler for the kernel to just make sure certain lists can't become empty. "Most systems just mount another filesystem over rootfs and ignore it. The amount of space an empty instance of ramfs takes up is tiny." This is the very thing that is happening on my Gentoo system, as I have two rootfs entries: # cat /etc/mtab | head -2 rootfs / rootfs rw 0 0 /dev/root / ext3 rw,noatime,errors=continue,barrier=0,data=ordered 0 0 And as I strace vmtoolsd during a vm snapshot with filesystem quiescing on, I can see that it is trying to FIFREEZE both root entries, only to fail on the second one and then and the entire operation aborts. open("/etc/mtab", O_RDONLY) = 20 fstat(20, {st_mode=S_IFREG|0644, st_size=985, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fdbe1ec7000 read(20, "rootfs / rootfs rw 0 0\n/dev/root"..., 1024) = 985 read(20, "", 1024) = 0 close(20) = 0 munmap(0x7fdbe1ec7000, 4096) = 0 open("/", O_RDONLY) = 20 ioctl(20, FIFREEZE, 0x14) = 0 open("/", O_RDONLY) = 21 ioctl(21, FIFREEZE, 0x15) = -1 EBUSY (Device or resource busy) close(21) = 0 ioctl(20, FITHAW, 0x3) = 0 close(20) = 0 sendto(16, "<12>Feb 7 17:09:26 vmsvc[3013]:"..., 84, MSG_NOSIGNAL, NULL, 0) = 84 I tested the same operation on the same system using the official tools binaries from VMWare, and they do not suffer from this problem. I wonder if Open Virtual Machine tools could be more intelligent about freezing filesystems, by not trying to freeze the same filesystem more than once. Thanks. ---------------------------------------------------------------------- >Comment By: Troy Bowman (adroit) Date: 2012-03-14 18:02 Message: For what it's worth, my current workaround is to edit /etc/init.d/mtab, and change the line from: grep -v "^[^ ]* / tmpfs " /proc/mounts > /etc/mtab to: egrep -v "^[^ ]* / tmpfs|rootfs" /proc/mounts > /etc/mtab Although, I would much rather have open-vm-tools be more intelligent. ---------------------------------------------------------------------- Comment By: Eric Johnson (ericejohnson) Date: 2012-03-13 04:16 Message: I can confirm that I see this problem as well on Gentoo Linux. I see no problems with kernel version 2.6.33. Subsequent kernels that I've tested, however, don't work. This is particularly problematic, because the latest stable gentoo uses a udev version that frowns upon kernel versions before 2.6.33, and the earliest stable version after that - as of this comment - is 3.0.17 (http://packages.gentoo.org/package/sys-kernel/gentoo-sources) So for Gentoo, this really needs a fix, because there's currently no way to bring up a new stable Gentoo system and use the open-vm-tools without running into this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3485535&group_id=204462 |
|
From: Dmitry T. <dt...@vm...> - 2012-03-13 16:10:19
|
On Tuesday, March 13, 2012 09:00:49 AM Stephen Hemminger wrote: > On Tue, 13 Mar 2012 16:48:10 +0100 > > Reindl Harald <h.r...@th...> wrote: > > Am 11.03.2012 02:25, schrieb Stephen Hemminger: > > > Latest kernels got rid of set/get tx/rx checksum in favor of a more > > > generic set_features interface. The vmxnet driver needs to be > > > updated. > > > Before I go off and waste time doing it, is there a newer version? > > > > why do you not use vmxnet3 which is in the mainline-kernel > > since a longer time and so needs no kernel-modules from > > third-party-packages? > > Vmware workstation does not officially support vmxnet3. It is possible to > make vmxnet3 work with some config file editing, but it isn't really > supported. > > Not a big issue, but need to use workstation to validate builds when running > on my laptop. While we are going to update OVT and that will bring fixes to vmxnet for newer kernels I believe we recommend using either e1000 or vmxnet3 virtual devices instead of vmxnet. Vmxnet is _very_ old. Thanks, Dmitry |
|
From: Reindl H. <h.r...@th...> - 2012-03-13 16:03:26
|
Am 13.03.2012 17:00, schrieb Stephen Hemminger: > On Tue, 13 Mar 2012 16:48:10 +0100 > Reindl Harald <h.r...@th...> wrote: > >> >> >> Am 11.03.2012 02:25, schrieb Stephen Hemminger: >>> Latest kernels got rid of set/get tx/rx checksum in favor of a more >>> generic set_features interface. The vmxnet driver needs to be updated. >>> Before I go off and waste time doing it, is there a newer version? >> >> why do you not use vmxnet3 which is in the mainline-kernel >> since a longer time and so needs no kernel-modules from >> third-party-packages? >> > > Vmware workstation does not officially support vmxnet3. It is possible to make > vmxnet3 work with some config file editing, but it isn't really supported. > > Not a big issue, but need to use workstation to validate builds when running > on my laptop. i am using vmxnet3 on a large amount of VMware-Wokrstation machines as also on all orduction servers hosted on ESXi 4.1 since a really long time and would never ever use vmxnet2 since you have a big problem is something goes wrong and you need network access from your guest to fix the troubles |
|
From: Stephen H. <she...@vy...> - 2012-03-13 16:00:58
|
On Tue, 13 Mar 2012 16:48:10 +0100 Reindl Harald <h.r...@th...> wrote: > > > Am 11.03.2012 02:25, schrieb Stephen Hemminger: > > Latest kernels got rid of set/get tx/rx checksum in favor of a more > > generic set_features interface. The vmxnet driver needs to be updated. > > Before I go off and waste time doing it, is there a newer version? > > why do you not use vmxnet3 which is in the mainline-kernel > since a longer time and so needs no kernel-modules from > third-party-packages? > Vmware workstation does not officially support vmxnet3. It is possible to make vmxnet3 work with some config file editing, but it isn't really supported. Not a big issue, but need to use workstation to validate builds when running on my laptop. |
|
From: Reindl H. <h.r...@th...> - 2012-03-13 15:48:20
|
Am 11.03.2012 02:25, schrieb Stephen Hemminger: > Latest kernels got rid of set/get tx/rx checksum in favor of a more > generic set_features interface. The vmxnet driver needs to be updated. > Before I go off and waste time doing it, is there a newer version? why do you not use vmxnet3 which is in the mainline-kernel since a longer time and so needs no kernel-modules from third-party-packages? |
|
From: SourceForge.net <no...@so...> - 2012-03-13 11:16:36
|
Tracker item #3485535, was opened at 2012-02-07 16:25 Message generated for change (Comment added) made by ericejohnson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3485535&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: guestd Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Troy Bowman (adroit) Assigned to: Nobody/Anonymous (nobody) Summary: vmtoolsd quiesce for snapshot and multiple root mtab entries Initial Comment: I don't know if the previous "quiescing fails on ubuntu" bug has anything to do with this, but here is what I am seeing on Gentoo. A feature of the 2.6 kernel is that rootfs is inherent and gets overmounted by the real root later in the boot process. From: /usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt "Rootfs is a special instance of ramfs (or tmpfs, if that's enabled), which is always present in 2.6 systems. You can't unmount rootfs for approximately the same reason you can't kill the init process; rather than having special code to check for and handle an empty list, it's smaller and simpler for the kernel to just make sure certain lists can't become empty. "Most systems just mount another filesystem over rootfs and ignore it. The amount of space an empty instance of ramfs takes up is tiny." This is the very thing that is happening on my Gentoo system, as I have two rootfs entries: # cat /etc/mtab | head -2 rootfs / rootfs rw 0 0 /dev/root / ext3 rw,noatime,errors=continue,barrier=0,data=ordered 0 0 And as I strace vmtoolsd during a vm snapshot with filesystem quiescing on, I can see that it is trying to FIFREEZE both root entries, only to fail on the second one and then and the entire operation aborts. open("/etc/mtab", O_RDONLY) = 20 fstat(20, {st_mode=S_IFREG|0644, st_size=985, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fdbe1ec7000 read(20, "rootfs / rootfs rw 0 0\n/dev/root"..., 1024) = 985 read(20, "", 1024) = 0 close(20) = 0 munmap(0x7fdbe1ec7000, 4096) = 0 open("/", O_RDONLY) = 20 ioctl(20, FIFREEZE, 0x14) = 0 open("/", O_RDONLY) = 21 ioctl(21, FIFREEZE, 0x15) = -1 EBUSY (Device or resource busy) close(21) = 0 ioctl(20, FITHAW, 0x3) = 0 close(20) = 0 sendto(16, "<12>Feb 7 17:09:26 vmsvc[3013]:"..., 84, MSG_NOSIGNAL, NULL, 0) = 84 I tested the same operation on the same system using the official tools binaries from VMWare, and they do not suffer from this problem. I wonder if Open Virtual Machine tools could be more intelligent about freezing filesystems, by not trying to freeze the same filesystem more than once. Thanks. ---------------------------------------------------------------------- Comment By: Eric Johnson (ericejohnson) Date: 2012-03-13 04:16 Message: I can confirm that I see this problem as well on Gentoo Linux. I see no problems with kernel version 2.6.33. Subsequent kernels that I've tested, however, don't work. This is particularly problematic, because the latest stable gentoo uses a udev version that frowns upon kernel versions before 2.6.33, and the earliest stable version after that - as of this comment - is 3.0.17 (http://packages.gentoo.org/package/sys-kernel/gentoo-sources) So for Gentoo, this really needs a fix, because there's currently no way to bring up a new stable Gentoo system and use the open-vm-tools without running into this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3485535&group_id=204462 |
|
From: Dmitry T. <dt...@vm...> - 2012-03-12 16:59:08
|
Hi Stephen, On Saturday, March 10, 2012 05:25:22 PM Stephen Hemminger wrote: > Latest kernels got rid of set/get tx/rx checksum in favor of a more > generic set_features interface. The vmxnet driver needs to be updated. > Before I go off and waste time doing it, is there a newer version? Which driver are you talking about? The mainline should be up to date, or are you talking about the driver coming with out VMware Tools? Thanks, Dmitry |
|
From: Stephen H. <she...@vy...> - 2012-03-11 01:25:32
|
Latest kernels got rid of set/get tx/rx checksum in favor of a more generic set_features interface. The vmxnet driver needs to be updated. Before I go off and waste time doing it, is there a newer version? |
|
From: SourceForge.net <no...@so...> - 2012-02-23 17:38:03
|
Tracker item #3378690, was opened at 2011-07-26 07:38 Message generated for change (Comment added) made by david99world You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3378690&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: None Status: Pending Resolution: None Priority: 5 Private: No Submitted By: Sean (svz90) Assigned to: Nobody/Anonymous (nobody) Summary: DnD From Host to Guest Fails Initial Comment: When trying to drag and drop a file from the Host operating system to the guest, I get the following error message: Error stating file '/proc/fs/vmblock/mountPoint/cdd623db/filename' No such file or directory where filename is the file from the host system. I am running open-vm-tools version 2011.07.19, with Arch Linux (kernel version 2.6.39), and Xfce 4.8. Using VMWare Player 3.1.4 build-385536. I checked the startup scripts, and vmblock is mounted and running. The /proc/fs/vmblock/mountpoint directory is symlinked to /tmp/VMWareDnD/cdd623db. Drag and drop from guest to host works fine. Clipboard synchronization works in both directions (though only with text - not with files). Thank you for any help in this matter. Regards, svz90 ---------------------------------------------------------------------- Comment By: DavidGray (david99world) Date: 2012-02-23 09:38 Message: Hi, I get exactly the same problem, ps ax | grep vmtoolsd shown below.. dave@ubuntu:~$ ps ax | grep vmtoolsd 1941 pts/0 S+ 0:00 grep --color=auto vmtoolsd ---------------------------------------------------------------------- Comment By: Marcelo Vanzin (mvanzin) Date: 2011-12-12 13:43 Message: No reply -> pending. ---------------------------------------------------------------------- Comment By: Marcelo Vanzin (mvanzin) Date: 2011-10-31 15:54 Message: How is vmware-user being started in your system? (You could do a "ps ax | grep vmtoolsd" and post the results so we could look at it.) The correct way is to run vmware-user-suid-wrapper; running "vmtoolsd -n vmusr" directly will not work and will cause the issue you're running into. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3378690&group_id=204462 |
|
From: SourceForge.net <no...@so...> - 2012-02-08 00:25:41
|
Tracker item #3485535, was opened at 2012-02-07 16:25 Message generated for change (Tracker Item Submitted) made by adroit You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3485535&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: guestd Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Troy Bowman (adroit) Assigned to: Nobody/Anonymous (nobody) Summary: vmtoolsd quiesce for snapshot and multiple root mtab entries Initial Comment: I don't know if the previous "quiescing fails on ubuntu" bug has anything to do with this, but here is what I am seeing on Gentoo. A feature of the 2.6 kernel is that rootfs is inherent and gets overmounted by the real root later in the boot process. From: /usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt "Rootfs is a special instance of ramfs (or tmpfs, if that's enabled), which is always present in 2.6 systems. You can't unmount rootfs for approximately the same reason you can't kill the init process; rather than having special code to check for and handle an empty list, it's smaller and simpler for the kernel to just make sure certain lists can't become empty. "Most systems just mount another filesystem over rootfs and ignore it. The amount of space an empty instance of ramfs takes up is tiny." This is the very thing that is happening on my Gentoo system, as I have two rootfs entries: # cat /etc/mtab | head -2 rootfs / rootfs rw 0 0 /dev/root / ext3 rw,noatime,errors=continue,barrier=0,data=ordered 0 0 And as I strace vmtoolsd during a vm snapshot with filesystem quiescing on, I can see that it is trying to FIFREEZE both root entries, only to fail on the second one and then and the entire operation aborts. open("/etc/mtab", O_RDONLY) = 20 fstat(20, {st_mode=S_IFREG|0644, st_size=985, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fdbe1ec7000 read(20, "rootfs / rootfs rw 0 0\n/dev/root"..., 1024) = 985 read(20, "", 1024) = 0 close(20) = 0 munmap(0x7fdbe1ec7000, 4096) = 0 open("/", O_RDONLY) = 20 ioctl(20, FIFREEZE, 0x14) = 0 open("/", O_RDONLY) = 21 ioctl(21, FIFREEZE, 0x15) = -1 EBUSY (Device or resource busy) close(21) = 0 ioctl(20, FITHAW, 0x3) = 0 close(20) = 0 sendto(16, "<12>Feb 7 17:09:26 vmsvc[3013]:"..., 84, MSG_NOSIGNAL, NULL, 0) = 84 I tested the same operation on the same system using the official tools binaries from VMWare, and they do not suffer from this problem. I wonder if Open Virtual Machine tools could be more intelligent about freezing filesystems, by not trying to freeze the same filesystem more than once. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3485535&group_id=204462 |
|
From: Dmitry T. <dt...@vm...> - 2012-02-01 17:54:15
|
Hi Kenneth, On Wednesday, February 01, 2012 09:11:39 AM Kenneth Adam Miller wrote: > If you read the link that I have posted, you will find that doing an > install from the repository doesn't give open-vm-tools that will run in > vmware when arch has the new 3.2 kernel. The link also talks about how to > fix the problem. Because I think that you will agree that installers of > this package should not have to go find this specific thread or know to > build against their kernel in order to get it to work, I am suggesting that > it be updated. I would perform the update if I could, but I'm not > authorized to contribute, and I'm not familiar with the code base. Let me > know if there's anything I can do to help. We (open-vm-tools project) do not create packages for specific distributions, but rather provide only source and expect distribution maintainers to package it in the way that is most suitable for particular distribution. Since you seem to be using Arch Linux you need to contact its package maintainer (Sergej Pupykin) and/or open bugs against this package. See: http://www.archlinux.org/packages/community/x86_64/open-vm-tools/ Regarding vmblock: we are deprecating in-kernel vmblock driver in favor of a FUSE-based solution and recommend distributions also switch to vmblock-fuse. Vmware Tools shipped with out products use FUSE-based vmblock when running on kernels 2.6.27 and above. Thanks, Dmitry |
|
From: Kenneth A. M. <ken...@gm...> - 2012-02-01 15:11:50
|
If you read the link that I have posted, you will find that doing an install from the repository doesn't give open-vm-tools that will run in vmware when arch has the new 3.2 kernel. The link also talks about how to fix the problem. Because I think that you will agree that installers of this package should not have to go find this specific thread or know to build against their kernel in order to get it to work, I am suggesting that it be updated. I would perform the update if I could, but I'm not authorized to contribute, and I'm not familiar with the code base. Let me know if there's anything I can do to help. https://bbs.archlinux.org/viewtopic.php?pid=1051159#p1051159 |
|
From: SourceForge.net <no...@so...> - 2012-01-17 10:44:36
|
Tracker item #3459926, was opened at 2011-12-15 02:06 Message generated for change (Comment added) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3459926&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: Carlo (clandmeter) Assigned to: Nobody/Anonymous (nobody) Summary: 2011.11.20 fails to build on uclibc Initial Comment: I am trying to build the latest tools on uclibc. It seems that previous uclibc fixes have been merged, but now I'm having a different issue. I'm building with: gcc-4.6.2-r3 uclibc 0.9.32 --prefix=/usr --sysconfdir=/etc --with-dnet --with-icu --with-procps --with-x --without-kernel-modules --without-pam /bin/bash ../libtool --tag=CC --mode=link ccache gcc -Wno-unused-but-set-variable -Wall -Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas -Wno-uninitialized -Wno-unused-but-set-variable -Wl,-z,defs -Wl,-lc -Wl,--as-needed -o libvmtools.la -rpath /usr/lib libvmtools_la-i18n.lo libvmtools_la-monotonicTimer.lo libvmtools_la-signalSource.lo libvmtools_la-vmtools.lo libvmtools_la-vmtoolsConfig.lo libvmtools_la-vmtoolsLog.lo libvmtools_la-vmxLogger.lo libvmtools_la-stub-log.lo ../lib/lock/libLock.la ../lib/backdoor/libBackdoor.la ../lib/dict/libDict.la ../lib/dynxdr/libDynxdr.la ../lib/err/libErr.la ../lib/file/libFile.la ../lib/glibUtils/libGlibUtils.la ../lib/guestApp/libGuestApp.la ../lib/guestRpc/libGuestRpc.la ../lib/message/libMessage.la ../lib/netUtil/libNetUtil.la ../lib/panic/libPanic.la ../lib/procMgr/libProcMgr.la ../lib/rpcChannel/libRpcChannel.la ../lib/rpcIn/libRpcIn.la ../lib/rpcOut/libRpcOut.la ../lib/rpcVmx/libRpcVmx.la ../lib/string/libString.la ../lib/syncDriver/libSyncDriver.la ../lib/system/libSystem.la ../lib/stubs/libStubsCS.la ../lib/unicode/libUnicode.la ../lib/user/libUser.la ../lib/vmCheck/libVmCheck.la ../lib/vmSignal/libVmSignal.la ../lib/wiper/libWiper.la ../lib/misc/libMisc.la -ldl -lrt -liconv -lcrypt -lpthread -lglib-2.0 -lintl -lpthread -ldl -lm -L/usr/lib -licui18n -licuuc -licudata -lpthread -ldl -lm libtool: link: ccache gcc -shared .libs/libvmtools_la-i18n.o .libs/libvmtools_la-monotonicTimer.o .libs/libvmtools_la-signalSource.o .libs/libvmtools_la-vmtools.o .libs/libvmtools_la-vmtoolsConfig.o .libs/libvmtools_la-vmtoolsLog.o .libs/libvmtools_la-vmxLogger.o .libs/libvmtools_la-stub-log.o -Wl,--whole-archive ../lib/lock/.libs/libLock.a ../lib/backdoor/.libs/libBackdoor.a ../lib/dict/.libs/libDict.a ../lib/dynxdr/.libs/libDynxdr.a ../lib/err/.libs/libErr.a ../lib/file/.libs/libFile.a ../lib/glibUtils/.libs/libGlibUtils.a ../lib/guestApp/.libs/libGuestApp.a ../lib/guestRpc/.libs/libGuestRpc.a ../lib/message/.libs/libMessage.a ../lib/netUtil/.libs/libNetUtil.a ../lib/panic/.libs/libPanic.a ../lib/procMgr/.libs/libProcMgr.a ../lib/rpcChannel/.libs/libRpcChannel.a ../lib/rpcIn/.libs/libRpcIn.a ../lib/rpcOut/.libs/libRpcOut.a ../lib/rpcVmx/.libs/libRpcVmx.a ../lib/string/.libs/libString.a ../lib/syncDriver/.libs/libSyncDriver.a ../lib/system/.libs/libSystem.a ../lib/stubs/.libs/libStubsCS.a ../lib/unicode/.libs/libUnicode.a ../lib/user/.libs/libUser.a ../lib/vmCheck/.libs/libVmCheck.a ../lib/vmSignal/.libs/libVmSignal.a ../lib/wiper/.libs/libWiper.a ../lib/misc/.libs/libMisc.a -Wl,--no-whole-archive -lrt -liconv -lcrypt -lglib-2.0 -lintl -L/usr/lib -licui18n -licuuc -licudata -lpthread -ldl -lm -Wl,-z -Wl,defs -Wl,-lc -Wl,--as-needed -Wl,-soname -Wl,libvmtools.so.0 -o .libs/libvmtools.so.0.0.0 ../lib/misc/.libs/libMisc.a(msgList.o): In function `MsgList_ToString': msgList.c:(.text+0x65f): undefined reference to `MsgFmt_Asprintf' ../lib/misc/.libs/libMisc.a(msgList.o): In function `MsgList_Log': msgList.c:(.text+0x73f): undefined reference to `MsgFmt_Asprintf' collect2: ld returned 1 exit status make[1]: *** [libvmtools.la] Error 1 make[1]: Leaving directory `/home/clandmeter/aports/main/open-vm-tools/src/open-vm-tools-2011.11.20-535097/libvmtools' make: *** [all-recursive] Error 1 ---------------------------------------------------------------------- Comment By: https://www.google.com/accounts () Date: 2012-01-17 02:44 Message: Here's how I'm currently building it on uclibc/buildroot: ############################################################# # # openvmtools # ############################################################# OPENVMTOOLS_VERSION = 2011.06.27-437995 #OPENVMTOOLS_VERSION = 2011.09.23-491607 OPENVMTOOLS_SOURCE = open-vm-tools-${OPENVMTOOLS_VERSION}.tar.gz OPENVMTOOLS_SITE = http://$(BR2_SOURCEFORGE_MIRROR).dl.sourceforge.net/sourceforge/open-vm-tools OPENVMTOOLS_INSTALL_STAGING = NO OPENVMTOOLS_INSTALL_TARGET = YES OPENVMTOOLS_CONF_OPT = --with-kernel-modules --with-linuxdir=$(BUILD_DIR)/linux-$(LINUX_HEADERS_VERSION) --without-pam --without-x LDFLAGS="-L${TARGET_DIR}/lib -L${TARGET_DIR}/usr/lib" --without-x --without-icu CUSTOM_DNET_CPPFLAGS="-I${TARGET_DIR}/usr/include" OPENVMTOOLS_MAKE_OPT="CFLAGS+=-liconv -DNO_FLOATING_POINT -DBUSYBOX_SHUTDOWN" OPENVMTOOLS_AUTORECONF = YES OPENVMTOOLS_DEPENDENCIES = procps libdnet gettext libdnet linux ifneq ($(BR2_TOOLCHAIN_BUILDROOT_INET_IPV6),y) OPENVMTOOLS_CONF_OPT += --without-dnet endif define OPENVMTOOLS_MOVE_KERNEL_MODULES mkdir -p ${TARGET_DIR}/modules/${LINUX_HEADERS_VERSION}/kernel cp -r ${TARGET_DIR}/root/buildroot-${BR2_VERSION}/output/build/linux-${LINUX_HEADERS_VERSION}/kernel/* ${TARGET_DIR}/lib/modules/${LINUX_HEADERS_VERSION}/kernel rm -rf ${TARGET_DIR}/root/ endef define OPENVMTOOLS_PRE_CONFIGURE_FIX mkdir -p ${BUILD_DIR}/linux-${LINUX_HEADERS_VERSION}/build ln -f -s ${BUILD_DIR}/linux-${LINUX_HEADERS_VERSION}/include ${BUILD_DIR}/linux-${LINUX_HEADERS_VERSION}/build/include cp -f ${BUILD_DIR}/libdnet-${LIBDNET_VERSION}/dnet-config ${TARGET_DIR}/usr/bin endef OPENVMTOOLS_POST_INSTALL_TARGET_HOOKS += OPENVMTOOLS_MOVE_KERNEL_MODULES OPENVMTOOLS_PRE_CONFIGURE_HOOKS += OPENVMTOOLS_PRE_CONFIGURE_FIX $(eval $(call AUTOTARGETS,package,openvmtools)) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3459926&group_id=204462 |
|
From: SourceForge.net <no...@so...> - 2012-01-09 14:37:11
|
Tracker item #3471380, was opened at 2012-01-09 06:36 Message generated for change (Settings changed) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3471380&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: https://www.google.com/accounts () Assigned to: Nobody/Anonymous (nobody) >Summary: vmxnet 2011.12.20.562307 failed to compile for 3.1.6 kernel Initial Comment: make[1]: Entering directory `/usr/src/linux-3.1.6-gentoo' CC [M] /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.o /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c: In function 'vmxnet_map_pkt': /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c:2045:2: error: implicit declaration of function 'skb_frag_size' /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c:2057:42: error: request for member 'p' in something not a structure or union /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c:2087:36: error: request for member 'p' in something not a structure or union /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c: In function 'vmxnet_rx_frags': /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c:2589:10: error: implicit declaration of function '__skb_frag_set_page' make[2]: *** [/var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.o] Error 1 make[1]: *** [_module_/var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet] Error 2 make[1]: Leaving directory `/usr/src/linux-3.1.6-gentoo' make: *** [vmxnet.ko] Error 2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3471380&group_id=204462 |
|
From: SourceForge.net <no...@so...> - 2012-01-09 14:36:10
|
Tracker item #3471380, was opened at 2012-01-09 06:36 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3471380&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: https://www.google.com/accounts () Assigned to: Nobody/Anonymous (nobody) Summary: vmxnet failed to compile for 3.1.6 kernel Initial Comment: make[1]: Entering directory `/usr/src/linux-3.1.6-gentoo' CC [M] /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.o /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c: In function 'vmxnet_map_pkt': /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c:2045:2: error: implicit declaration of function 'skb_frag_size' /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c:2057:42: error: request for member 'p' in something not a structure or union /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c:2087:36: error: request for member 'p' in something not a structure or union /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c: In function 'vmxnet_rx_frags': /var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c:2589:10: error: implicit declaration of function '__skb_frag_set_page' make[2]: *** [/var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.o] Error 1 make[1]: *** [_module_/var/tmp/portage/app-emulation/open-vm-tools-kmod-2011.12.20.562307/work/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet] Error 2 make[1]: Leaving directory `/usr/src/linux-3.1.6-gentoo' make: *** [vmxnet.ko] Error 2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3471380&group_id=204462 |
|
From: Danxiang Li <dan...@gm...> - 2011-12-31 05:06:38
|
/bin/sh ../libtool --mode=install /usr/bin/install -c
libvmtools.la'/usr/local/lib'
libtool: install: /usr/bin/install -c .libs/libvmtools.so.0.0.0
/usr/local/lib/libvmtools.so.0.0.0
libtool: install: (cd /usr/local/lib && { ln -s -f libvmtools.so.0.0.0
libvmtools.so.0 || { rm -f libvmtools.so.0 && ln -s libvmtools.so.0.0.0
libvmtools.so.0; }; })
libtool: install: (cd /usr/local/lib && { ln -s -f libvmtools.so.0.0.0
libvmtools.so || { rm -f libvmtools.so && ln -s libvmtools.so.0.0.0
libvmtools.so; }; })
libtool: install: /usr/bin/install -c .libs/libvmtools.lai /usr/local/lib/
libvmtools.la
libtool: install: /usr/bin/install -c .libs/libvmtools.a
/usr/local/lib/libvmtools.a
libtool: install: chmod 644 /usr/local/lib/libvmtools.a
libtool: install: ranlib /usr/local/lib/libvmtools.a
libtool: finish: PATH="/usr/sbin:/bin:/usr/bin:/sbin:/sbin" ldconfig -n
/usr/local/lib
----------------------------------------------------------------------
Libraries have been installed in:
/usr/local/lib
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,-rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/remote/openvmtools/libvmtools'
make[1]: Leaving directory `/remote/openvmtools/libvmtools'
Making install in libhgfs
make[1]: Entering directory `/remote/openvmtools/libhgfs'
make[2]: Entering directory `/remote/openvmtools/libhgfs'
test -z "/usr/local/lib" || /bin/mkdir -p "/usr/local/lib"
/bin/sh ../libtool --mode=install /usr/bin/install -c
libhgfs.la'/usr/local/lib'
libtool: install: warning: relinking `libhgfs.la'
libtool: install: (cd /remote/openvmtools/libhgfs; /bin/sh
/remote/openvmtools/libtool --tag CC --mode=relink gcc -g -O2 -Wall
-Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing
-Wno-unknown-pragmas -Wno-uninitialized -Wno-unused-but-set-variable
-Wl,-z,defs -Wl,-lc -o libhgfs.la -rpath /usr/local/lib
libhgfs_la-hgfslib.lo ../lib/hgfs/libHgfs.la
../lib/hgfsHelper/libHgfsHelper.la ../lib/hgfsServer/libHgfsServer.la
../lib/hgfsServerManagerGuest/libHgfsServerManagerGuest.la
../lib/hgfsServerPolicyGuest/libHgfsServerPolicyGuest.la -lglib-2.0
-pthread -lgthread-2.0 -lrt -lglib-2.0 /remote/openvmtools/libvmtools/
libvmtools.la -lglib-2.0 )
mv: cannot move `libhgfs.so.0.0.0' to `libhgfs.so.0.0.0U': Permission denied
libtool: install: error: relink `libhgfs.la' with the above command before
installing it
make[2]: *** [install-libLTLIBRARIES] Error 1
make[2]: Leaving directory `/remote/openvmtools/libhgfs'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/remote/openvmtools/libhgfs'
make: *** [install-recursive] Error
|
|
From: SourceForge.net <no...@so...> - 2011-12-26 13:23:35
|
Tracker item #3457581, was opened at 2011-12-11 14:21 Message generated for change (Comment added) made by zbiggy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3457581&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: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Zbigniew Luszpinski (zbiggy) Assigned to: Nobody/Anonymous (nobody) Summary: vmxnet fails to compile on kernels 3.0 nad later Initial Comment: Hello, vmxnet kernel module fails to build on kernels 3.0 and later up to and including latest 3.2rc5. Here is compile error: /usr/src/open-vm-tools-2011.11.20-535097/modules/linux/vmxnet/vmxnet.c: In function 'vmxnet_probe_device': /usr/src/open-vm-tools-2011.11.20-535097/modules/linux/vmxnet/vmxnet.c:992:7: error: unknown field 'ndo_set_multicast_list' specified in initializer /usr/src/open-vm-tools-2011.11.20-535097/modules/linux/vmxnet/vmxnet.c:992:7: warning: initialization from incompatible pointer type [enabled by default] /usr/src/open-vm-tools-2011.11.20-535097/modules/linux/vmxnet/vmxnet.c:992:7: warning: (near initialization for 'vmxnet_netdev_ops.ndo_vlan_rx_add_vid') [enabled by default] /usr/src/open-vm-tools-2011.11.20-535097/modules/linux/vmxnet/vmxnet.c: In function 'vmxnet_map_pkt': /usr/src/open-vm-tools-2011.11.20-535097/modules/linux/vmxnet/vmxnet.c:2047:32: error: incompatible type for argument 2 of 'pci_map_page' include/asm-generic/pci-dma-compat.h:43:1: note: expected 'struct page *' but argument is of type 'struct <anonymous>' /usr/src/open-vm-tools-2011.11.20-535097/modules/linux/vmxnet/vmxnet.c:2066:26: error: incompatible type for argument 2 of 'pci_map_page' include/asm-generic/pci-dma-compat.h:43:1: note: expected 'struct page *' but argument is of type 'struct <anonymous>' /usr/src/open-vm-tools-2011.11.20-535097/modules/linux/vmxnet/vmxnet.c: In function 'vmxnet_rx_frags': /usr/src/open-vm-tools-2011.11.20-535097/modules/linux/vmxnet/vmxnet.c:2561:48: error: incompatible types when assigning to type 'struct <anonymous>' from type 'struct page *' make[4]: *** [/usr/src/open-vm-tools-2011.11.20-535097/modules/linux/vmxnet/vmxnet.o] Error 1 make[3]: *** [_module_/usr/src/open-vm-tools-2011.11.20-535097/modules/linux/vmxnet] Error 2 make[2]: *** [vmxnet.ko] Error 2 make[1]: *** [vmxnet] Error 2 make: *** [all-recursive] Error 1 I use gcc 4.6.2, kernel 3.2rc5 from kernel,org and latest open-vm-tools. ---------------------------------------------------------------------- >Comment By: Zbigniew Luszpinski (zbiggy) Date: 2011-12-26 05:23 Message: Fixed in open-vm-tools-2011.12.20-562307.tar.gz ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3457581&group_id=204462 |
|
From: Reindl H. <h.r...@th...> - 2011-12-23 14:31:09
|
today i recompiled 2011.11.20 sucessfull for 2.6.41.6-1.fc15.x86_64
so the kernel and build-environemnt is OK
after that i saw 2011.12.20 is out and should contain the fixes
for Fedora 2.6.4x and vsyc and the two patches needed before are
no longer matching which confirms this
but it refuses to build :-(
would be nice to have configure-options to not build
vmhgfs, vmxnet2 at all which are not needed/wanted on
server-environemnts (ESXi) with modern kernels
_____________________________
make[1]: Leaving directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/xferlogs'
Making all in modules
make[1]: Entering directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules'
make VM_UNAME=2.6.41.6-1.fc15.x86_64 MV=mv RM=rm \
OVT_SOURCE_DIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307 \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux \
-C "/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmsync"
make VM_UNAME=2.6.41.6-1.fc15.x86_64 MV=mv RM=rm \
OVT_SOURCE_DIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307 \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux \
-C "/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci"
make VM_UNAME=2.6.41.6-1.fc15.x86_64 MV=mv RM=rm \
OVT_SOURCE_DIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307 \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux \
-C "/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock"
Using 2.6.x kernel build system.
Using 2.6.x kernel build system.
Using 2.6.x kernel build system.
make[2]: Entering directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci'
make -C /lib/modules/2.6.41.6-1.fc15.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux modules
Building VMCI Sockets without VMCI module symbols.
make[2]: Entering directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock'
make -C /lib/modules/2.6.41.6-1.fc15.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux modules
make[2]: Entering directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmsync'
make -C /lib/modules/2.6.41.6-1.fc15.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux modules
make[3]: Entering directory `/usr/src/kernels/2.6.41.6-1.fc15.x86_64'
make[3]: Entering directory `/usr/src/kernels/2.6.41.6-1.fc15.x86_64'
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/linux/driver.o
make[3]: Entering directory `/usr/src/kernels/2.6.41.6-1.fc15.x86_64'
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmsync/sync.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/linux/af_vsock.o
LD [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmsync/vmsync.o
Building modules, stage 2.
MODPOST 1 modules
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/linux/vmciKernelIf.o
CC /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmsync/vmsync.mod.o
LD [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmsync/vmsync.ko
make[3]: Leaving directory `/usr/src/kernels/2.6.41.6-1.fc15.x86_64'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux postbuild
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/linux/vsockAddr.o
make[3]: Entering directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmsync'
make[3]: `postbuild' is up to date.
make[3]: Leaving directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmsync'
cp -f vmsync.ko ./../vmsync.o
make[2]: Leaving directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmsync'
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/common/vmciDatagram.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/common/vmciDriver.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/common/vmciResource.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/linux/notifyQState.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/common/vmciRoute.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/common/vmciContext.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/common/vmciPageChannel.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/linux/util.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/common/vmciHashtable.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/common/vmciEvent.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/linux/stats.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/common/vmciQueuePair.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/common/vmciQPair.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/linux/notify.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/common/vmciDoorbell.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/driverLog.o
make VM_UNAME=2.6.41.6-1.fc15.x86_64 MV=mv RM=rm \
OVT_SOURCE_DIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307 \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux \
-C "/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet"
Using 2.6.x kernel build system.
make[2]: Entering directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet'
make -C /lib/modules/2.6.41.6-1.fc15.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux modules
LD [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/vmci.o
Building modules, stage 2.
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/driverLog.o
MODPOST 1 modules
CC /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/vmci.mod.o
LD [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.o
LD [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/vmci.ko
Building modules, stage 2.
make[3]: Leaving directory `/usr/src/kernels/2.6.41.6-1.fc15.x86_64'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux postbuild
make[3]: Entering directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci'
cp -f /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci/./Module.symvers
/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/VMwareVMCIModule.symvers
make[3]: Leaving directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci'
cp -f vmci.ko ./../vmci.o
make[2]: Leaving directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmci'
make VM_UNAME=2.6.41.6-1.fc15.x86_64 MV=mv RM=rm \
OVT_SOURCE_DIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307 \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux \
-C "/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock"
Using 2.6.x kernel build system.
make[3]: Entering directory `/usr/src/kernels/2.6.41.6-1.fc15.x86_64'
MODPOST 1 modules
WARNING: "VMCIDatagram_CreateHnd"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIEvent_Subscribe"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_ProduceBufReady"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCI_DeviceGet"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_DequeueV"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_EnqueueV"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCI_DeviceRelease"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_GetConsumeIndexes"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_PeekV"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_Detach"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIDatagram_CreateHndPriv"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_GetProduceIndexes"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_ProduceFreeSpace"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_Alloc"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIContext_GetPrivFlags"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_ConsumeBufReady"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIQPair_ConsumeFreeSpace"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCI_GetContextID"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIDatagram_Send"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCI_IsContextOwner"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
WARNING: "VMCIEvent_Unsubscribe"
[/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko] undefined!
CC /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.mod.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.o
make[2]: Entering directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock'
make -C /lib/modules/2.6.41.6-1.fc15.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux modules
LD [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock/vsock.ko
make[3]: Leaving directory `/usr/src/kernels/2.6.41.6-1.fc15.x86_64'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux postbuild
make[3]: Entering directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock'
make[3]: `postbuild' is up to date.
make[3]: Leaving directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock'
cp -f vsock.ko ./../vsock.o
make[2]: Leaving directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vsock'
make VM_UNAME=2.6.41.6-1.fc15.x86_64 MV=mv RM=rm \
OVT_SOURCE_DIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307 \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux \
-C "/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs"
Using 2.6.x kernel build system.
/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c: In function
'vmxnet_map_pkt':
/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c:2045:2: error:
implicit declaration of function 'skb_frag_size' [-Werror=implicit-function-declaration]
/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c:2057:42: error:
request for member 'p' in something not a structure or union
/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c:2087:36: error:
request for member 'p' in something not a structure or union
/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c: In function
'vmxnet_rx_frags':
/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.c:2589:10: error:
implicit declaration of function '__skb_frag_set_page' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[4]: *** [/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet/vmxnet.o] Error 1
make[3]: *** [_module_/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet] Error 2
make[3]: Leaving directory `/usr/src/kernels/2.6.41.6-1.fc15.x86_64'
make[2]: *** [vmxnet.ko] Error 2
make[2]: Leaving directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmxnet'
make[1]: *** [vmxnet] Error 2
make[1]: *** Waiting for unfinished jobs....
Building vmhgfs with VMCI module symbols.
make[2]: Entering directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs'
cp -f /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/VMwareVMCIModule.symvers
./Module.symvers
make -C /lib/modules/2.6.41.6-1.fc15.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux modules
make[3]: Entering directory `/usr/src/kernels/2.6.41.6-1.fc15.x86_64'
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock/linux/filesystem.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock/linux/file.o
make[3]: Entering directory `/usr/src/kernels/2.6.41.6-1.fc15.x86_64'
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock/linux/module.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/dir.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock/linux/super.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock/linux/control.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock/linux/inode.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/request.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock/linux/dentry.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock/block.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/filesystem.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock/stubs.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/stubs.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/tcp.o
LD [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock/vmblock.o
Building modules, stage 2.
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/link.o
MODPOST 1 modules
CC /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock/vmblock.mod.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/transport.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/module.o
LD [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock/vmblock.ko
make[3]: Leaving directory `/usr/src/kernels/2.6.41.6-1.fc15.x86_64'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux postbuild
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/file.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/super.o
make[3]: Entering directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock'
make[3]: `postbuild' is up to date.
make[3]: Leaving directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock'
cp -f vmblock.ko ./../vmblock.o
make[2]: Leaving directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmblock'
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/vmci.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/bdhandler.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/fsutil.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/page.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/inode.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/dentry.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/backdoor.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/backdoorGcc64.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/cpName.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/cpNameLinux.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/cpNameLite.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/hgfsEscape.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/hgfsUtil.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/hgfsBd.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/message.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/rpcout.o
CC [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/kernelStubsLinux.o
LD [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/vmhgfs.mod.o
LD [M] /home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs/vmhgfs.ko
make[3]: Leaving directory `/usr/src/kernels/2.6.41.6-1.fc15.x86_64'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR=/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux postbuild
make[3]: Entering directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs'
make[3]: `postbuild' is up to date.
make[3]: Leaving directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs'
cp -f vmhgfs.ko ./../vmhgfs.o
make[2]: Leaving directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules/linux/vmhgfs'
make[1]: Leaving directory `/home/builduser/rpmbuild/BUILD/open-vm-tools-2011.12.20-562307/modules'
make: *** [all-recursive] Error 1
|
|
From: SourceForge.net <no...@so...> - 2011-12-19 23:00:44
|
Tracker item #3461175, was opened at 2011-12-16 17:17 Message generated for change (Comment added) made by mvanzin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3461175&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: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Eugene Varnavsky (varnav) Assigned to: Nobody/Anonymous (nobody) Summary: FreeBSD port fails to build with GCC 4.6.3 Initial Comment: I have FreeBSD 8.2 with GCC 4.6.3 installed like it is described in handbook: http://www.freebsd.org/doc/en/articles/custom-gcc/article.html I get the following error from gcc while trying to build the port: unrecognized command line option '-fformat-extensions' ---------------------------------------------------------------------- >Comment By: Marcelo Vanzin (mvanzin) Date: 2011-12-19 15:00 Message: My FreeBSD 7.1 VM has this in /sys/conf/kern.mk: CWARNFLAGS?= -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes \ -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual \ ${_wundef} ${_Wno_pointer_sign} -fformat-extensions So the flag is coming from FreeBSD's makefiles, not ours. If the new compiler doesn't support it, I guess they have to fix the instructions. ---------------------------------------------------------------------- Comment By: Eugene Varnavsky (varnav) Date: 2011-12-16 22:16 Message: Looks like the problem arises in making of /modules/freebsd/vmemctl/ when some files from kernel source are linked. No, it's pure setup according to instructions in handbook. I tried to add or remove CPUTYPE and CFLAGS variables in make.conf - no effect. Commenting out CC=gcc46 in make.conf helps. ---------------------------------------------------------------------- Comment By: Marcelo Vanzin (mvanzin) Date: 2011-12-16 18:27 Message: I don't see any plane in our sources where that switch is added to gcc's command line. Are you sure you don't have some local config file or env variable that has it? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3461175&group_id=204462 |
|
From: SourceForge.net <no...@so...> - 2011-12-17 06:16:16
|
Tracker item #3461175, was opened at 2011-12-16 17:17 Message generated for change (Comment added) made by varnav You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3461175&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: Eugene Varnavsky (varnav) Assigned to: Nobody/Anonymous (nobody) Summary: FreeBSD port fails to build with GCC 4.6.3 Initial Comment: I have FreeBSD 8.2 with GCC 4.6.3 installed like it is described in handbook: http://www.freebsd.org/doc/en/articles/custom-gcc/article.html I get the following error from gcc while trying to build the port: unrecognized command line option '-fformat-extensions' ---------------------------------------------------------------------- Comment By: Eugene Varnavsky (varnav) Date: 2011-12-16 22:16 Message: Looks like the problem arises in making of /modules/freebsd/vmemctl/ when some files from kernel source are linked. No, it's pure setup according to instructions in handbook. I tried to add or remove CPUTYPE and CFLAGS variables in make.conf - no effect. Commenting out CC=gcc46 in make.conf helps. ---------------------------------------------------------------------- Comment By: Marcelo Vanzin (mvanzin) Date: 2011-12-16 18:27 Message: I don't see any plane in our sources where that switch is added to gcc's command line. Are you sure you don't have some local config file or env variable that has it? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3461175&group_id=204462 |
58 messages has been excluded from this view by a project administrator.
