Hi,
I find the problem is caused by msys or by msys's make.exe, the command
line:
$(CABMAN) /C bootdata/packages/reactos.dff /L $(BOOTCD_DIR)/reactos /I
Will be expanded like this:
$(CABMAN) c:/ bootdata/packages/reactos.dff c:/msys/1.0/L
(BOOTCD_DIR)/reactos i:/
I don't know why. And when I use "mingw32-make bootcd", everything is ok.
And if we use cabman.exe in msys, the command line should like this:
$(CABMAN) //C bootdata/packages/reactos.dff //L $(BOOTCD_DIR)/reactos //I
It goes well.
-----邮件原件-----
发件人: ros-dev-bounces(a)reactos.com [mailto:ros-dev-bounces@reactos.com] 代
表 Hartmut Birr
发送时间: 2005年5月5日 19:32
收件人: ReactOS Development List
主题: Re: [ros-dev] about rules.mak, a small bug fixed
Your patch breaks compiling on windows without msys. I've commit a
different fix which will solve your problem. There does exist one
problem, it isn't possible to build the bootcd. There is somewhere a
'c:/..' on the path, which isn't correct within a simulated posix system
like msys.
- Hartmut
greatlrd(a)svn.reactos.com wrote:
> tinus
> implement MouseResolution setting
>
> Me (Magnus Olsen)
> remove old psuax drv from hiveinst.inf and add tinus mouse drv settings
> add MouseResolution setting to reg
>
>
>
>
> Updated files:
> trunk/reactos/bootdata/hiveinst.inf
> trunk/reactos/bootdata/hivesys.inf
> trunk/reactos/drivers/input/i8042prt/i8042prt.h
> trunk/reactos/drivers/input/i8042prt/mouse.c
>
The mouse is moving slowly in my machine.
What are the possible values for MouseResolution setting in Hivesys.inf
Regards
Gerard
weiden(a)svn.reactos.com wrote:
> - directly forward GetSecurityDescriptorLength to NTDLL.RtlLengthSecurityDescriptorguard dumping the stack trace to prevent infinite exception loopsguard dumping the stack trace to prevent infinite exception loops
my svn client somehow screwed up the message, it's supposed to be only
- directly forward GetSecurityDescriptorLength to
NTDLL.RtlLengthSecurityDescriptor
Best Regards,
Thomas
hbirr(a)svn.reactos.com wrote:
>- Free always the name string and the completion context in IopDeleteFile.
>
>
>Updated files:
>trunk/reactos/ntoskrnl/io/file.c
>
>
>
The lack of a Device Object signifies there is something REALLY wrong
with the file, and should be treated as invalid. It might not be wise to
do any further operations on it, since they probably already have been done.
Best regards,
Alex Ionescu
Mark Junker wrote:
> The build system seems to be sub-optimal <g>.
There is a new xml build system coming into place soon which is much better
than the current one.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
1) Assertion gets hit on:
Assertion PdoNameInfo->Name.Length failed at io/deviface.c:606
Entered debugger on embedded INT3 at 0x0008:0x80005813.
2) Cmd.exe outputs garbage.
3) DHCP crashes during boot.
Best regards,
Alex Ionescu
hbirr(a)svn.reactos.com wrote:
>- Guard the copying to the IOSB.
>- Do the main processing on success or if previous STATUS_PENDING was returned.
> Do not use some of the IRP and FO flags at this point.
>
>
Ok, I was going to complain about this, but I realize that it must be
used since defintely some parts of ROS don't work properly with those
flags set.
>- Set all results before signaling the events.
>- Signal the FO event previous the user event.
>- Made the code a little bit shorter.
>
>
>
I like your changes and have no complaints, except that the signaling
semantics of the File/User events should be different in the failure
case (my "else" path). You've completely removed that path and thus
changed the logic.
Best regards,
Alex Ionescu
When I compile reactos, I find a problem, my make report:
string: [DEPENDS] i386/.wcsrchr.d
/bin/sh.exe: ....toolsdepends.exe: command not found
make[1]: *** [i386/.wcsrchr.d] Error 127
make: *** [string] Error 2
I find the problem is that sh.exe ignored ��\��.
The command line is :
@gcc -Wall -Werror -D_DISABLE_TIDENTS -D__USE_W32API -fno-strict-aliasing
-O6 -
I. -I../../include -I../../w32api/include -pipe -march=i486 -D_M_IX86 -Os
-Wno-s
trict-aliasing -ftracer -momit-leaf-frame-pointer
-mpreferred-stack-boundary=2 -
funit-at-a-time -fweb -g -M i386/wcsrchr.s | ..\..\tools\depends.exe i386
i386/.
wcsrchr.d
And ��..\..\tools\depends.exe�� was changed into ��....tools\depends.exe��
by sh.exe
My msys is MSYS-1.0.10
So I made a patch on rules.mak , and the problem solved .
F:\SVNReactos\reactos>svn diff rules.mak
Index: rules.mak
===================================================================
--- rules.mak (修订版 14957�?
+++ rules.mak (工作拷贝)
@@ -122,7 +122,7 @@
export NASM_CMD = $(Q)nasmw
export DOSCLI = yes
export FLOPPY_DIR = A:
-export SEP := \$(EMPTY_VAR)
+export SEP := /$(EMPTY_VAR)
export PIPE := -pipe
endif