broken mingw build

[Kevin Koltzau]

This patch
http://cvs.winehq.org/patch.py?id=12495
seems to have broken the mingw build, currently getting

i386-mingw32msvc-gcc -c -I. -I. -I../../include -I../../include  -D__WINESRC__ -D_REENTRANT -Wall -pipe -fno-strength-reduce -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith  -g -O2 -o interlocked.o interlocked.c
{standard input}: Assembler messages:
{standard input}:124: Error: unknown pseudo-op: `.previous'
{standard input}:135: Error: unknown pseudo-op: `.previous'
{standard input}:145: Error: unknown pseudo-op: `.previous'
{standard input}:155: Error: unknown pseudo-op: `.previous'
{standard input}:165: Error: unknown pseudo-op: `.previous'
make[2]: *** [interlocked.o] Error 1

[Hans Leidekker]

On Sunday 30 May 2004 02:59, Kevin Koltzau wrote:
> This patch
> http://cvs.winehq.org/patch.py?id=12495
> seems to have broken the mingw build, currently getting

Are you saying you could build Wine with MinGW before this patch?
> i386-mingw32msvc-gcc -c -I. -I. -I../../include -I../../include  -D__WINESRC__ -D_REENTRANT -Wall -pipe -fno-strength-reduce -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith  -g -O2 -o interlocked.o interlocked.c
> {standard input}: Assembler messages:
> {standard input}:124: Error: unknown pseudo-op: `.previous'
> {standard input}:135: Error: unknown pseudo-op: `.previous'
> {standard input}:145: Error: unknown pseudo-op: `.previous'
> {standard input}:155: Error: unknown pseudo-op: `.previous'
> {standard input}:165: Error: unknown pseudo-op: `.previous'
> make[2]: *** [interlocked.o] Error 1

I suspect .previous is ELF specific? Don't know if it's worth fixing
this since AFAICS this code is about portability toward Unix platforms
and now we're trying to build PE executables from it with MinGW. Cygwin
might be an interesting target in this respect though.

-Hans

Changelog:
  MinGW portability fix.

[Mike Hearn]

On Tue, 2004-06-01 at 09:50 +0200, Hans Leidekker wrote:
> I suspect .previous is ELF specific?

Yes, .previous is ELF specific. It reverts the assembler to generating
output in whatever the previous section was, so if you write:

.text
blah blah blah
.previous

then you are now back in the section you were before .text - PE doesn't
really have the same idea of sections as ELF does.

thanks -mike