Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have downloaded wineX CVS and when I got to compile it using the wineinstall script i get these errors.
"../include/basetsd.h:148:3: error: #error Unknown CPU architecture!
In file included from ../include/windef.h:16,
from ../include/wine/unicode.h:10,
from casemap.c:4:
../include/winnt.h:1035:2: error: #error You need to define a CONTEXT for your CPU
In file included from ../include/windef.h:16,
from ../include/wine/unicode.h:10,
from casemap.c:4:
../include/winnt.h:1038: error: syntax error before ‘*’ token
../include/winnt.h:1038: warning: type defaults to ‘int’ in declaration of ‘PCONTEXT’
../include/winnt.h:1038: warning: data definition has no type or storage class
../include/winnt.h:2073: error: syntax error before ‘PCONTEXT’
../include/winnt.h:2073: warning: no semicolon at end of struct or union
../include/winnt.h:2074: warning: type defaults to ‘int’ in declaration of ‘EXCEPTION_POINTERS’
../include/winnt.h:2074: warning: type defaults to ‘int’ in declaration of ‘PEXCEPTION_POINTERS’
../include/winnt.h:2074: warning: data definition has no type or storage class
../include/winnt.h:2086: error: syntax error before ‘PCONTEXT’
../include/winnt.h:2098: error: syntax error before ‘ExceptionInfo’
../include/winnt.h:2101: error: syntax error before ‘epointers’
In file included from ../include/winnls.h:5,
from ../include/wine/unicode.h:11,
from casemap.c:4:
../include/winbase.h:121: error: syntax error before ‘LPCONTEXT’
../include/winbase.h:121: warning: type defaults to ‘int’ in declaration of ‘LPCONTEXT’
../include/winbase.h:121: warning: data definition has no type or storage class
../include/winbase.h:123: error: syntax error before ‘LPEXCEPTION_POINTERS’
../include/winbase.h:123: warning: type defaults to ‘int’ in declaration of ‘LPEXCEPTION_POINTERS’
../include/winbase.h:123: warning: data definition has no type or storage class
../include/winbase.h:1366: error: syntax error before ‘CONTEXT’
../include/winbase.h:1503: warning: type defaults to ‘int’ in declaration of ‘CONTEXT’
../include/winbase.h:1503: error: syntax error before ‘*’ token
make[1]: *** [casemap.o] Error 1
make[1]: Leaving directory `/home/daniel/winex/unicode'
make: *** [unicode/libwine_unicode.so] Error 2
Someone was telling me the other day that the Cedega CVS had been broken for a while, dunno how true it is though. I do know hoever, that if you/your distro is using gcc4 then it won't compile no matter whether the source is broken or not.
Someone was telling me the other day that the Cedega CVS had been broken for a while, dunno how true it is though. I do know hoever, that if you/your distro is using gcc4 then it won't compile no matter whether the source is broken or not.
I believe I'm using winex-cvs version 12/17/2005,
and yes it's best to stay away from the cutting-edge
when running this off the wall stuff.
I'm still on gcc-3.3.4 and kernel 2.4.x
It won't work because gcc4 is anal about some stuff that gcc3 didn't really care about. It means it enforces good coding practices but some stuff won't build under it, cvscedega being one of those things.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.