Hi, I had a problem with Wine20050830 compilation. Error: error parse before "BerElement"; in lines: 289, 290, 322, 323 in "wine/dlls/wldap32/winldap_private.h" file. In file winldap.h I found declaration of BerElement type. This header is not included in winldap_private.h. I put declaration of BerElement type to winldap_private.h and it resolved the problem. I tried add line: #include "winldap.h" to winldap.h too, but it makes double declaration errors. I'm sorry if my English is horrible :) Well I hope my letter will be helpful. Perhaps this error appear only on my computer (?) :D Fun of your Wine.
j0zue(a)o2.pl wrote:
I had a problem with Wine20050830 compilation. Error: error parse before "BerElement"; in lines: 289, 290, 322, 323 in "wine/dlls/wldap32/winldap_private.h" file. In file winldap.h I found declaration of BerElement type. This header is not included in winldap_private.h. I put declaration of BerElement type to winldap_private.h and it resolved the problem.
I tried add line: #include "winldap.h" to winldap.h too, but it makes double declaration errors.
I'm sorry if my English is horrible :) Well I hope my letter will be helpful. Perhaps this error appear only on my computer (?) :D
This question has been asked and answered a couple of times now. You could spare everybody some time by searching the list archives before blindly posting here. Please do so in the future ;-). GMANE search: http://search.gmane.org/?group=gmane.comp.emulators.wine.user&query=BerEleme... (USERS list, try first) http://search.gmane.org/?group=gmane.comp.emulators.wine.devel&query=BerElem... (DEVEL list) To view an entire thread in GMANE, after clicking the search result, click the 'Subject' link.
Fun of your Wine.
hehe :-).
Molle Bestefich wrote:
j0zue(a)o2.pl wrote:
I had a problem with Wine20050830 compilation. Error: error parse before "BerElement";
This question has been asked and answered a couple of times now.
GMANE search: http://search.gmane.org/?group=gmane.comp.emulators.wine.user&query=BerEleme... (USERS list, try first) http://search.gmane.org/?group=gmane.comp.emulators.wine.devel&query=BerElem... (DEVEL list)
To view an entire thread in GMANE, after clicking the search result, click the 'Subject' link.
Actually, your problem is in the Wine Bugs database too: http://bugs.winehq.org/query.cgi The interface is absolutely horrid though, at least if you're a bugzilla newbie or if you're searching for known bugs..: After typing 'BerElement' in the freetext field, you have to check all of the items in the 'Status' field to make the search return anything.
Molle Bestefich wrote:
Molle Bestefich wrote:
j0zue(a)o2.pl wrote:
I had a problem with Wine20050830 compilation. Error: error parse before "BerElement";
This question has been asked and answered a couple of times now.
GMANE search: http://search.gmane.org/?group=gmane.comp.emulators.wine.user&query=BerEleme... (USERS list, try first) http://search.gmane.org/?group=gmane.comp.emulators.wine.devel&query=BerElem... (DEVEL list)
To view an entire thread in GMANE, after clicking the search result, click the 'Subject' link.
Actually, your problem is in the Wine Bugs database too: http://bugs.winehq.org/query.cgi
The interface is absolutely horrid though, at least if you're a bugzilla newbie or if you're searching for known bugs..:
After typing 'BerElement' in the freetext field, you have to check all of the items in the 'Status' field to make the search return anything.
That said, it seems a bit rude that the 20050830 CVS drop is *still* on the front page of http://www.winehq.com/, even after everyone knows that it's missing a patch to compile cleanly. Why not just add the patch to the package and slap it up as '20050830-1' ? Or add a link to the bugzilla entry to the front page ?
On 9/29/05, Molle Bestefich <molle.bestefich(a)gmail.com> wrote:
That said, it seems a bit rude that the 20050830 CVS drop is *still* on the front page of http://www.winehq.com/, even after everyone knows that it's missing a patch to compile cleanly.
Why not just add the patch to the package and slap it up as '20050830-1' ? Or add a link to the bugzilla entry to the front page ?
1. Adding the Bugzilla entry as a news item is a good idea. However, we're possibly close to a September drop, so at this point it's probably easiest to just wait for that. I'm very open to adding news items to the front page, so definitely feel free to drop me an email when you think of things like that. How about WWN coverage instead? 2. CVS drops are just that - drops. They haven't been compiled on a bizillion systems or tested with real-world applications to ensure things aren't massively broken. Furthermore, no work was done to stabilize the release other than normal bug fixes. Instead, it represents a point in time where Alexandre ran the regression tests, things worked for him, and a tarball was made. There was discussion of that process changing after a beta release is made. 3. Binary packages are highly recommended unless you prefer to muck around occasionally with source code. That probably doesn't apply to you since you're reading wine-devel, but for 99% of the people in the world they should use the binaries. In theory we'll catch things at that point. -Brian
On 9/29/05, Brian Vincent <brian.vincent(a)gmail.com> wrote:
On 9/29/05, Molle Bestefich <molle.bestefich(a)gmail.com> wrote:
That said, it seems a bit rude that the 20050830 CVS drop is *still* on the front page of http://www.winehq.com/, even after everyone knows that it's missing a patch to compile cleanly.
Why not just add the patch to the package and slap it up as '20050830-1' ? Or add a link to the bugzilla entry to the front page ?
1. Adding the Bugzilla entry as a news item is a good idea. However, we're possibly close to a September drop, so at this point it's probably easiest to just wait for that. I'm very open to adding news items to the front page, so definitely feel free to drop me an email when you think of things like that. How about WWN coverage instead?
Depends.. Is the CVS drop distributed through other channels than the winehq front page? If not, and that one's going away in two days, then it's probably not worth it.. I'd be happy to write up a few lines for WWN if you want something in there (albeit my english does suck, so beware :-)).
2. CVS drops are just that - drops. They haven't been compiled on a bizillion systems or tested with real-world applications to ensure things aren't massively broken. Furthermore, no work was done to stabilize the release other than normal bug fixes. Instead, it represents a point in time where Alexandre ran the regression tests, things worked for him, and a tarball was made. There was discussion of that process changing after a beta release is made.
3. Binary packages are highly recommended unless you prefer to muck around occasionally with source code. That probably doesn't apply to you since you're reading wine-devel, but for 99% of the people in the world they should use the binaries. In theory we'll catch things at that point.
Thanks for the clarifications. I'm super newbie so I don't know how these things work - sorry! Just thought I'd point it out since it seemed noone else had :-/.
Molle Bestefich wrote:
If not, and that one's going away in two days, then it's probably not worth it..
Well, assuming that nobody cares about the hundreds of (potential) users put off during those two days :-) Isn't it possible to post a previous version or remove it completely? Is it lots of work, or something rather easy? (the question is genuine, I don't know anything about insides of Wine release process) Krzysztof
At 09:40 AM 9/29/2005, Brian Vincent wrote:
On 9/29/05, Molle Bestefich <molle.bestefich(a)gmail.com> wrote:
That said, it seems a bit rude that the 20050830 CVS drop is *still* on the front page of http://www.winehq.com/, even after everyone knows that it's missing a patch to compile cleanly.
<snip> Are you referring to a multiple defined struct option in winedump? I spent quite a while trying to compile this drop on Solaris 9 this morning. The multiple defined struct was easy to find/fix, but assembler having BIG troubles. Pretty sure it is using gas, since I renamed as and made a symlink to gas. </snip>
3. Binary packages are highly recommended unless you prefer to muck around occasionally with source code. That probably doesn't apply to you since you're reading wine-devel, but for 99% of the people in the world they should use the binaries. In theory we'll catch things at that point.
-Brian
If I could find a Solaris 9 binary of ANY wine version in the last year or so, I would be VERY happy!!! Google found a couple links to Solaris 9 binaries a couple years old or so, but the link didnt even work. Rob D
I have been trying to compile wine from source on Solaris 9 on x86. This has proven to be very frustrating. I had to rename a struct in one of the files in the tools/windump/main.c because of a name clash, but that was easy. I am pretty new to the whole compiling from source thing on Unix, but have built several packages (including Wine), on various Linux platforms and a few on Solaris. The main problem I seem to be having is with the assembler portion. All goes well until it gets to the d3d8 directory, and I get the following: ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ./d3d8.spec basetexture.o cubetexture.o d3d8_main.o device.o directx.o drawprim.o indexbuffer.o resource.o shader.o stateblock.o surface.o swapchain.o texture.o utils.o vertexbuffer.o volume.o volumetexture.o vshaderdeclaration.o d3d8.dll.dbg.o version.res -o d3d8.dll.so -L../../dlls -L../../dlls/wined3d -L../../dlls/user32 -L../../dlls/gdi32 -L../../dlls/advapi32 -L../../dlls/kernel32 -lwined3d -luser32 -lgdi32 -ladvapi32 -lkernel32 -L../../libs/wine -lwine -ldxguid -luuid -L/usr/openwin/lib -R/usr/openwin/lib -lSM -lICE -lXext -lX11 -lsocket -lnsl -lGL -L../../libs/port -lwine_port -lresolv -lsocket -lnsl Assembler: d3d8.dll-LsL4C9.spec.c "/var/tmp//ccpfivNU.s", line 515 : Illegal mnemonic "/var/tmp//ccpfivNU.s", line 515 : Syntax error "/var/tmp//ccpfivNU.s", line 516 : Illegal mnemonic "/var/tmp//ccpfivNU.s", line 516 : Syntax error "/var/tmp//ccpfivNU.s", line 517 : Illegal mnemonic "/var/tmp//ccpfivNU.s", line 517 : Syntax error "/var/tmp//ccpfivNU.s", line 518 : Illegal mnemonic "/var/tmp//ccpfivNU.s", line 518 : Syntax error "/var/tmp//ccpfivNU.s", line 519 : Illegal mnemonic "/var/tmp//ccpfivNU.s", line 519 : Syntax error "/var/tmp//ccpfivNU.s", line 520 : Illegal mnemonic "/var/tmp//ccpfivNU.s", line 520 : Syntax error "/var/tmp//ccpfivNU.s", line 522 : Illegal mnemonic "/var/tmp//ccpfivNU.s", line 522 : Syntax error "/var/tmp//ccpfivNU.s", line 523 : Illegal mnemonic "/var/tmp//ccpfivNU.s", line 523 : Syntax error "/var/tmp//ccpfivNU.s", line 524 : Illegal mnemonic "/var/tmp//ccpfivNU.s", line 524 : Syntax error "/var/tmp//ccpfivNU.s", line 525 : Illegal mnemonic "/var/tmp//ccpfivNU.s", line 525 : Syntax error "/var/tmp//ccpfivNU.s", line 526 : Illegal mnemonic "/var/tmp//ccpfivNU.s", line 526 : Syntax error "/var/tmp//ccpfivNU.s", line 527 : Illegal mnemonic "/var/tmp//ccpfivNU.s", line 527 : Syntax error "/var/tmp//ccpfivNU.s", line 555 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_WineDirect3DCreate" "/var/tmp//ccpfivNU.s", line 564 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_ChangeDisplaySettingsExW" "/var/tmp//ccpfivNU.s", line 573 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_GetClientRect" "/var/tmp//ccpfivNU.s", line 582 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_GetDC" "/var/tmp//ccpfivNU.s", line 591 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_GetDesktopWindow" "/var/tmp//ccpfivNU.s", line 600 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_GetPropA" "/var/tmp//ccpfivNU.s", line 609 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_GetSystemMetrics" "/var/tmp//ccpfivNU.s", line 618 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_ReleaseDC" "/var/tmp//ccpfivNU.s", line 627 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_SetWindowLongA" "/var/tmp//ccpfivNU.s", line 636 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_SetWindowPos" "/var/tmp//ccpfivNU.s", line 645 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_CreateDCA" "/var/tmp//ccpfivNU.s", line 654 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_DeleteDC" "/var/tmp//ccpfivNU.s", line 663 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_ExtEscape" "/var/tmp//ccpfivNU.s", line 672 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_GetDeviceCaps" "/var/tmp//ccpfivNU.s", line 681 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_GetDeviceGammaRamp" "/var/tmp//ccpfivNU.s", line 690 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_SetDeviceGammaRamp" "/var/tmp//ccpfivNU.s", line 699 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_RegOpenKeyA" "/var/tmp//ccpfivNU.s", line 708 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_RegQueryValueExA" "/var/tmp//ccpfivNU.s", line 717 : Warning: Illegal subtraction - symbols from different sections: "imports", ".L__wine_spec_DisableThreadLibraryCalls" "/var/tmp//ccpfivNU.s", line 726 : Warning: Illegal subtraction - symbol s from different sections: "imports", ".L__wine_spec_GetModuleHandleA" "/var/tmp//ccpfivNU.s", line 735 : Warning: Illegal subtraction - symbol s from different sections: "imports", ".L__wine_spec_GetProcAddress" "/var/tmp//ccpfivNU.s", line 744 : Warning: Illegal subtraction - symbol s from different sections: "imports", ".L__wine_spec_GetTickCount" "/var/tmp//ccpfivNU.s", line 753 : Warning: Illegal subtraction - symbol s from different sections: "imports", ".L__wine_spec_HeapAlloc" "/var/tmp//ccpfivNU.s", line 762 : Warning: Illegal subtraction - symbol s from different sections: "imports", ".L__wine_spec_HeapFree" "/var/tmp//ccpfivNU.s", line 771 : Warning: Illegal subtraction - symbol s from different sections: "imports", ".L__wine_spec_MultiByteToWideChar" "/var/tmp//ccpfivNU.s", line 775 : Syntax error "/var/tmp//ccpfivNU.s", line 777 : Syntax error winegcc: gcc failed. *** Error code 2 make: Fatal error: Command failed for target `d3d8.dll.so' Current working directory /export/home/opt/wine-20050830/dlls/d3d8 *** Error code 1 make: Fatal error: Command failed for target `d3d8' Current working directory /export/home/opt/wine-20050830/dlls *** Error code 1 make: Fatal error: Command failed for target `dlls' I thought at first that it was inadvertently using the AS assembler, but apparently the AS = gas in the Makefile says otherwise. Not sure where to go from here, since the /var/tmp files disappear immediately. gcc -v says it is 3.3.2 with posix thread model gas -v says 2.11 (i386-pc-solaris2.9) using BFD version 2.11 Configure sets up the Makefiles with: SHELL /bin/sh CC gcc CFLAGS -g -02 LN ln AS gas LD ld Thanks in advance for any help Rob Done
Le lun 03/10/2005 à 19:11, Rob D a écrit :
I have been trying to compile wine from source on Solaris 9 on x86. This has proven to be very frustrating.
I had to rename a struct in one of the files in the tools/windump/main.c because of a name clash, but that was easy.
I am pretty new to the whole compiling from source thing on Unix, but have built several packages (including Wine), on various Linux platforms and a few on Solaris. The main problem I seem to be having is with the assembler portion.
All goes well until it gets to the d3d8 directory, and I get the following: [snip] I thought at first that it was inadvertently using the AS assembler, but apparently the AS = gas in the Makefile says otherwise. Not sure where to go from here, since the /var/tmp files disappear immediately.
Are you sure your gcc is setup to use gas and not as? There's a section about that on Solaris in README. The same kind of problem can happen too with ld. Robert Lunnon makes some Solaris version of Wine, maybe you could find them. Vincent
On Mon, 3 Oct 2005, Rob D wrote:
I have been trying to compile wine from source on Solaris 9 on x86. This has proven to be very frustrating.
I had to rename a struct in one of the files in the tools/windump/main.c because of a name clash, but that was easy.
As a first step, could submit a patch fixing this problem?
I am pretty new to the whole compiling from source thing on Unix, but have built several packages (including Wine), on various Linux platforms and a few on Solaris. The main problem I seem to be having is with the assembler portion.
All goes well until it gets to the d3d8 directory, and I get the following:
Is this the first dll the Wine tries to compile? It looks like the assembler does not like the code generated by winebuild (not that I know anything about it, mind you) so I would expect every dll to get these errors. Also, I believe there's been quite a lot of changes in this area since the 20050830 release. It might be worth trying 20050930. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ May your Tongue stick to the Roof of your Mouth with the Force of a Thousand Caramels.
At 04:36 AM 10/4/2005, Francois Gouget wrote:
On Mon, 3 Oct 2005, Rob D wrote:
I have been trying to compile wine from source on Solaris 9 on x86. This has proven to be very frustrating.
I had to rename a struct in one of the files in the tools/windump/main.c because of a name clash, but that was easy.
As a first step, could submit a patch fixing this problem?
I am downloading 20050930 now. If it has the same problem, I will figure out how to submit a patch.
I am pretty new to the whole compiling from source thing on Unix, but have built several packages (including Wine), on various Linux platforms and a few on Solaris. The main problem I seem to be having is with the assembler portion.
All goes well until it gets to the d3d8 directory, and I get the following:
Is this the first dll the Wine tries to compile? It looks like the assembler does not like the code generated by winebuild (not that I know anything about it, mind you) so I would expect every dll to get these errors.
It is the first one that winegcc tries to build. This is after the gcc pass.
Also, I believe there's been quite a lot of changes in this area since the 20050830 release. It might be worth trying 20050930.
OK :)
-- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ May your Tongue stick to the Roof of your Mouth with the Force of a Thousand Caramels.
participants (7)
-
Brian Vincent -
Francois Gouget -
j0zue＠o2.pl -
Krzysztof Foltman -
Molle Bestefich -
Rob D -
Vincent Béron