Summary: | app-emulation/vmware-modules-1.0.0.15-r1 syntax error w/ gcc-3.4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kurt Guenther <kurtg> |
Component: | Current packages | Assignee: | Gentoo VMWare Bug Squashers [disabled] <vmware+disabled> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | clmason, flavio.cappelli, gengor, mephinet, p.gentoo, raistlin, sulla, wbrana |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kurt Guenther
2007-07-31 21:59:30 UTC
My guess is that this won't work with gcc-3.4.6. Since there is at least one gcc-4.x that's stable, could you please use gcc-config to set your system compiler to that, and try recompiling vmware-modules? Please be aware that if it compiles successfully, you'll need to rebuild you kernel before it is usable, and may have to update many other packages. For more information see http://www.gentoo.org/doc/en/gcc-upgrading.xml. Please report back whether that cured the problem or not. Thanks very much... 5:) I switched to i686-pc-linux-gnu-4.1.2 using gcc-config, and now vmware-modules compiles and vmware-player works with kernel 2.6.21-r4. *** Bug 187625 has been marked as a duplicate of this bug. *** *** Bug 188810 has been marked as a duplicate of this bug. *** I am not really happy with this. I spent 8 hours today trying to figure this out. Why isn't there any dependency or notes that gcc-4 is required? searching for vmware-modules on bugs.gentoo.org doesn't bring up this bug id for some reason. Sulla, I'm very sorry you've experienced some frustration today. Let me try to go through your questions and hopefully offer some answers. There is no dependency on gcc-4.x, because it wouldn't do any good. Gcc-4.1 was marked stable awhile ago, and is most likely installed on most people's machines. However, having a new version of gcc installed on your machine does not mean that you are actually compiling with it. You would have to manually use gcc-config to change your profile, otherwise you'll continue compiling with the old version of gcc. For that reason, a dependency on the latest version of gcc will still not guarantee that it is in use. There are no notes that gcc-4 is required because it was only recently discovered that it was a requirement, and I've been very busy for the past two weeks. The previous ebuilds were not deleted. To package up all the various modules for use with the different packages would be a huge task. As it turns out someone very kindly writes a compatibility package, which is one set of source code that can create all the necessary modules for all of the packages. When this is updated, we make the change in a single location and all of the vmware-modules ebuilds are updated at once. Due to recent kernel changes and the new vmware-workstation-6, this compatibility package has changed significantly. During those changes it would appear that support for gcc-3.x has been dropped. There was no indication of this in the readme, and since gcc-4.x has been stable for quite some time, none of our testers encountered this problem. There are no old ebuilds to go back to, because the same ebuild is simply building against this new set of sources. Finally, bugs.gentoo.org's search box will, in general, only return OPEN bugs, rather than bugs that have already been RESOLVED. If you'd like to search all bugs on gentoo, you can do so by adding ALL (in capitals) to the beginning of your search, for example 'ALL vmware-modules'. I hope this has helped you understand the various problems you faced and why you encountered them. I'm sorry there is little we can do to help, hopefully you'll turn up bugs like this more quickly in the future... As it turns out, I've just checked this package, and indeed there's been a bugfix release specifically for this problem. I'm bumping the vmware overlay to vmware-any-any-update113, and if there are no issues with it, I'll push it out to the main tree in a week or so... Works for me as well. btw, OpenOffice still fails with gcc-4.x, so you'll need to zigzag between compilers to get desktop install/updates to complete. (In reply to comment #8) > As it turns out, I've just checked this package, and indeed there's been a > bugfix release specifically for this problem. I'm bumping the vmware overlay > to vmware-any-any-update113, and if there are no issues with it, I'll push it > out to the main tree in a week or so... > This is great news because hardened is still stuck with gcc 3.4.6. Thanks. (In reply to comment #10) > (In reply to comment #8) > > As it turns out, I've just checked this package, and indeed there's been a > > bugfix release specifically for this problem. I'm bumping the vmware overlay > > to vmware-any-any-update113, and if there are no issues with it, I'll push it > > out to the main tree in a week or so... > > > > This is great news because hardened is still stuck with gcc 3.4.6. Thanks. > I switched one vmware server to a xen dom0 (from layman xen) yesterday. It was a pain recompiling glibc but it was well worth it. Thank you Mike for your long explanation. However I don't think this bug should be set to resolved because of the broken dependency. The only reason I was hit by this bug was a dependency problem which still exists. You should at least put a warning prior to building vmware-tools that it will fell using gcc 3.4... It was working today until yesterday. I guess all the hardened gentoo will have to migrate to xen too. Mike says: "Due to recent kernel changes and the new vmware-workstation-6, this compatibility package has changed significantly. During those changes it would appear that support for gcc-3.x has been dropped. There was no indication of this in the readme, and since gcc-4.x has been stable for quite some time, none of our testers encountered this problem. There are no old ebuilds to go back to, because the same ebuild is simply building against this new set of sources." *** Bug 189064 has been marked as a duplicate of this bug. *** Any news on when the patch will be in the tree ? I had the same problem and it will save me a hurried switch to gcc 4.1.2 :) Sorry, forgot to mention, this is now fixed in the tree. Sorry for the delays... |