Problem rebuilding VMWare Workstation 10.0.2 Modules

philad · 2014-05-01 14:05:30

Hi,

today I updated my Kernel to 3.14.2-1 and wanted to rebuild the modules for VMware Workstation 10.0.2. Doing so causes the following error.
I used this patch before http://pastie.org/pastes/9090538/.
Has there been major changes between 3.14.1-1 and 3.14.2-1 which cause this problems? It worked before. Someone else experiences this?

Greets
PhilAd

# vmware-modconfig --console --install-all
Stopping VMware services:
   VMware Authentication Daemon                                        done
   VM communication interface socket family                            done
   Virtual machine communication interface                             done
   Virtual machine monitor                                             done
   Blocking file system                                                done
make: Entering directory '/tmp/modconfig-WBV6v7/vmmon-only'
Using 2.6.x kernel build system.
/sbin/make -C /lib/modules/3.14.2-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/lib/modules/3.14.2-1-ARCH/build'
Makefile:615: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
  CC [M]  /tmp/modconfig-WBV6v7/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/modconfig-WBV6v7/vmmon-only/linux/driver.o
  CC [M]  /tmp/modconfig-WBV6v7/vmmon-only/linux/hostif.o
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmmon-only/linux/driverLog.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmmon-only/linux/driverLog.o] Error 1
  CC [M]  /tmp/modconfig-WBV6v7/vmmon-only/common/apic.o
make[2]: *** Warte auf noch nicht beendete Prozesse...
  CC [M]  /tmp/modconfig-WBV6v7/vmmon-only/common/memtrack.o
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmmon-only/linux/driver.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmmon-only/linux/driver.o] Error 1
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmmon-only/linux/hostif.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmmon-only/linux/hostif.o] Error 1
  CC [M]  /tmp/modconfig-WBV6v7/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/modconfig-WBV6v7/vmmon-only/common/vmx86.o
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmmon-only/common/apic.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmmon-only/common/apic.o] Error 1
  CC [M]  /tmp/modconfig-WBV6v7/vmmon-only/common/cpuid.o
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmmon-only/common/memtrack.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmmon-only/common/memtrack.o] Error 1
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmmon-only/common/hashFunc.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmmon-only/common/hashFunc.o] Error 1
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmmon-only/common/vmx86.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmmon-only/common/vmx86.o] Error 1
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmmon-only/common/cpuid.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmmon-only/common/cpuid.o] Error 1
Makefile:1274: recipe for target '_module_/tmp/modconfig-WBV6v7/vmmon-only' failed
make[1]: *** [_module_/tmp/modconfig-WBV6v7/vmmon-only] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.14.2-1-ARCH/build'
Makefile:130: recipe for target 'vmmon.ko' failed
make: *** [vmmon.ko] Error 2
make: Leaving directory '/tmp/modconfig-WBV6v7/vmmon-only'
make: Entering directory '/tmp/modconfig-WBV6v7/vmnet-only'
Using 2.6.x kernel build system.
/sbin/make -C /lib/modules/3.14.2-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/lib/modules/3.14.2-1-ARCH/build'
Makefile:615: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
  CC [M]  /tmp/modconfig-WBV6v7/vmnet-only/driver.o
  CC [M]  /tmp/modconfig-WBV6v7/vmnet-only/hub.o
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmnet-only/driver.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmnet-only/driver.o] Error 1
  CC [M]  /tmp/modconfig-WBV6v7/vmnet-only/userif.o
  CC [M]  /tmp/modconfig-WBV6v7/vmnet-only/netif.o
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
make[2]: *** Warte auf noch nicht beendete Prozesse...
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmnet-only/hub.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmnet-only/hub.o] Error 1
  CC [M]  /tmp/modconfig-WBV6v7/vmnet-only/bridge.o
  CC [M]  /tmp/modconfig-WBV6v7/vmnet-only/filter.o
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmnet-only/userif.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmnet-only/userif.o] Error 1
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmnet-only/netif.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmnet-only/netif.o] Error 1
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmnet-only/bridge.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmnet-only/bridge.o] Error 1
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmnet-only/filter.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmnet-only/filter.o] Error 1
Makefile:1274: recipe for target '_module_/tmp/modconfig-WBV6v7/vmnet-only' failed
make[1]: *** [_module_/tmp/modconfig-WBV6v7/vmnet-only] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.14.2-1-ARCH/build'
Makefile:130: recipe for target 'vmnet.ko' failed
make: *** [vmnet.ko] Error 2
make: Leaving directory '/tmp/modconfig-WBV6v7/vmnet-only'
make: Entering directory '/tmp/modconfig-WBV6v7/vmci-only'
Using 2.6.x kernel build system.
/sbin/make -C /lib/modules/3.14.2-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/lib/modules/3.14.2-1-ARCH/build'
Makefile:615: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
  CC [M]  /tmp/modconfig-WBV6v7/vmci-only/linux/driver.o
  CC [M]  /tmp/modconfig-WBV6v7/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/modconfig-WBV6v7/vmci-only/common/vmciDriver.o
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
  CC [M]  /tmp/modconfig-WBV6v7/vmci-only/common/vmciResource.o
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmci-only/linux/driver.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmci-only/linux/driver.o] Error 1
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
make[2]: *** Warte auf noch nicht beendete Prozesse...
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmci-only/linux/vmciKernelIf.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmci-only/linux/vmciKernelIf.o] Error 1
  CC [M]  /tmp/modconfig-WBV6v7/vmci-only/common/vmciRoute.o
  CC [M]  /tmp/modconfig-WBV6v7/vmci-only/common/vmciContext.o
  CC [M]  /tmp/modconfig-WBV6v7/vmci-only/common/vmciDatagram.o
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
  CC [M]  /tmp/modconfig-WBV6v7/vmci-only/common/vmciHashtable.o
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmci-only/common/vmciContext.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmci-only/common/vmciContext.o] Error 1
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmci-only/common/vmciDriver.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmci-only/common/vmciDriver.o] Error 1
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmci-only/common/vmciResource.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmci-only/common/vmciResource.o] Error 1
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmci-only/common/vmciRoute.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmci-only/common/vmciRoute.o] Error 1
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmci-only/common/vmciDatagram.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmci-only/common/vmciDatagram.o] Error 1
gcc: Fehler: nicht erkannte Kommandozeilenoption »-fstack-protector-strong«
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-WBV6v7/vmci-only/common/vmciHashtable.o' failed
make[2]: *** [/tmp/modconfig-WBV6v7/vmci-only/common/vmciHashtable.o] Error 1
Makefile:1274: recipe for target '_module_/tmp/modconfig-WBV6v7/vmci-only' failed
make[1]: *** [_module_/tmp/modconfig-WBV6v7/vmci-only] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.14.2-1-ARCH/build'
Makefile:130: recipe for target 'vmci.ko' failed
make: *** [vmci.ko] Error 2
make: Leaving directory '/tmp/modconfig-WBV6v7/vmci-only'
Unable to install all modules.  See log for details.

jaylittle · 2014-05-01 16:16:42

I'm experiencing this issue as well.

azzido · 2014-05-01 17:08:07

Same problem here.

Tried this https://communities.vmware.com/thread/477701 patch, but it did not work.

ilusi0n · 2014-05-01 18:15:22

Probably is because of this https://mailman.archlinux.org/pipermail … 36065.html
There is a lot of threads on forum at the moment regarding problems on compiling the modules

jaylittle · 2014-05-01 20:21:48

<sigh> Shit is getting sloppy around here. Seriously.

headkase · 2014-05-01 21:03:01

jaylittle wrote:

<sigh> Shit is getting sloppy around here. Seriously.

Do you mean the free volunteer work by the Arch developers or VMWare's modules? If you meant the former then I suggest go making your own distribution. With blackjack and hookers.

jaylittle · 2014-05-01 21:39:38

And because the work is done on a volunteer basis, it is not subject to criticism? Come on - that's a cop out. There's a metric ton of stuff broken outside the testing repos right now and it's gotten a little bit absurd.

headkase · 2014-05-01 21:47:23

jaylittle wrote:

And because the work is done on a volunteer basis, it is not subject to criticism? Come on - that's a cop out. There's a metric ton of stuff broken outside the testing repos right now and it's gotten a little bit absurd.

Didn't mean to step into your entitled world. I hear SuSE is backed by a major corporation - perhaps you could try that OS?

jaylittle · 2014-05-01 21:55:04

Entitled? Hardly. Realistic? You betcha. From the perspective of a long time Arch user, let me give it t to you straight: The quality of Arch has decreased precipitously in the last few months. People are screaming bloody murder over the massive amount of broken stuff in Ubuntu LTS 14.04 which seems more than fair given the fact that things are broken. Why is the Arch team being cut slack on this? When packages move from testing to non-testing repos, they should be tested and verified working. Anything less than that constitutes a failure in the QA process and if negative user feedback isn't part of fixing that, then we've got a real problem here.

headkase · 2014-05-01 22:01:13

The magic Arch developers don't have oodles of cash to spend on regression testing. The "Testing" repo and the reports generated by it are user-driven. If no one tests on the wide variety of hardware the Arch developers can't afford then regressions in those special cases won't be caught. Seriously, Arch isn't oozing money: try Fedora, SuSE, or run your Arch on bare metal and you won't have to worry so much.

karol · 2014-05-01 22:04:58

Can we please get back on topic? If you want you can continue this conversation privately e.g. via e-mail.

jaylittle · 2014-05-01 22:05:24

I do run Arch on bare metal. I use VMWare Workstation for work related purposes. It is not optional. When VMWare is broken, my ability to productively use Linux is broken by extension. As for the Arch team and their lacking resources, let's take your point at face value. Now, we've known what the problem is for almost four hours and no fix has been issued. There are two possible ways to fix this particular problem:

[1] Recompile 3.14.2 with the version of GCC currently available in core (4.8.2)
[2] Push GCC 4.9.x to core.

And yet.... nothing. Meanwhile many of us cannot use Arch unless we are willing to switch to testing repos as custom compiled modules are a core part of the Linux experience for many users. I for one refuse to switch to testing repos... for what I would hope are now obvious reasons.

fukawi2 · 2014-05-01 22:14:15

We're done here.

@jaylittle - Arch and it's team owe you nothing except freedom -- and you have that freedom to tell your story walking. This is your first warning
https://wiki.archlinux.org/index.php/Fo … ther_Users
https://wiki.archlinux.org/index.php/Fo … _Not_Flame
https://wiki.archlinux.org/index.php/Fo … IKESHED.29
https://wiki.archlinux.org/index.php/Fo … 2C_Banning

Closing -- apologies to the OP that this got hijacked in such a negative manner, but we do appear to have an answer to the problem, the solution just needs to progress through [testing] et al. Please ensure a bug report has been filed; the devs don't monitor the forums for bugs.

ewaller · 2014-05-01 22:18:46

Moderator comment.

https://wiki.archlinux.org/index.php/Fo … _Not_Flame
https://wiki.archlinux.org/index.php/Fo … ther_Users
https://wiki.archlinux.org/index.php/Fo … mpty_Posts
and
https://wiki.archlinux.org/index.php/Fo … _Hijacking

We are not being of much use to philad here, now are we. Even though his first post on these forums was rather good.
So, please, lets be a bit more professional.

Last edited by ewaller (2014-05-01 22:21:26)

ewaller · 2014-05-01 22:20:34

fukawi2, you beat me to it. I see you picked a slightly different subset than did I.

Arch Linux

#1 2014-05-01 14:05:30

Problem rebuilding VMWare Workstation 10.0.2 Modules

#2 2014-05-01 16:16:42

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

#3 2014-05-01 17:08:07

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

#4 2014-05-01 18:15:22

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

#5 2014-05-01 20:21:48

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

#6 2014-05-01 21:03:01

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

#7 2014-05-01 21:39:38

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

#8 2014-05-01 21:47:23

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

#9 2014-05-01 21:55:04

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

#10 2014-05-01 22:01:13

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

#11 2014-05-01 22:04:58

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

#12 2014-05-01 22:05:24

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

#13 2014-05-01 22:14:15

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

#14 2014-05-01 22:18:46

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

#15 2014-05-01 22:20:34

Re: Problem rebuilding VMWare Workstation 10.0.2 Modules

Board footer