Need Help Compiling Cedega From Cvs... cdrom.h: present but cannot be compiled.

Hi...

yesterday I downloaded CVS snapshot of Cedega (formely WineX) Windows API implementaction for Linux... I encountered only one problem while compiling:

checking linux/cdrom.h usability... nochecking linux/cdrom.h presence... yesconfigure: WARNING: linux/cdrom.h: present but cannot be compiledconfigure: WARNING: linux/cdrom.h:     check for missing prerequisite headers?configure: WARNING: linux/cdrom.h: see the Autoconf documentationconfigure: WARNING: linux/cdrom.h:     section "Present But Cannot Be Compiled"configure: WARNING: linux/cdrom.h: proceeding with the preprocessor's resultconfigure: WARNING: linux/cdrom.h: in the future, the compiler will take precedenceconfigure: WARNING:     ## --------------------------------- ##configure: WARNING:     ## Report this to the Cedega lists.  ##configure: WARNING:     ## --------------------------------- ##checking for linux/cdrom.h... yes

have someone encountered something like this? I would be happy if I can get any help

Giniu

PS.: I'm using vanilla 2.6.9 kernel, my gcc version is 3.3.4, and glibc version is 2.3.4.

Im having trouble compiling too. Right now i use SuSE 9.1 and when i get to the MAKE stage i get a looong list of errors, maybe my glibc is out dated?

this long list of errors as far as I know is related to "present but cannot be compiled" (for my situation), and yes I was thinking about it as bug in glibc or autoconf, but I wasn't able to find any constructive help... For now on, I sent error log to Cedega support, also tryied Wine CVS today, and I got same error :Pand you can be sure - if you get error or warning while configure, you probably would get error while compiling or it would probably segfault while trying to run... first of all make sure you get clean configure log, and then type make, without this, it is loss of time...

Cedega is NOT free.The reason why free CVS access to source code is allowed, is for you to study the code, and help them develop it by hacking the code and submitting patches.the CVS code is only the emulation part, and some key parts to the source code are missing.very very very few epeople have ever managed to get a stable working install from the CVS source code, and to do it, they needed to fill in the gaps, writing and hacking at the code. a simple "make install" will not work.A while ago, the people at Gentoo Linux used to release patched CVS source code that worked.... however the wineX / cedeger people kindly explained that the CVS access was not meant as a way to get the emulator without paying, and the people at gentoo removed the ebuild portage installer.In other words, unless you have a very good knoleged of Linux AND windowsAPI's and a great deal of C, then you have no chance of getting the CVS code to work.Cedeger is very cheap, why not pay for it ??? help the cause :PEDIT: ohh, and just for the fun of answering the question....either /usr/src/linux is a symbolic link to the wrong kernel source version ? (do you have more than one kernel source version installed) or you just have the wrong kernel source version installed.did you compile the kernel yourself ?

Hi, thanks to your reply qwijibow, and now to answer your questions:- yup, /usr/src/linux is pointing to right (only one, I removed old after new one worked) source...- nope, this kernel is stright from my Slackware distribution- I know that this is only for testing, but as I said the same happend to me when I was trying to compile regulat Wine CVS or even any Wine sources (also from stable)...- and at least - to pay for software, you musn't live in my country - I cannot afford monthly paymeny, besides there are many more important things, so I decided to test this CVS a liitle, and since my Graphics Card doesn't have copy protection related code and texture compression (and this is as I remember only part removed from CVS, for now...), this doesn't make me any difference for me, so sending regular bug reports when I would find something, wouldn't be hard to me... and I have some experience in doing this kind of stuff when I manage to get the program running...

I cannot afford monthly paymeny,

this is a ommon mis-understanding.
the monthly paymens are only to keep your account active and allow you to download new versions of Cedeger.

Most people will only pay the minimum for 1 weeks membership, and download within that week.

after membership is over, you can still use cedeger as much as you like. you only need to pay again if you wan the latest version.

EDIT:
im not 100% sure with whats wrong with the compiling then, but ui do know that i have attempted many times before, and even when i manage to get it to compile without error, i fail to make it run even programs which wine work with.

may i ask what you want to use cedeger for ???
you can download pre-compiled Wine for free, which is a very good windows emulator.
you only need cedeger for games like half-life 2 that are directX only games. (openGL games somtimes work)

Hi...

What for?? so... I want to use it for Fallout 2 - and before you ask I would answer - yes, Wine runs Fallout better than Cedega, but, from some time it was running it realy slow, but CVS version of Wine and Cedega are reported to work again fast... I don't want to use about one year old wine, so I decided to download CVS - I tryied to compile wine and got cdrom.h warning, then I thought that maybe Cedega fixed this, or just uses other method to obtain this, but unfortuneatly this also went down at same point, so I decided to ask there for help...

ps.: on builded snapshot of wine, when I run it in separate xserwer it runs realy slow, maybe I did it wrong? I made startup script that looked like that:

xinit /usr/bin/wine /usr/locale/games/fallout2/fallout2.exe -- :1 -depth 16

To avoid running in 24 depth, since all Fallouts are running very slow, when depth is scaled up... It doesn't work in 8, so as it was recomended for Fallout BoS, I choose to run in 16... maybe it is just wrongly configured? if yes then if someone managed to run Fallout 2 in wine and can post his config, I would be graetful

Finaly!!It compiled great now I don't know jet if it would work faster, but it works ... I would tell what was wrong... it was rather my error than any bug...Right now I have 2.6.9 kernel, but my glibc was compiled with 2.4.29 kernel... I installed 2.4.29 kernel headers and everything went great :)Stupid little thing... any way - now it works