Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
vmware-modules-279.1 failed to build
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
dmitrio
Tux's lil' helper
Tux's lil' helper


Joined: 10 Dec 2002
Posts: 108
Location: DFW

PostPosted: Sat Dec 28, 2013 5:19 am    Post subject: vmware-modules-279.1 failed to build Reply with quote

I can not build vmware-modules-279.1
Code:

 * Package:    app-emulation/vmware-modules-279.1
 * Repository: gentoo
 * Maintainer: vmware@gentoo.org
 * USE:        amd64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     3.12.6-gentoo.2013-12-27_23-00
 * Checking for suitable kernel configuration options...
 [ ok ]
 * Checking for suitable kernel configuration options...
 [ ok ]
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/app-emulation/vmware-modules-279.1/work
>>> Preparing source in /var/tmp/portage/app-emulation/vmware-modules-279.1/work ...
 * Applying 279-makefile-kernel-dir.patch ...
 [ ok ]
 * Applying 279-makefile-include.patch ...
 [ ok ]
 * Applying 279-netdevice.patch ...
 [ ok ]
 * Applying 279-apic.patch ...
 [ ok ]
 * Applying 279-putname.patch ...
 [ ok ]
 * Applying 279-vmblock.patch ...
 [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-emulation/vmware-modules-279.1/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/app-emulation/vmware-modules-279.1/work ...
 * Preparing vmblock module
make -j2 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/usr/src/
linux
Using 2.6.x kernel build system.
make -C /usr/src/linux SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-gentoo'
  CC [M]  /var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/filesystem.o
  CC [M]  /var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/dentry.o
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/dentry.c:38:4: warning: initialization from incompatible pointer type [enabled by d
efault]
    .d_revalidate = DentryOpRevalidate,
    ^
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/dentry.c:38:4: warning: (near initialization for ‘LinkDentryOps.d_revalidate’) [ena
bled by default]
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/dentry.c:104:7: warning: passing argument 2 of ‘actualDentry->d_op->d_revalidate’ m
akes integer from pointer without a cast [enabled by default]
       return actualDentry->d_op->d_revalidate(actualDentry, nd);
       ^
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/dentry.c:104:7: note: expected ‘unsigned int’ but argument is of type ‘struct namei
data *’
  CC [M]  /var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/stubs.o
  CC [M]  /var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/file.o
  CC [M]  /var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/block.o
  CC [M]  /var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/inode.o
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/file.c:240:4: error: unknown field ‘readdir’ specified in initializer
    .readdir = FileOpReaddir,
    ^
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/file.c:240:4: warning: initialization from incompatible pointer type [enabled by default]
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/file.c:240:4: warning: (near initialization for ‘RootFileOps.owner’) [enabled by default]
/usr/src/linux-3.12.6-gentoo/scripts/Makefile.build:308: recipe for target '/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/file.o' failed
make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/file.o] Error 1
make[3]: *** Waiting for unfinished jobs....
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/inode.c:49:4: warning: initialization from incompatible pointer type [enabled by default]
    .lookup = InodeOpLookup,
    ^
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/inode.c:49:4: warning: (near initialization for ‘RootInodeOps.lookup’) [enabled by default]
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/inode.c: In function ‘InodeOpFollowlink’:
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/inode.c:224:4: error: implicit declaration of function ‘vfs_follow_link’ [-Werror=implicit-function-declaration]
    ret = vfs_follow_link(nd, iinfo->name);
    ^
cc1: some warnings being treated as errors
/usr/src/linux-3.12.6-gentoo/scripts/Makefile.build:308: recipe for target '/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/inode.o' failed
make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/inode.o] Error 1
/usr/src/linux-3.12.6-gentoo/Makefile:1228: recipe for target '_module_/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only' failed
make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-3.12.6-gentoo'
Makefile:130: recipe for target 'vmblock.ko' failed
make: *** [vmblock.ko] Error 2
 * ERROR: app-emulation/vmware-modules-279.1::gentoo failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-279.1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-emulation/vmware-modules-279.1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/app-emulation/vmware-modules-279.1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-279.1/temp/environment'.
 * Working directory: '/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmblock-only'
 * S: '/var/tmp/portage/app-emulation/vmware-modules-279.1/work'


Output for
emerge --info '=app-emulation/vmware-modules-279.1'
Code:

Portage 2.2.7 (default/linux/amd64/13.0/desktop, gcc-4.8.2, glibc-2.17, 3.12.6-gentoo.2013-12-27_23-00 x86_64)
=================================================================
                         System Settings
=================================================================
System uname: Linux-3.12.6-gentoo.2013-12-27_23-00-x86_64-Intel-R-_Core-TM-_i5_CPU_M_520_@_2.40GHz-with-gentoo-2.2
KiB Mem:     3839636 total,   2707708 free
KiB Swap:    1016828 total,   1016828 free
Timestamp of tree: Sat, 28 Dec 2013 02:15:01 +0000
ld GNU ld (GNU Binutils) 2.23.2
app-shells/bash:          4.2_p45
dev-java/java-config:     2.2.0
dev-lang/python:          2.7.6, 3.2.5-r3, 3.3.3
dev-util/cmake:           2.8.12.1-r2
dev-util/pkgconfig:       0.28
sys-apps/baselayout:      2.2
sys-apps/openrc:          0.12.4
sys-apps/sandbox:         2.6-r1
sys-devel/autoconf:       2.13, 2.69
sys-devel/automake:       1.11.6, 1.12.6, 1.14.1
sys-devel/binutils:       2.23.2
sys-devel/gcc:            4.8.2
sys-devel/gcc-config:     1.8
sys-devel/libtool:        2.4.2
sys-devel/make:           4.0-r1
sys-kernel/linux-headers: 3.12 (virtual/os-headers)
sys-libs/glibc:           2.17
Repositories: gentoo sunrise
ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="*"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=core2 -mtune=generic -Os -pipe -msse3 -msse4 -mcx16 -msahf -mpopcnt"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5.5/ext-active/ /etc/php/cgi-php5.5/ext-active/ /etc/php/cli-php5.5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-march=core2 -mtune=generic -Os -pipe -msse3 -msse4 -mcx16 -msahf -mpopcnt"
DISTDIR="/usr/portage/distfiles"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo http://mirrors.rit.edu/gentoo/ http://mirror.the-best-hosting.net"
LANG="en_US.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/var/lib/layman/sunrise"
SYNC="rsync://rsync25.us.gentoo.org/gentoo-portage"
USE="3dnowext 64bit X a52 aac acl acoustid acpi admin alsa amd64 apm atasmart bash-completion berkdb bittorrent bluetooth branding bzip2 cairo cdda cdparanoia cdr cgi cleartype cli client compress-db consolekit cracklib crypt css cups curl cxx dbus detex dhclient dmx down-root dri dts dvd dvdr emboss encode exif faac faad fading-colors fam fastcgi ffmpeg ffmpegsource firefox flac fontconfig fonts fortran gd gdbm gif gnutls gpm gstreamer gtk gtk3 gtkstyle handbook hdaps hddtemp hexen iconv icu imlib introspection iostats ipv6 jingle jpeg laptop lcms libkms libnotify libsamplerate lilo lm_sensors lua luatex lzma lzo mad md5sum memlimit midi mikmod mmx mmxext mng moc mod modplug modules mozilla mp3 mp4 mpeg mudflap multilib ncurses nls nptl nsplugin ogg opengl openmp optimized-qmake opus osdmenu pam pango passwordsave pcf pcre pdf perl plugins pm-utils pmu png policykit powersave ppds psf python python3 qt3support qt4 quicktime rar readline ru-dv ru-g ru-i ru-k scsi sdl secure-delete sensord session sftp shared-dricore shared-glapi smp sndfile speex spell sql sqlite sqlite3 sse sse2 sse3 ssl ssse3 startup-notification subversion svg symlink system-cairo system-crontab system-ffmpeg system-icu system-jpeg system-libs system-sqlite tcpd theora thinkpad threadsafe thunar tiff timidity tls tools truetype udev udisks unicode unlock-notify uploadprogress upower usb uxa v4l vcd vim vim-pager vim-syntax vorbis wav wavpack weather-xoap webdav webkit webkit2 wifi wxwidgets x264 xcb xft xml xorg xosd xscreensaver xv xvid xz zlib" ABI_X86="64" ALSA_CARDS="hda-intel usb-audio" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="evdev synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LINGUAS="en ru de" NGINX_MODULES_HTTP="access auth_basic autoindex browser charset empty_gif fastcgi gzip limit_conn limit_req map memcached referer rewrite scgi split_clients ssi upstream_ip_hash userid uwsgi auth_pam dav dav_ext fancyindex gunzip spdy" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-5" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_3" RUBY_TARGETS="ruby19 ruby18" USERLAND="GNU" VIDEO_CARDS="intel" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON


I am not sure is the error belongs to my config, gentoo related or vendor's bug.
_________________

... Leaving ground, destination is unknown,
into the darkness and far away from home,
Will your dream come true and what will you find,
when fate is your guide ...
Back to top
View user's profile Send private message
Kompi
Apprentice
Apprentice


Joined: 05 Oct 2002
Posts: 251
Location: Germany

PostPosted: Mon Dec 30, 2013 10:26 am    Post subject: Reply with quote

looks like vmware-modules-279.1 is not yet officially compatible with your very recent 3.12.x kernel version.

You may either use an older kernel or try to patch vmware-modules. Here are some open gentoo bug reports adressing issues with that kernel version where you might find patches: #488072, #483410. Maybe this patch can help too.
Back to top
View user's profile Send private message
dmitrio
Tux's lil' helper
Tux's lil' helper


Joined: 10 Dec 2002
Posts: 108
Location: DFW

PostPosted: Mon Dec 30, 2013 4:33 pm    Post subject: danke Reply with quote

excellent, thanks.
i will try to patch.
_________________

... Leaving ground, destination is unknown,
into the darkness and far away from home,
Will your dream come true and what will you find,
when fate is your guide ...
Back to top
View user's profile Send private message
padoor
Advocate
Advocate


Joined: 30 Dec 2005
Posts: 3995
Location: india

PostPosted: Wed Jan 01, 2014 11:01 am    Post subject: Reply with quote

i need some detailed istructions to apply the 3.12 patch
some one help me
thanks :)
_________________
reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name)
Back to top
View user's profile Send private message
Kompi
Apprentice
Apprentice


Joined: 05 Oct 2002
Posts: 251
Location: Germany

PostPosted: Wed Jan 01, 2014 2:58 pm    Post subject: Reply with quote

If you want to try the the ebuild patch + source code path from bug #488072 you should copy the existing vmware-modules ebuild dir into an overlay and then apply the ebuild patch to the ebuild file. Copy the source code patch to the files/ subdir.

Assuming you have a local overlay in /usr/local/portage:
Code:
mkdir -p /usr/local/portage/app-emulation
cp -dpRv /usr/portage/app-emulation/vmware-modules/ /usr/local/portage/app-emulation
cd /usr/local/portage/app-emulation/vmware-modules/
patch -p0 < [EBUILD PATCH FILENAME]
cp [VMWARE SRC PATCH FILES] /usr/local/portage/app-emulation/vmware-modules/files/


If you do not have your local overlay setup yet, you have to set the PORTDIR_OVERLAY variable in /etc/portage/make.conf to /usr/local/portage.

More info on local overlay are at: http://wiki.gentoo.org/wiki/Overlay


If you want to try a patch to the upstream source, like the patch from https://github.com/elitak/ports-2012/commit/d602a321a1e53379a6e674302b9b77f3df924a28, you could as well use the user patches dir in /etc/portage/patches. Just copy all patches that should be applied to /etc/portage/patches/app-emulation/vmware-modules/:
Code:
mkdir -p /etc/portage/patches/app-emulation/vmware-modules/
cp <DOWNLOADED PATCH FILE> /etc/portage/patches/app-emulation/vmware-modules/

See http://wiki.gentoo.org/wiki//etc/portage/patches and http://dilfridge.blogspot.de/2012/04/neat-trick-for-testing-patches-in.html for more info on that dir.


If this does not work I would suggest downgrading the kernel to a previous version for the time beeing, if you are not in desperate need for new kernel features from that version. As soon as a new virtualbox-modules version is out that is compatible, you can upgrade again. At least that way you get a stable and somewhat tested version.
Back to top
View user's profile Send private message
padoor
Advocate
Advocate


Joined: 30 Dec 2005
Posts: 3995
Location: india

PostPosted: Thu Jan 02, 2014 8:20 am    Post subject: Reply with quote

it does not bother to look at the patch either way
tried making local overlay
tried using the /etc/portage/patches
probably it needs much more than the simple ways to apply the patch
_________________
reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name)
Back to top
View user's profile Send private message
Kompi
Apprentice
Apprentice


Joined: 05 Oct 2002
Posts: 251
Location: Germany

PostPosted: Thu Jan 02, 2014 11:19 am    Post subject: Reply with quote

Does portage complain about errors in your config?

Because I forget an important step: If you have modified (patched) an ebuild, you need to update the file hashed, otherwise portage will refuse to use the ebuild. You can do so by:

Code:
ebuild digest /usr/local/portage/.../<modified ebuild file name.ebuild>


If your local overlay is properly configured (i.e. the PORTDIR_OVERLAY variable set), portage should prefer the overlay version over the portage tree one, as long as the version is bigger or equal.

If you do a:

Code:
emerge --verbose --ask vmware-modules


it should indicate using the overlay one by the suffix "::local" or "::localOverlay" after the version number. Does it show that?


Regarding the /etc/portage/patches: Did you add the /etc/portage/bashrc file as described in http://wiki.gentoo.org/wiki//etc/portage/patches? If not, add it and try again if it works.
Back to top
View user's profile Send private message
padoor
Advocate
Advocate


Joined: 30 Dec 2005
Posts: 3995
Location: india

PostPosted: Fri Jan 03, 2014 9:34 am    Post subject: Reply with quote

Code:
tux ramaswamy # mkdir -p /usr/local/portage/app-emulation
tux ramaswamy # cp -dpRv /usr/portage/app-emulation/vmware-modules/ /usr/local/portage/app-emulation
'/usr/portage/app-emulation/vmware-modules/' -> '/usr/local/portage/app-emulation/vmware-modules'
'/usr/portage/app-emulation/vmware-modules/ChangeLog' -> '/usr/local/portage/app-emulation/vmware-modules/ChangeLog'
'/usr/portage/app-emulation/vmware-modules/metadata.xml' -> '/usr/local/portage/app-emulation/vmware-modules/metadata.xml'
'/usr/portage/app-emulation/vmware-modules/vmware-modules-279.1.ebuild' -> '/usr/local/portage/app-emulation/vmware-modules/vmware-modules-279.1.ebuild'
'/usr/portage/app-emulation/vmware-modules/vmware-modules-271.2.ebuild' -> '/usr/local/portage/app-emulation/vmware-modules/vmware-modules-271.2.ebuild'
'/usr/portage/app-emulation/vmware-modules/files' -> '/usr/local/portage/app-emulation/vmware-modules/files'
'/usr/portage/app-emulation/vmware-modules/files/279-apic.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/279-apic.patch'
'/usr/portage/app-emulation/vmware-modules/files/264-jobserver.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/264-jobserver.patch'
'/usr/portage/app-emulation/vmware-modules/files/hardened.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/hardened.patch'
'/usr/portage/app-emulation/vmware-modules/files/264-makefile-include.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/264-makefile-include.patch'
'/usr/portage/app-emulation/vmware-modules/files/271-putname.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/271-putname.patch'
'/usr/portage/app-emulation/vmware-modules/files/264-3.2.0.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/264-3.2.0.patch'
'/usr/portage/app-emulation/vmware-modules/files/271-apic.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/271-apic.patch'
'/usr/portage/app-emulation/vmware-modules/files/264-newline.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/264-newline.patch'
'/usr/portage/app-emulation/vmware-modules/files/264-d-make-root.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/264-d-make-root.patch'
'/usr/portage/app-emulation/vmware-modules/files/279-hardened.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/279-hardened.patch'
'/usr/portage/app-emulation/vmware-modules/files/279-netdevice.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/279-netdevice.patch'
'/usr/portage/app-emulation/vmware-modules/files/264-netdevice.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/264-netdevice.patch'
'/usr/portage/app-emulation/vmware-modules/files/279-putname.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/279-putname.patch'
'/usr/portage/app-emulation/vmware-modules/files/264-3.10.0.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/264-3.10.0.patch'
'/usr/portage/app-emulation/vmware-modules/files/264-putname.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/264-putname.patch'
'/usr/portage/app-emulation/vmware-modules/files/279-vmblock.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/279-vmblock.patch'
'/usr/portage/app-emulation/vmware-modules/files/264-3.8.0.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/264-3.8.0.patch'
'/usr/portage/app-emulation/vmware-modules/files/264-makefile-kernel-dir.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/264-makefile-kernel-dir.patch'
'/usr/portage/app-emulation/vmware-modules/files/271-vmmon.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/271-vmmon.patch'
'/usr/portage/app-emulation/vmware-modules/files/271-netdevice.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/271-netdevice.patch'
'/usr/portage/app-emulation/vmware-modules/files/271-makefile-kernel-dir.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/271-makefile-kernel-dir.patch'
'/usr/portage/app-emulation/vmware-modules/files/279-makefile-kernel-dir.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/279-makefile-kernel-dir.patch'
'/usr/portage/app-emulation/vmware-modules/files/271-3.10.0.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/271-3.10.0.patch'
'/usr/portage/app-emulation/vmware-modules/files/279-makefile-include.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/279-makefile-include.patch'
'/usr/portage/app-emulation/vmware-modules/files/264-apic.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/264-apic.patch'
'/usr/portage/app-emulation/vmware-modules/files/271-makefile-include.patch' -> '/usr/local/portage/app-emulation/vmware-modules/files/271-makefile-include.patch'
'/usr/portage/app-emulation/vmware-modules/vmware-modules-264.5.ebuild' -> '/usr/local/portage/app-emulation/vmware-modules/vmware-modules-264.5.ebuild'
'/usr/portage/app-emulation/vmware-modules/Manifest' -> '/usr/local/portage/app-emulation/vmware-modules/Manifest'
'/usr/portage/app-emulation/vmware-modules/vmware-modules-279.0.ebuild' -> '/usr/local/portage/app-emulation/vmware-modules/vmware-modules-279.0.ebuild'
tux ramaswamy # cd /usr/local/portage/app-emulation/vmware-modules/
tux vmware-modules # cp /home/ramaswamy/279-vmblock-3.12.patch /usr/local/portage/app-emulation/vmware-modules/files/
tux vmware-modules # ebuild digest vmware-modules-test.ebuild
ebuild: digest: does not end with '.ebuild'
tux vmware-modules # ebuild digest vmware-modules-test       
ebuild: digest: does not end with '.ebuild'
tux vmware-modules # ebuild digest vmware-modules-test.digest
ebuild: digest: does not end with '.ebuild'
tux vmware-modules # ebuild digest vmware-modules.digest
ebuild: digest: does not end with '.ebuild'
tux vmware-modules #


i am missing something in the digest
_________________
reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name)
Back to top
View user's profile Send private message
Kompi
Apprentice
Apprentice


Joined: 05 Oct 2002
Posts: 251
Location: Germany

PostPosted: Fri Jan 03, 2014 10:34 am    Post subject: Reply with quote

First you need to modify the ebuild to actually apply the patch you copied into files. In bug #483410, comment 3-4 there is a modified ebuild or a patch to modify the ebuild.

Then you have to give the "ebuild digest" an existing ebuild file with a valid version. "vmware-modules-test.ebuild" will not work. Just use the ebuild with the leatest version you just copied from the portage tree, modify it to apply the patch you copied to files/, then call a "ebuild digest vmware-modules-<VER>.ebuild" on that ebuild file.
Back to top
View user's profile Send private message
padoor
Advocate
Advocate


Joined: 30 Dec 2005
Posts: 3995
Location: india

PostPosted: Sat Jan 04, 2014 2:22 pm    Post subject: Reply with quote

Code:
tux vmware-modules # dir files                               
264-3.10.0.patch          271-makefile-kernel-dir.patch
264-3.2.0.patch             271-netdevice.patch
264-3.8.0.patch             271-putname.patch
264-apic.patch             271-vmmon.patch
264-d-make-root.patch          279-apic.patch
264-jobserver.patch          279-hardened.patch
264-makefile-include.patch     279-makefile-include.patch
264-makefile-kernel-dir.patch  279-makefile-kernel-dir.patch
264-netdevice.patch          279-netdevice.patch
264-newline.patch          279-putname.patch
264-putname.patch          279-vmblock-3.11.patch
271-3.10.0.patch          279-vmblock-3.12.patch
271-apic.patch             279-vmblock.patch
271-makefile-include.patch     hardened.patch
tux vmware-modules # dir
ChangeLog  metadata.xml         vmware-modules-279.0.ebuild
Manifest   vmware-modules-264.5.ebuild   vmware-modules-279.1.ebuild
files      vmware-modules-271.2.ebuild
tux vmware-modules # ebuild vmware-modules-279.1.ebuild digest
!!! Repository 'x-portage' is missing masters attribute in '/usr/local/portage/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility
/usr/local/portage/app-emulation/vmware-modules/vmware-modules-279.1.ebuild: line 86: warning: here-document at line 79 delimited by end-of-file (wanted `EOF')
/usr/local/portage/app-emulation/vmware-modules/vmware-modules-279.1.ebuild: line 87: syntax error: unexpected end of file
 * ERROR: app-emulation/vmware-modules-279.1::x-portage failed (depend phase):
 *   error sourcing ebuild
 *
 * Call stack:
 *   ebuild.sh, line 545:  Called die
 * The specific snippet of code:
 *            source "$EBUILD" || die "error sourcing ebuild"
 *
 * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-279.1::x-portage'`,
 * the complete build log and the output of `emerge -pqv '=app-emulation/vmware-modules-279.1::x-portage'`.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-279.1/temp/environment'.
 * Working directory: '/usr/lib64/portage/pym'
 * S: '/var/tmp/portage/app-emulation/vmware-modules-279.1/work'
tux vmware-modules #


i have done exactly said in comment 12 https://github.com/funtoo/ports-2012/pull/5

i don't understand what is problem
what it means by x-portage ?

Code:
tux vmware-modules # uname -a
Linux tux 3.12.6-gentoo #1 SMP Sun Dec 22 19:18:51 IST 2013 x86_64 AMD E1-1200 APU with Radeon(tm) HD Graphics AuthenticAMD GNU/Linux
tux vmware-modules #


that is why i have taken from comment 12
_________________
reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name)
Back to top
View user's profile Send private message
Kompi
Apprentice
Apprentice


Joined: 05 Oct 2002
Posts: 251
Location: Germany

PostPosted: Sat Jan 04, 2014 4:36 pm    Post subject: Reply with quote

"x-portage" refers to your overlay, it is the name portage has chosen for your overlay, as you don't have one set by yourself. (which you can do by adding a file /usr/local/portage/profile/repo_name with just one line containing a custom name in it).

The first warning you see:
Code:
!!! Repository 'x-portage' is missing masters attribute in '/usr/local/portage/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility

is not really an issue. You should do as it tells you, (create a file called /usr/local/portage/metadata/layout.conf and put a line in there "masters=gentoo"), but that should not make a difference. As the message states, this is for future compatibility with portage versions that may not set this automatically anymore. It basically tells portage to use the main gentoo portage tree as "master" for this one, i.e. use eclasses of thaet tree. More info on that is here: http://wiki.gentoo.org/wiki/Repository_format/metadata/layout.conf

The actual error is this:
Code:
/usr/local/portage/app-emulation/vmware-modules/vmware-modules-279.1.ebuild: line 86: warning: here-document at line 79 delimited by end-of-file (wanted `EOF')
/usr/local/portage/app-emulation/vmware-modules/vmware-modules-279.1.ebuild: line 87: syntax error: unexpected end of file

Looks like the patch broke something while patching the ebuild file. There is probably some quot character or something at line 79 that has no closing quote. If you find the problem try to correct it and call the ebuild digest again. If not, post your patched ebuild file here.
Back to top
View user's profile Send private message
padoor
Advocate
Advocate


Joined: 30 Dec 2005
Posts: 3995
Location: india

PostPosted: Sat Jan 04, 2014 5:22 pm    Post subject: Reply with quote

vmware-modules / files / 279-vmblock-3.11.patch

Code:
--- a/vmblock-only/linux/file.c
+++ b/vmblock-only/linux/file.c
@@ -38,46 +38,6 @@ typedef u64 inode_num_t;
 typedef ino_t inode_num_t;
 #endif
 
-/* Specifically for our filldir_t callback */
-typedef struct FilldirInfo {
-   filldir_t filldir;
-   void *dirent;
-} FilldirInfo;
-
-
-/*
- *----------------------------------------------------------------------------
- *
- * Filldir --
- *
- *    Callback function for readdir that we use in place of the one provided.
- *    This allows us to specify that each dentry is a symlink, but pass through
- *    everything else to the original filldir function.
- *
- * Results:
- *    Original filldir's return value.
- *
- * Side effects:
- *    Directory information gets copied to user's buffer.
- *
- *----------------------------------------------------------------------------
- */
-
-static int
-Filldir(void *buf,              // IN: Dirent buffer passed from FileOpReaddir
-        const char *name,       // IN: Dirent name
-        int namelen,            // IN: len of dirent's name
-        loff_t offset,          // IN: Offset
-        inode_num_t ino,        // IN: Inode number of dirent
-        unsigned int d_type)    // IN: Type of file
-{
-   FilldirInfo *info = buf;
-
-   /* Specify DT_LNK regardless */
-   return info->filldir(info->dirent, name, namelen, offset, ino, DT_LNK);
-}
-
-
 /* File operations */
 
 /*
@@ -166,11 +126,10 @@ FileOpOpen(struct inode *inode,  // IN
 
 static int
 FileOpReaddir(struct file *file,  // IN
-              void *dirent,       // IN
-              filldir_t filldir)  // IN
+              struct dir_context *ctx)  // IN
 {
    int ret;
-   FilldirInfo info;
+
    struct file *actualFile;
 
    if (!file) {
@@ -184,12 +143,10 @@ FileOpReaddir(struct file *file,  // IN
       return -EINVAL;
    }
 
-   info.filldir = filldir;
-   info.dirent = dirent;
-
-   actualFile->f_pos = file->f_pos;
-   ret = vfs_readdir(actualFile, Filldir, &info);
-   file->f_pos = actualFile->f_pos;
+   /* Ricky Wong Yung Fei:
+    * Manipulation of pos is now handled internally by iterate_dir().
+    */
+   ret = iterate_dir(actualFile, ctx);
 
    return ret;
 }
@@ -237,7 +194,7 @@ FileOpRelease(struct inode *inode, // IN
 
 
 struct file_operations RootFileOps = {
-   .readdir = FileOpReaddir,
+   .iterate = FileOpReaddir,
    .open    = FileOpOpen,
    .release = FileOpRelease,
 };




vmware-modules / files / 279-vmblock-3.12.patch

Code:
--- a/vmblock-only/linux/control.c        2013-10-03 04:29:47.471339204 -0400
+++ b/vmblock-only/linux/control.c        2013-10-03 04:31:56.607334636 -0400
@@ -283,7 +283,7 @@
    int i;
    int retval;
 
-   name = getname(buf);
+   name = (char*)getname(buf)->name;
    if (IS_ERR(name)) {
       return PTR_ERR(name);
    }
--- a/vmblock-only/linux/dentry.c        2013-10-03 04:29:47.471339204 -0400
+++ b/vmblock-only/linux/dentry.c        2013-10-03 04:31:56.607334636 -0400
@@ -32,7 +32,7 @@
 #include "block.h"
 
 
-static int DentryOpRevalidate(struct dentry *dentry, struct nameidata *nd);
+static int DentryOpRevalidate(struct dentry *dentry, unsigned int flags);
 
 struct dentry_operations LinkDentryOps = {
    .d_revalidate = DentryOpRevalidate,
@@ -60,7 +60,7 @@
 
 static int
 DentryOpRevalidate(struct dentry *dentry,  // IN: dentry revalidating
-                   struct nameidata *nd)   // IN: lookup flags & intent
+                   unsigned int flags)     // IN: lookup flags & intent
 {
    VMBlockInodeInfo *iinfo;
    struct nameidata actualNd;
@@ -101,7 +101,7 @@
    if (actualDentry &&
        actualDentry->d_op &&
        actualDentry->d_op->d_revalidate) {
-      return actualDentry->d_op->d_revalidate(actualDentry, nd);
+      return actualDentry->d_op->d_revalidate(actualDentry, flags);
    }
 
    if (compat_path_lookup(iinfo->name, 0, &actualNd)) {
--- a/vmblock-only/linux/inode.c        2013-10-03 04:29:47.471339204 -0400
+++ b/vmblock-only/linux/inode.c        2013-10-03 04:31:56.607334636 -0400
@@ -36,7 +36,7 @@
 
 /* Inode operations */
 static struct dentry *InodeOpLookup(struct inode *dir,
-                                    struct dentry *dentry, struct nameidata *nd);
+                                    struct dentry *dentry, unsigned int flags);
 static int InodeOpReadlink(struct dentry *dentry, char __user *buffer, int buflen);
 #if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 13)
 static void *InodeOpFollowlink(struct dentry *dentry, struct nameidata *nd);
@@ -75,7 +75,7 @@
 static struct dentry *
 InodeOpLookup(struct inode *dir,      // IN: parent directory's inode
               struct dentry *dentry,  // IN: dentry to lookup
-              struct nameidata *nd)   // IN: lookup intent and information
+              unsigned int flags)     // IN: lookup intent and information
 {
    char *filename;
    struct inode *inode;
@@ -221,7 +221,7 @@
       goto out;
    }
 
-   ret = vfs_follow_link(nd, iinfo->name);
+   nd_set_link(nd, iinfo->name);
 
 out:
 #if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 13)


vmware-modules / vmware-modules-279.1.ebuild[/code]

Code:
# Copyright 1999-2013 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/app-emulation/vmware-modules/vmware-modules-279.1.ebuild,v 1.1 2013/11/06 23:08:20 dilfridge Exp $

EAPI=5

inherit eutils flag-o-matic linux-info linux-mod user versionator udev

PV_MAJOR=$(get_major_version)
PV_MINOR=$(get_version_component_range 2)

DESCRIPTION="VMware kernel modules"
HOMEPAGE="http://www.vmware.com/"

SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~amd64 ~x86"
IUSE="pax_kernel"

RDEPEND=""
DEPEND="${RDEPEND}
        || ( =app-emulation/vmware-player-6.0.${PV_MINOR}*
        =app-emulation/vmware-workstation-10.0.${PV_MINOR}* )"

S=${WORKDIR}

pkg_setup() {
        CONFIG_CHECK="~HIGH_RES_TIMERS"
        if kernel_is ge 2 6 37 && kernel_is lt 2 6 39; then
                CONFIG_CHECK="${CONFIG_CHECK} BKL"
        fi

        linux-info_pkg_setup

        linux-mod_pkg_setup

        VMWARE_GROUP=${VMWARE_GROUP:-vmware}

        VMWARE_MODULE_LIST="vmblock vmci vmmon vmnet vsock"
        VMWARE_MOD_DIR="${PN}-${PVR}"

        BUILD_TARGETS="auto-build KERNEL_DIR=${KERNEL_DIR} KBUILD_OUTPUT=${KV_OUT_DIR}"

        enewgroup "${VMWARE_GROUP}"
        filter-flags -mfpmath=sse

        for mod in ${VMWARE_MODULE_LIST}; do
                MODULE_NAMES="${MODULE_NAMES} ${mod}(misc:${S}/${mod}-only)"
        done
}

src_unpack() {
        cd "${S}"
        for mod in ${VMWARE_MODULE_LIST}; do
                tar -xf /opt/vmware/lib/vmware/modules/source/${mod}.tar
        done
}

src_prepare() {
        epatch "${FILESDIR}/${PV_MAJOR}-makefile-kernel-dir.patch"
        epatch "${FILESDIR}/${PV_MAJOR}-makefile-include.patch"
        epatch "${FILESDIR}/${PV_MAJOR}-netdevice.patch"
        use pax_kernel && epatch "${FILESDIR}/hardened.patch"
        epatch "${FILESDIR}/${PV_MAJOR}-apic.patch"
        kernel_is ge 3 7 0 && epatch "${FILESDIR}/${PV_MAJOR}-putname.patch"
        kernel_is ge 3 10 0 && epatch "${FILESDIR}/${PV_MAJOR}-vmblock.patch"
        kernel_is ge 3 11 0 && epatch "${FILESDIR}/${PV_MAJOR}-vmblock-3.11.patch"
        kernel_is ge 3 12 0 && epatch "${FILESDIR}/${PV_MAJOR}-vmblock-3.12.patch"

        # Allow user patches so they can support RC kernels and whatever else
        epatch_user
}

src_install() {
        linux-mod_src_install
        local udevrules="${T}/60-vmware.rules"
        cat > "${udevrules}" <<-EOF
                KERNEL=="vmci",  GROUP="vmware", MODE=660
                KERNEL=="vmmon", GROUP="vmware", MODE=660
                KERNEL=="vsock", GROUP="vmware", MODE=660
        EOF
        udev_dorules "${udevrules}"
}

_________________
reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name)
Back to top
View user's profile Send private message
Kompi
Apprentice
Apprentice


Joined: 05 Oct 2002
Posts: 251
Location: Germany

PostPosted: Sat Jan 04, 2014 5:32 pm    Post subject: Reply with quote

ahh, there is the error. The heredoc text block in the src_install() method is does not end properly, as the error message says.

The "EOF" in the 3rd line from the bottom should not be indented, it must start the line. Just remove all white spaces / tabs before the EOF, then it should work. Like this:

Code:
src_install() {
        linux-mod_src_install
        local udevrules="${T}/60-vmware.rules"
        cat > "${udevrules}" <<-EOF
                KERNEL=="vmci",  GROUP="vmware", MODE=660
                KERNEL=="vmmon", GROUP="vmware", MODE=660
                KERNEL=="vsock", GROUP="vmware", MODE=660
EOF
        udev_dorules "${udevrules}"
}
Back to top
View user's profile Send private message
padoor
Advocate
Advocate


Joined: 30 Dec 2005
Posts: 3995
Location: india

PostPosted: Sun Jan 05, 2014 7:57 am    Post subject: Reply with quote

wow that is very fast thinking and right to the point.
vmware-modules-279.1 merged nicely for kernel-3.12.6
thank you very much. Kompi :D :D
also i learnt some more about local poratge usage
_________________
reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name)
Back to top
View user's profile Send private message
Massimo B.
Veteran
Veteran


Joined: 09 Feb 2005
Posts: 1169
Location: PB, Germany

PostPosted: Tue Jan 07, 2014 11:19 am    Post subject: Reply with quote

As explained here copying both patches into /etc/portage/patches/app-emulation/vmware-modules solved to emerge app-emulation/vmware-modules-279.1 with running sys-kernel/ck-sources-3.12.5 here.
_________________
ppc:PowerBook5,8 15"(1440)-G4/1.67, 2G(dev.notes[pdf]) | amd64:Core2Duo,i5-3470 | amd64-prefix:OpenSuse@Core2Quad | Lila-Theme
Back to top
View user's profile Send private message
TripleD
n00b
n00b


Joined: 21 Jan 2003
Posts: 30

PostPosted: Sat Jan 18, 2014 4:40 am    Post subject: Reply with quote

I've followed the patching advice above and although it gets a little further into the compile, it cuts out again. Any suggestions? I get the same result when putting the patches in the portage directory "vmware-modules/files" and changing the ebuild.

Code:

Calculating dependencies 
 * IMPORTANT: 7 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.

... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) app-emulation/vmware-modules-279.1
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/3.12.7-gentoo/build
 * Found sources for kernel version:
 *     3.12.7-gentoo
 * Checking for suitable kernel configuration options...
 [ ok ]
 * Checking for suitable kernel configuration options...
 [ ok ]
>>> Unpacking source...
>>> Source unpacked in /Build/portage/app-emulation/vmware-modules-279.1/work
>>> Preparing source in /Build/portage/app-emulation/vmware-modules-279.1/work ...
 * Applying 279-makefile-kernel-dir.patch ...
 [ ok ]
 * Applying 279-makefile-include.patch ...
 [ ok ]
 * Applying 279-netdevice.patch ...
 [ ok ]
 * Applying 279-apic.patch ...
 [ ok ]
 * Applying 279-putname.patch ...
 [ ok ]
 * Applying 279-vmblock.patch ...
 [ ok ]
 * Applying user patches from /etc/portage/patches//app-emulation/vmware-modules ...
 *   279-vmblock-3.11.patch ...
 [ ok ]
 *   279-vmblock-3.12.patch ...
 [ ok ]
 * Done with patching
>>> Source prepared.
>>> Configuring source in /Build/portage/app-emulation/vmware-modules-279.1/work ...
>>> Source configured.
>>> Compiling source in /Build/portage/app-emulation/vmware-modules-279.1/work ...
 * Preparing vmblock module
make HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/3.12.7-gentoo/build
Using 2.6.x kernel build system.
make -C /lib/modules/3.12.7-gentoo/build SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/Source/linux-3.12.7-gentoo'
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/filesystem.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/stubs.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/file.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/block.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/inode.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/super.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/control.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/module.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/linux/dentry.o
  LD [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/vmblock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/vmblock.mod.o
  LD [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only/vmblock.ko
make[1]: Leaving directory '/Source/linux-3.12.7-gentoo'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
 * Preparing vmci module
make HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/3.12.7-gentoo/build
Using 2.6.x kernel build system.
make -C /lib/modules/3.12.7-gentoo/build SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/Source/linux-3.12.7-gentoo'
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/linux/driver.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/linux/vmciKernelIf.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/common/vmciDriver.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/common/vmciResource.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/common/vmciRoute.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/common/vmciContext.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/common/vmciDatagram.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/common/vmciHashtable.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/common/vmciEvent.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/common/vmciQueuePair.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/common/vmciQPair.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/common/vmciDoorbell.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/driverLog.o
  LD [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/vmci.mod.o
  LD [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only/vmci.ko
make[1]: Leaving directory '/Source/linux-3.12.7-gentoo'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/Build/portage/app-emulation/vmware-modules-279.1/work/vmci-only'
cp -f vmci.ko ./../vmci.o
 * Preparing vmmon module
make HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= auto-build KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/3.12.7-gentoo/build
Using 2.6.x kernel build system.
make -C /lib/modules/3.12.7-gentoo/build SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/Source/linux-3.12.7-gentoo'
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driverLog.o
  CC [M]  /Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.o
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c: In function ‘LinuxDriverSyncCallOnEachCPU’:
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c:1252:4: error: too many arguments to function ‘smp_call_function’
    compat_smp_call_function(LinuxDriverSyncCallHook, &args, 0);
    ^
In file included from /Source/linux-3.12.7-gentoo/include/linux/percpu.h:5:0,
                 from /Source/linux-3.12.7-gentoo/include/linux/percpu-rwsem.h:6,
                 from /Source/linux-3.12.7-gentoo/include/linux/fs.h:30,
                 from /Source/linux-3.12.7-gentoo/include/linux/highmem.h:4,
                 from /Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c:25:
/Source/linux-3.12.7-gentoo/include/linux/smp.h:94:5: note: declared here
 int smp_call_function(smp_call_func_t func, void *info, int wait);
     ^
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c: At top level:
/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.c:1342:1: warning: always_inline function might not be inlinable [-Wattributes]
 LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
 ^
/Source/linux-3.12.7-gentoo/scripts/Makefile.build:308: recipe for target '/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.o' failed
make[3]: *** [/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only/linux/driver.o] Error 1
/Source/linux-3.12.7-gentoo/Makefile:1228: recipe for target '_module_/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only' failed
make[2]: *** [_module_/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/Source/linux-3.12.7-gentoo'
Makefile:130: recipe for target 'vmmon.ko' failed
make: *** [vmmon.ko] Error 2
 * ERROR: app-emulation/vmware-modules-279.1 failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-279.1'`,
 * the complete build log and the output of `emerge -pqv '=app-emulation/vmware-modules-279.1'`.
 * The complete build log is located at '/Files/Portage-Logs/app-emulation:vmware-modules-279.1:20140118-043135.log'.
 * For convenience, a symlink to the build log is located at '/Build/portage/app-emulation/vmware-modules-279.1/temp/build.log'.
 * The ebuild environment file is located at '/Build/portage/app-emulation/vmware-modules-279.1/temp/environment'.
 * Working directory: '/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only'
 * S: '/Build/portage/app-emulation/vmware-modules-279.1/work'

>>> Failed to emerge app-emulation/vmware-modules-279.1, Log file:

>>>  '/Files/Portage-Logs/app-emulation:vmware-modules-279.1:20140118-043135.log'
 * Messages for package app-emulation/vmware-modules-279.1:
 * ERROR: app-emulation/vmware-modules-279.1 failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-279.1'`,
 * the complete build log and the output of `emerge -pqv '=app-emulation/vmware-modules-279.1'`.
 * The complete build log is located at '/Files/Portage-Logs/app-emulation:vmware-modules-279.1:20140118-043135.log'.
 * For convenience, a symlink to the build log is located at '/Build/portage/app-emulation/vmware-modules-279.1/temp/build.log'.
 * The ebuild environment file is located at '/Build/portage/app-emulation/vmware-modules-279.1/temp/environment'.
 * Working directory: '/Build/portage/app-emulation/vmware-modules-279.1/work/vmmon-only'
 * S: '/Build/portage/app-emulation/vmware-modules-279.1/work'


Here's some more info I should have posted earlier:


Code:

Portage 2.3.6-r5 (funtoo/1.0/linux-gnu/arch/x86-64bit, gcc-4.8.1, glibc-2.18, 3.12.7-gentoo x86_64)
=================================================================
                         System Settings
=================================================================
System uname: Linux-3.12.7-gentoo-x86_64-AMD_FX-tm-8150_Eight-Core_Processor-with-gentoo-2.2.0
KiB Mem:    16374136 total,  14446836 free
KiB Swap:   16777208 total,  16777208 free
Timestamp of tree: Unknown
ld GNU ld (GNU Binutils) 2.23.2
app-shells/bash:          4.2_p45-r1
dev-java/java-config:     2.2.0-r1000
dev-lang/python:          2.7.6-r1000, 3.2.5-r1000, 3.3.3-r1000
dev-util/cmake:           2.8.12.1-r3
sys-apps/baselayout:      2.2.0-r4
sys-apps/openrc:          0.12.3-r1
sys-apps/sandbox:         2.6-r2
sys-devel/autoconf:       2.13, 2.69
sys-devel/automake:       1.11.6, 1.12.6, 1.13.4
sys-devel/binutils:       2.23.2
sys-devel/gcc:            4.8.1-r3
sys-devel/gcc-config:     1.8
sys-devel/libtool:        2.4.2
sys-devel/make:           4.0-r1
sys-kernel/linux-headers: 3.7 (virtual/os-headers)
sys-libs/glibc:           2.18
Repositories: gentoo
ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="* -@EULA Oracle-BCLA-JavaSE MakeMKV-EULA skype-eula PUEL Nero-EULA-US dlj-1.1 AdobeFlash-10.1 AdobeFlash-10.3 AdobeFlash-11.x googleearth google-talkplugin google-chrome"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe -fomit-frame-pointer -march=bdver1 -mtune=bdver1 -mcx16 -msahf -maes -mpclmul -mpopcnt -mabm -mavx"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt /usr/share/themes/oxygen-gtk/gtk-2.0"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-O2 -pipe -fomit-frame-pointer -march=bdver1 -mtune=bdver1 -mcx16 -msahf -maes -mpclmul -mpopcnt -mabm -mavx"
DISTDIR="/Files/distfiles"
EMERGE_DEFAULT_OPTS="--autounmask=n --quiet-build=n"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch xattr"
FFLAGS=""
GENTOO_MIRRORS="ftp://mirrors.rit.edu/gentoo http://mirror.csclub.uwaterloo.ca/gentoo-distfiles ftp://ftp.gtlib.gatech.edu/pub/gentoo"
LANG="en_US.utf8"
LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--as-needed"
LINGUAS="en en_US"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_TMPDIR="/Build"
PORTDIR="/Portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
SYNC_USER="root"
USE="X a52 aac aalib acl acpi alsa amd64 apng aspell bash-completion berkdb bitmap bzip2 cdda cddb cdparanoia cdr cleartype consolekit corefonts cracklib crypt cups curl cxx dbus declarative desktopglobe dga dirac djvu dts dv dvd dvdr dvdread encode exif expat fam fbcon ffmpeg flac fontconfig fortran ftp gd gdbm geoip ggi gif gmp gnuplot google-gadgets gphoto2 gps gtk hal iconv icu imagemagick imlib inotify introspection ipod java jbig jpeg jpeg2k justify kde kdeenablefinal kipi lame lcms libcaca libnotify lm_sensors lzma lzo mad matroska mmx mmxext mng modules mp3 mp3rtp mpeg mpi mtrr mudflap multilib ncurses nls nptl nsplugin ogg openal openexr opengl openmp oss pam pch pcre pdf plotutils png policykit postgres postscript pppd python qalculate qt3support qt4 qwt raw readline realtime resolvconf scanner sdl semantic-desktop slang smp sndfile soup sox spell sql sqlite sse sse2 sse4_1 sse4_2 sse4a ssl ssse3 startup-notification stream svg svm taglib tcl tcpd theora threads tiff tk truetype twolame type1 udev udisks unicode usb vdpau vorbis wavpack webkit win32codecs wmf xattr xcomposite xml xmp xorg xscreensaver xv zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel ice1724 intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias authn_core authz_core socache_shmcb unixd" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" CAMERAS="nikon" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" DRACUT_MODULES="bash resume" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LINGUAS="en en_US" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-5" PYTHON_ABIS="2.7 3.2 3.3" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_3" QEMU_SOFTMMU_TARGETS="i386 x86_64" QEMU_USER_TARGETS="i386 x86_64" RUBY_TARGETS="ruby18 ruby19 ruby20" USERLAND="GNU" VIDEO_CARDS="nvidia vesa" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CPPFLAGS, CTARGET, INSTALL_MASK, LC_ALL, MAKEOPTS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, SYNC_UMASK
Back to top
View user's profile Send private message
njcwotx
Guru
Guru


Joined: 25 Feb 2005
Posts: 499
Location: Texas

PostPosted: Sun Jan 19, 2014 5:19 am    Post subject: Reply with quote

I am getting the same error on a 3.10.25 kernel. there is already a patch for 3.10 in portage app-emulation/vmware-modules/files.

The patches here are for 3.11 and 3.12.

I filed a new bug https://bugs.gentoo.org/show_bug.cgi?id=498520 but I get the exact same emerge results as above.
_________________
Drinking from the fountain of knowldege.
Sometimes sipping.
Sometimes gulping.
Always thirsting.
Back to top
View user's profile Send private message
njcwotx
Guru
Guru


Joined: 25 Feb 2005
Posts: 499
Location: Texas

PostPosted: Sun Jan 19, 2014 9:33 pm    Post subject: Reply with quote

out of desperation I tried the patches above. I really dont have much of a clue as to what I was doing when it comes to ebuild patches :lol: but, I was able to modify the ebuild to bring in the 311 and 312 version of the patches when I emerged. I could see it in the build process as using the patch but it still failed.
_________________
Drinking from the fountain of knowldege.
Sometimes sipping.
Sometimes gulping.
Always thirsting.
Back to top
View user's profile Send private message
TripleD
n00b
n00b


Joined: 21 Jan 2003
Posts: 30

PostPosted: Mon Jan 20, 2014 9:51 pm    Post subject: Reply with quote

njcwotx wrote:
out of desperation I tried the patches above. I really dont have much of a clue as to what I was doing when it comes to ebuild patches :lol: but, I was able to modify the ebuild to bring in the 311 and 312 version of the patches when I emerged. I could see it in the build process as using the patch but it still failed.


Finally, success! I commented out my CFLAGS in make.conf which got it to install.

Give it a try.
Back to top
View user's profile Send private message
njcwotx
Guru
Guru


Joined: 25 Feb 2005
Posts: 499
Location: Texas

PostPosted: Tue Jan 21, 2014 4:53 pm    Post subject: Reply with quote

Sadly, it did nto work for me, I still get the same incompatible pointer types. :(

I will keep trying, I tried every version of workstation, each one pulled in a different version of modules but none worked and had same error.
_________________
Drinking from the fountain of knowldege.
Sometimes sipping.
Sometimes gulping.
Always thirsting.
Back to top
View user's profile Send private message
TripleD
n00b
n00b


Joined: 21 Jan 2003
Posts: 30

PostPosted: Tue Jan 21, 2014 11:32 pm    Post subject: Reply with quote

njcwotx wrote:
Sadly, it did nto work for me, I still get the same incompatible pointer types. :(

I will keep trying, I tried every version of workstation, each one pulled in a different version of modules but none worked and had same error.


Have a look over here, maybe it will help you out.

https://bugs.gentoo.org/show_bug.cgi?id=488072
Back to top
View user's profile Send private message
njcwotx
Guru
Guru


Joined: 25 Feb 2005
Posts: 499
Location: Texas

PostPosted: Wed Jan 22, 2014 4:15 pm    Post subject: Reply with quote

Saw them and tried them, they are the patches I mentioned in my previous post. Those are for newer kernels in unstable tree. However, I modified ebuild to apply them on 3.10.25 and redigested them and saw them apply during emerge and they still failed. I cleared the changes and resync'd the portage tree.

I have a case opened and am waiting to see what comes up.

I have tried ever version of vmware-workstation and each version takes a different version of modules, they all fail the same way. Incompatible pointer errors.
_________________
Drinking from the fountain of knowldege.
Sometimes sipping.
Sometimes gulping.
Always thirsting.
Back to top
View user's profile Send private message
njcwotx
Guru
Guru


Joined: 25 Feb 2005
Posts: 499
Location: Texas

PostPosted: Wed Jan 22, 2014 6:48 pm    Post subject: Reply with quote

Found this bug searching for the "incompatible types when assigning to type 'kgid_t' from type 'int' " error.

https://bugs.gentoo.org/show_bug.cgi?id=462666

It was for an older version of modules, so I installed the patch and the modules for 271.2 were pulled in and installed workstation 9, which had another issue with icu....

https://bugs.gentoo.org/show_bug.cgi?id=465126

Undaunted, I renamed 271-unerns.patch to 279-userns.patch and added
Code:
kernel_is ge 3 8 0 && epatch "${FILESDIR}/${PV_MAJOR}-userns.patch"

to the src_prepare block in 279.1 ebuild so it pulls in patches and redigested it.

Its a hack job on my part, I only know enough to be dangerous, but it did work.

I have a bug started, hopefully it will also get a correcly formed and properly adjusted patch for 279 soon.
https://bugs.gentoo.org/show_bug.cgi?id=498520
_________________
Drinking from the fountain of knowldege.
Sometimes sipping.
Sometimes gulping.
Always thirsting.
Back to top
View user's profile Send private message
padoor
Advocate
Advocate


Joined: 30 Dec 2005
Posts: 3995
Location: india

PostPosted: Thu Jan 23, 2014 6:37 am    Post subject: Reply with quote

now that 3.13.0 kernel is out, i hope a patch is made for this kernel too.
_________________
reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name)
Back to top
View user's profile Send private message
padoor
Advocate
Advocate


Joined: 30 Dec 2005
Posts: 3995
Location: india

PostPosted: Fri Jan 24, 2014 1:28 pm    Post subject: Reply with quote

Code:
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmnet-only/filter.c:64:18: note: previous declaration of ‘VNetFilterHookFn’ was here
 static nf_hookfn VNetFilterHookFn;
                  ^
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmnet-only/filter.c:64:18: warning: ‘VNetFilterHookFn’ used but never defined [enabled by default]
/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmnet-only/filter.c:206:1: warning: ‘VNetFilterHookFn’ defined but not used [-Wunused-function]
 VNetFilterHookFn(unsigned int hooknum,                 // IN:
 ^
make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmnet-only/filter.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmnet-only] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/usr/src/linux-3.13.0-gentoo-r1'
make: *** [vmnet.ko] Error 2
 * ERROR: app-emulation/vmware-modules-279.1::x-portage failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-279.1::x-portage'`,
 * the complete build log and the output of `emerge -pqv '=app-emulation/vmware-modules-279.1::x-portage'`.
 * The complete build log is located at '/var/tmp/portage/app-emulation/vmware-modules-279.1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-279.1/temp/environment'.
 * Working directory: '/var/tmp/portage/app-emulation/vmware-modules-279.1/work/vmnet-only'
 * S: '/var/tmp/portage/app-emulation/vmware-modules-279.1/work'

>>> Failed to emerge app-emulation/vmware-modules-279.1, Log file:

>>>  '/var/tmp/portage/app-emulation/vmware-modules-279.1/temp/build.log'


this is a different module build error.
vmnet.only does not build and error is not same as vmblock.only module

the current kernel used is 3.13-0-gentoo-r1
_________________
reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum