On Tuesday 5 October 2004 08:37, Martin Fuchs wrote:
I tried building from the top, from libs/wine/, libs/port/, from some dlls/... and programs/... directories.
When building from the top, I am getting:
make[1]: Entering directory `/home/cvs/wine/libs' make[2]: Entering directory `/home/cvs/wine/libs/port' gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o interlocked.o interlocked.c {standard input}: Assembler messages: {standard input}:253: Error: unknown pseudo-op: `.previous' {standard input}:264: Error: unknown pseudo-op: `.previous' {standard input}:274: Error: unknown pseudo-op: `.previous' {standard input}:284: Error: unknown pseudo-op: `.previous' {standard input}:294: Error: unknown pseudo-op: `.previous' make[2]: *** [interlocked.o] Fehler 1 make[2]: Leaving directory `/home/cvs/wine/libs/port' make[1]: *** [port] Fehler 2 make[1]: Leaving directory `/home/cvs/wine/libs' make: *** [libs] Fehler 2
What compiler/platform are you on? This code is protected like this:
#if defined(__GNUC__) && !defined(__MINGW32__) && !defined(__APPLE__)
So if you're on Cygwin we may need to add && !defined(__CYGWIN__) or whatever is the appropriate define for that platform. As discussed earlier on this list, the .previous directive is ELF specific.
BTW, is there a define that identifies an ELF platform, a PE platform? Should we introduce those? That would make the check simpler and not as open ended like it is now.
-Hans