[ros-bugs] [Bug 3879] New: Various Build Problems in Win2k8 and Recent Trunk
ReactOS.Bugzilla at www.reactos.org
ReactOS.Bugzilla at www.reactos.org
Sun Nov 16 23:17:53 CET 2008
http://www.reactos.org/bugzilla/show_bug.cgi?id=3879
Summary: Various Build Problems in Win2k8 and Recent Trunk
Product: ReactOS
Version: TRUNK
Platform: VMWare 6
OS/Version: ReactOS
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: Win32
AssignedTo: ros-bugs at reactos.org
ReportedBy: reimer.daniel at freenet.de
QAContact: ros-bugs at reactos.org
Created an attachment (id=3246)
--> (http://www.reactos.org/bugzilla/attachment.cgi?id=3246)
"Fix" for 1st Problem
I have several Problems with building recent Trunk Versions on RosBE 1.3 on my
Win2K8 PC. The first problem is:
Reading build files...tools\rbuild\module.cpp:752 Test on unknown property
'_ELF
_' at D:/SVNTree/ReactOS/ntoskrnl/ntoskrnl-generic.rbuild(16)
mingw32-make: *** No rule to make target `bootcd'. Stop.
I "fixed" this with the patch above.
Then after a while I get this:
[CC] drivers\base\beep\beep.c
[WRC] obj-i386\drivers\base\beep\beep_beep.coff
[LD] output-i386\drivers\base\beep\beep.sys
obj-i386\drivers\base\beep\beep_beep.o: In function `BeepDPC at 16':
D:/SVNTree/ReactOS/include/psdk/intrin_x86.h:142: undefined reference to
`___syn
c_fetch_and_add_4'
obj-i386\drivers\base\beep\beep_beep.o: In function `BeepClose at 8':
D:/SVNTree/ReactOS/include/psdk/intrin_x86.h:142: undefined reference to
`___syn
c_fetch_and_add_4'
obj-i386\drivers\base\beep\beep_beep.o: In function `BeepUnload at 4':
D:/SVNTree/ReactOS/include/psdk/intrin_x86.h:142: undefined reference to
`___syn
c_fetch_and_add_4'
obj-i386\drivers\base\beep\beep_beep.o: In function `BeepStartIo at 8':
D:/SVNTree/ReactOS/include/psdk/intrin_x86.h:142: undefined reference to
`___syn
c_fetch_and_add_4'
D:/SVNTree/ReactOS/include/psdk/intrin_x86.h:142: undefined reference to
`___syn
c_fetch_and_add_4'
--
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the Ros-bugs
mailing list