http://bugs.winehq.com/show_bug.cgi?id=1030
------- Additional Comments From z_god@wanadoo.nl 2003-23-06 05:47 ------- Bug comments restored from Gmane.org:
I had problems with compiling a new version of wine. I analysed a problem and I have found that configure script does a very bad job.
It generates under some circumstances wrong macro __ASM_FUNC inside config.h file.
---------------WRONG---------------- /* Define to a macro to generate an assembly function directive */ #define __ASM_FUNC(name) ".def " __ASM_NAME(name) "; .scl 2; .type 32; .endef"
---------------GOOD---------------- /* Define to a macro to generate an assembly function directive */ #define __ASM_FUNC(name) ".type " __ASM_NAME(name) ",@function"
When I replaced a definition of __ASM_FUNC from previous release of wine, everything was compiled succesfully. Could you explain me what does this new feature mean?
---------see errorneous OUTPUT of COMPILER------- gcc -c -I. -I. -I../include -I../include -g -O2 -Wall -mpreferred-stack- boundary=2 -fPIC -D__WINE__ -DDLLDIR=""/usr/local/lib/wine"" -D_REENTRANT - I/usr/X11R6/include -o ldt.o ldt.c ldt.s: Assembler messages: ldt.s:1550: Error: unknown pseudo-op: `.def' ldt.s:1550: Error: unknown pseudo-op: `.scl' ldt.s:1550: Error: unrecognized symbol type "" ldt.s:1550: Warning: rest of line ignored; first ignored character is `3' ldt.s:1550: Error: unknown pseudo-op: `.endef' ldt.s:1556: Error: unknown pseudo-op: `.def' ldt.s:1556: Error: unknown pseudo-op: `.scl' ldt.s:1556: Error: unrecognized symbol type "" ldt.s:1556: Warning: rest of line ignored; first ignored character is `3' ldt.s:1556: Error: unknown pseudo-op: `.endef' ldt.s:1562: Error: unknown pseudo-op: `.def' ldt.s:1562: Error: unknown pseudo-op: `.scl' ldt.s:1562: Error: unrecognized symbol type "" ldt.s:1562: Warning: rest of line ignored; first ignored character is `3' ldt.s:1562: Error: unknown pseudo-op: `.endef' ldt.s:1568: Error: unknown pseudo-op: `.def' ldt.s:1568: Error: unknown pseudo-op: `.scl' ldt.s:1568: Error: unrecognized symbol type "" ldt.s:1568: Warning: rest of line ignored; first ignored character is `3' ldt.s:1568: Error: unknown pseudo-op: `.endef' ldt.s:1574: Error: unknown pseudo-op: `.def' ldt.s:1574: Error: unknown pseudo-op: `.scl' ldt.s:1574: Error: unrecognized symbol type "" ldt.s:1574: Warning: rest of line ignored; first ignored character is `3' ldt.s:1574: Error: unknown pseudo-op: `.endef' ldt.s:1580: Error: unknown pseudo-op: `.def' ldt.s:1580: Error: unknown pseudo-op: `.scl' ldt.s:1580: Error: unrecognized symbol type "" ldt.s:1580: Warning: rest of line ignored; first ignored character is `3' ldt.s:1580: Error: unknown pseudo-op: `.endef' ldt.s:1586: Error: unknown pseudo-op: `.def' ldt.s:1586: Error: unknown pseudo-op: `.scl' ldt.s:1586: Error: unrecognized symbol type "" ldt.s:1586: Warning: rest of line ignored; first ignored character is `3' ldt.s:1586: Error: unknown pseudo-op: `.endef' ldt.s:1593: Error: unknown pseudo-op: `.def' ldt.s:1593: Error: unknown pseudo-op: `.scl' ldt.s:1593: Error: unrecognized symbol type "" ldt.s:1593: Warning: rest of line ignored; first ignored character is `3' ldt.s:1593: Error: unknown pseudo-op: `.endef' make: *** [ldt.o] Error 1
------- Additional Comments From fojtik <at> htc.honeywell.cz 2002-09-17 02:18 ------- My OS configuration is: Slackware 7 + kernel 2.2.21 + gcc 3.0
------- Additional Comments From marcus <at> jet.franken.de 2002-09-17 15:06 ------- Can you ionclude the config.log file generated by configure please?
------- Additional Comments From fojtik <at> htc.honeywell.cz 2002-09-23 01:38 ------- Created an attachment (id=296) --> (http://bugs.winehq.com/attachment.cgi?id=296&action=view) The output of failing configure script
------- Additional Comments From fojtik <at> htc.honeywell.cz 2002-09-23 01:39 ------- Created an attachment (id=297) --> (http://bugs.winehq.com/attachment.cgi?id=297&action=view) The output of correct configure script - same enviroment
------- Additional Comments From fojtik <at> htc.honeywell.cz 2002-09-23 01:42 ------- You could kindly discard this bug. I tested against current snapshot and the bug did not occur any more. When I meet with it in the future, I'll reactivate this bug. I have archived failing configure script for a while if you want trace out the source of this bug.
------- Additional Comments From tony_lambregts <at> telusplanet.net 2002-09-29 23:57 ------- Marking as INVALID
------- Additional Comments From tony_lambregts <at> telusplanet.net 2003-03-26 15:35 ------- Closing