On Mon, 2011-09-12 at 17:45 -0500, melancholy wrote: > this is weird, grep shows nothing... > > > Code: > ~/archive/wine-1.3.28$ grep -r __NR_modify_ldt * > ~/archive/wine-1.3.28$ > > I varied __NR_modify_ldt as well to see if it can find something then, but nothing... > Thats really odd: it should at least have found the use of the symbol that caused gcc to say its undefined. If you have the downloaded 1.3.28 archive somewhere and in a form where you can unpack it in some different directory, do so and run grep against it there to see if you accidentally blitzed something. Failing that, find the source file(s) that use the __NR_modify_ldt symbol use them as a guide to finding where its defined, which should either be in the same source file or in one of the #included header files. Apart from it simply being omitted by mistake (unlikely in published code, but odd things do happen) the main possibilities are: - its defined in a header that used to be #included and isn't now for some reason - its defined in a conditionally included code section (delimited by #ifdef ... #endif preprocessor directives) and the #ifdef evaluates as false. This is usually the result of 'configure' misbehaving or simply not having been run after the source archive was unpacked. Sorry I can't be more explicit, but I don't compile Wine myself: the programs I use it with have by and large just worked apart from installing VB runtimes with winetricks. I'm just reminding you what usually causes this type of error and saying how I usually go about tracking down this sort of problem. Martin
