Wine on cygwin

[dominik]

Hi all,
I've just tried to build wine on cygwin in order to build the test suite 
in order to maybe find out why some tests fail on my machine.

configure runs reasonably well, but when the first dll is being built, 
hell breaks loose.

The assembler files generated from the .spec files are not accepted by "as".

.section ".init","ax"
yields
a.0dtc3a.s: Assembler messages:
a.0dtc3a.s:5: Error: junk at end of line, first unrecognized character 
is `"'

Then there is:
.hidden __wine_spec_nt_header
=>
a.0dtc3a.s:14: Error: unknown pseudo-op: `.hidden'

  .type __wine_stub_EditAuditInfo,@function
=>
a.iNk2s9.s:81: Warning: .type pseudo-op used outside of .def/.endef ignored.
a.iNk2s9.s:81: Error: junk at end of line, first unrecognized character 
is `_'

and much more ...

Are those Linux-specific assembler directives ?

Does anybody have an idea on how to workaround those ?

Regards

Dominik

[Austin English]

On Sat, Jul 25, 2009 at 12:36 PM, dominik<dominik(a)die-strassers.de> wrote:
> Hi all,
> I've just tried to build wine on cygwin in order to build the test suite in
> order to maybe find out why some tests fail on my machine.
>
> configure runs reasonably well, but when the first dll is being built, hell
> breaks loose.
>
> The assembler files generated from the .spec files are not accepted by "as".
>
> .section ".init","ax"
> yields
> a.0dtc3a.s: Assembler messages:
> a.0dtc3a.s:5: Error: junk at end of line, first unrecognized character is
> `"'
>
> Then there is:
> .hidden __wine_spec_nt_header
> =>
> a.0dtc3a.s:14: Error: unknown pseudo-op: `.hidden'
>
>  .type __wine_stub_EditAuditInfo,@function
> =>
> a.iNk2s9.s:81: Warning: .type pseudo-op used outside of .def/.endef ignored.
> a.iNk2s9.s:81: Error: junk at end of line, first unrecognized character is
> `_'
>
> and much more ...
>
> Are those Linux-specific assembler directives ?
>
> Does anybody have an idea on how to workaround those ?
>
> Regards
>
> Dominik

The cygwin build is pretty broken...you can build the tests for
windows really easily on Linux/Unix if you install mingw.

Just 'sudo apt-get/yum/etc. install mingw', then ./configure in your
wine tree. Use 'make crosstest' to build the windows tests.

-- 
-Austin

[King InuYasha]

If you are using Fedora, "yum install mingw32*" will install the whole
cross-compiling suite.

On Sat, Jul 25, 2009 at 6:39 PM, Austin English <austinenglish(a)gmail.com>wrote:
> On Sat, Jul 25, 2009 at 12:36 PM, dominik<dominik(a)die-strassers.de> wrote:
> > Hi all,
> > I've just tried to build wine on cygwin in order to build the test suite
> > in
> > order to maybe find out why some tests fail on my machine.
> >
> > configure runs reasonably well, but when the first dll is being built,
> > hell
> > breaks loose.
> >
> > The assembler files generated from the .spec files are not accepted by
> > "as".
> >
> > .section ".init","ax"
> > yields
> > a.0dtc3a.s: Assembler messages:
> > a.0dtc3a.s:5: Error: junk at end of line, first unrecognized character is
> > `"'
> >
> > Then there is:
> > .hidden __wine_spec_nt_header
> > =>
> > a.0dtc3a.s:14: Error: unknown pseudo-op: `.hidden'
> >
> > .type __wine_stub_EditAuditInfo,@function
> > =>
> > a.iNk2s9.s:81: Warning: .type pseudo-op used outside of .def/.endef
> > ignored.
> > a.iNk2s9.s:81: Error: junk at end of line, first unrecognized character
> > is
> > `_'
> >
> > and much more ...
> >
> > Are those Linux-specific assembler directives ?
> >
> > Does anybody have an idea on how to workaround those ?
> >
> > Regards
> >
> > Dominik
>
> The cygwin build is pretty broken...you can build the tests for
> windows really easily on Linux/Unix if you install mingw.
>
> Just 'sudo apt-get/yum/etc. install mingw', then ./configure in your
> wine tree. Use 'make crosstest' to build the windows tests.
>
> --
> -Austin

[Stefan Dösinger]

Am Sunday 26 July 2009 01:53:46 schrieb King InuYasha:
> > > .section ".init","ax"
> > > yields
> > > a.0dtc3a.s: Assembler messages:
> > > a.0dtc3a.s:5: Error: junk at end of line, first unrecognized character
> > > is `"'
> > >
> > > Then there is:
> > > .hidden __wine_spec_nt_header
> > > =>
> > > a.0dtc3a.s:14: Error: unknown pseudo-op: `.hidden'
> > >
> > > .type __wine_stub_EditAuditInfo,@function
> > > =>
> > > a.iNk2s9.s:81: Warning: .type pseudo-op used outside of .def/.endef
> > > I think winebuild has some problems. I sent one patch for this, but more is 
> > > remaining. This is a "git diff" from my Wine tree on my windows 
> > > partition(mostly used for D3D testing, so there are some unrelated things in 
> > > it).

Its mostly a matter of opening the right files in binary mode(Not sure how 
much that matters on cygwin though, it does on mingw). Also you have to run 
configure with CFLAGS=-D_WINDOWS because of the code in 
tools/winebuild/main.c, line 69. I think the correct define to check is 
__WIN32__, but I am not sure.

cross-compiler availability (was Re: Wine on cygwin)

[Hin-Tak Leung]

I think on most shells, you need to backslash escape the "*" - i.e.
    yum install mingw32\*
Just to cover all grounds, I came across the opensuse location of SuSE cross-compiler recently on the mono web site. (search in http://www.go-mono.com or www.mono-project.com) since win32 mono can be cross-built, and ximian/mono/suse/novell is one big family... 

--- On Sun, 26/7/09, King InuYasha <ngompa13(a)gmail.com> wrote:
> If you are using Fedora, "yum install
> mingw32*" will install the whole cross-compiling
> suite.
>
> On Sat, Jul 25, 2009 at 6:39 PM,
> Austin English <austinenglish(a)gmail.com>
> wrote:
> The cygwin build is pretty broken...you can
> build the tests for
>
> windows really easily on Linux/Unix if you install mingw.
>
> Just 'sudo apt-get/yum/etc. install mingw', then
> ./configure in your
>
> wine tree. Use 'make crosstest' to build the
> windows tests.
>
> --
>
> -Austin