Red Hat Bugzilla – Bug 984792
Wine Compilation error
Last modified: 2014-11-18 16:34:22 EST
Description of problem: I got error when compiling some dll program. This was done during the wine installation process. Version-Release number of selected component (if applicable): Cent OS 6.4 & Wine 1.6-rc5 How reproducible: Been getting this message since wine released its latest version rc5. However, also changed chmod of /home/sol013/lib/ to readable. Steps to Reproduce: Get LoL installation script: winehq.org = app list - League of Legends and copy wget ... Install_LoL.sh and paste it in terminal. Actual results: When compiling, towards the end I get compiling error. It is saying it could be Os or hardware problem and report it to this site. Expected results: Compilation w/o any error Additional info: This could be the indicator that my computer is unstable. Been getting crashes in Linux... This problem because I am using every slot of my memory and also have been downclocking my CPU (by 10MHz) to make it stable. However, also writing this issue because it could be a OS problem. If you know any relationship between computer stability and comiling please let me know. Or if anyone having this issue please join in!
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux.
Can you reproduce it, always on the same file same compiler options same error? If the compiler says it can't reproduce it, likely it is a hw issue. If you can reproduceably trigger it, please attach preprocessed source and list all compiler options used to compile the source that triggers the compiler internal error.
While we acknowledge that an internal-compiler-error is bad, we are not planning to update compat-gcc-34 to fix this issue. While we certainly could fix this bug, policy is to minimize the amount of changes made to the compat-gcc packages. We strongly recommend using the base system compiler or the DTS compilers.