Hi,
Robert if you are out there I think we want to try to branch for 0.2.6 sometime in the middle of
the coming week. Alex is going to merge his changes in to the trunk and then we should be mostly
ready. If Robert is not free and no one else wants to do it then I will plan on branching on
Wednesday. I expect we can let the 0.2.6 branch run for about a week so lets plan on shipping
0.2.6-final on 2005/03/16.
Thanks
Steven
__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/
Hi,
since my last svn update, I'm not able to compile ros on ros. It seems
that something is wrong with the pipes.
- Hartmut
f:\Sandbox\Ros\ReactOS>_make
ReactOS Build Number Generator
Current date : 2005-03-06
ROS Version : 0.3-CVS (build 20050306)
ar: creating zlib.host.a
ntoskrnl: [DLLTOOL] libntoskrnl.a
hal: [CC] hal.c
gcc: pipe: Invalid argument (EINVAL)
_make[1]: *** [hal.o] Error 1
_make: *** [hallib] Error 2
Hi,
compiling fails if KDBG = 0 and DBG = 1.
objects/ke.o: In function `InitializeListHead':
M:/Sandbox/ros_work/reactos/ntoskrnl/../include/ntos/rtl.h:96: undefined
reference to `KdbInit'
objects/ps.o: In function `PsUnlockProcess':
M:/Sandbox/ros_work/reactos/ntoskrnl/ps/process.c:2973: undefined
reference to `KdbDeleteProcessHook'
collect2: ld returned 1 exit status
_make[1]: *** [ntoskrnl.nostrip.exe] Error 1
_make: *** [ntoskrnl] Error 2
- Hartmut
blight(a)svn.reactos.com schrieb:
>Little KDB update ;-) If you have any problems and/or questions let me know. I hope it was tested enough and works well enough for everybody.
>
>
>Added files:
>trunk/reactos/media/drivers/etc/KDB.init
>trunk/reactos/ntoskrnl/dbg/i386/longjmp.S
>trunk/reactos/ntoskrnl/dbg/i386/setjmp.S
>trunk/reactos/ntoskrnl/dbg/kdb_cli.c
>trunk/reactos/ntoskrnl/dbg/kdb_expr.c
>trunk/reactos/ntoskrnl/dbg/kdb_string.c
>
>Updated files:
>trunk/reactos/Makefile
>trunk/reactos/drivers/input/keyboard/keyboard.c
>trunk/reactos/ntoskrnl/Makefile
>trunk/reactos/ntoskrnl/dbg/i386/i386-dis.c
>trunk/reactos/ntoskrnl/dbg/i386/kdb_help.S
>trunk/reactos/ntoskrnl/dbg/kdb.c
>trunk/reactos/ntoskrnl/dbg/kdb.h
>trunk/reactos/ntoskrnl/dbg/kdb_keyboard.c
>trunk/reactos/ntoskrnl/dbg/kdb_serial.c
>trunk/reactos/ntoskrnl/dbg/kdb_symbols.c
>trunk/reactos/ntoskrnl/include/internal/i386/ke.h
>trunk/reactos/ntoskrnl/include/internal/kd.h
>trunk/reactos/ntoskrnl/ke/catch.c
>trunk/reactos/ntoskrnl/ke/i386/trap.s
>trunk/reactos/ntoskrnl/ke/i386/tskswitch.S
>trunk/reactos/ntoskrnl/ke/kthread.c
>trunk/reactos/ntoskrnl/ke/main.c
>trunk/reactos/ntoskrnl/ps/w32call.c
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
>
I'm getting this after merging...
Filip/Eric, this seems to be related to your changes...any clue?
Assertion Irp->CancelRoutine == NULL failed at io/irp.c:310
Best regards,
Alex Ionescu
Hi Alex!
Good job! I let the testing go on through the night (23 hours) and started
testing your last commit, it's running great!
ion(a)svn.reactos.com wrote:
> Merge with blight's rewrite
>
>
> Added files:
> branches/alex_devel_branch/reactos/media/drivers/etc/KDB.init
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/i386/longjmp.S
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/i386/setjmp.S
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb_cli.c
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb_expr.c
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb_string.c
>
> Updated files:
> branches/alex_devel_branch/reactos/Makefile
> branches/alex_devel_branch/reactos/drivers/input/keyboard/keyboard.c
> branches/alex_devel_branch/reactos/ntoskrnl/Makefile
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/i386/i386-dis.c
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/i386/kdb_help.S
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb.c
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb.h
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb_keyboard.c
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb_serial.c
> branches/alex_devel_branch/reactos/ntoskrnl/dbg/kdb_symbols.c
> branches/alex_devel_branch/reactos/ntoskrnl/include/internal/i386/ke.h
> branches/alex_devel_branch/reactos/ntoskrnl/include/internal/kd.h
> branches/alex_devel_branch/reactos/ntoskrnl/io/iomgr.c
> branches/alex_devel_branch/reactos/ntoskrnl/ke/catch.c
> branches/alex_devel_branch/reactos/ntoskrnl/ke/i386/trap.s
> branches/alex_devel_branch/reactos/ntoskrnl/ke/i386/tskswitch.S
> branches/alex_devel_branch/reactos/ntoskrnl/ke/kthread.c
> branches/alex_devel_branch/reactos/ntoskrnl/ke/main.c
> branches/alex_devel_branch/reactos/ntoskrnl/ps/w32call.c
>
BTW, I'm getting this;
ntoskrnl: [CC] ke/kthread.c
ke/kthread.c: In function `KeInitializeThread':
ke/kthread.c:254: error: too many arguments to function `RtlZeroMemory'
ke/kthread.c:266: error: too many arguments to function `RtlZeroMemory'
ke/kthread.c:267: error: too many arguments to function `RtlZeroMemory'
make[1]: *** [ke/kthread.o] Error 1
make: *** [ntoskrnl] Error 2
Thanks,
James
Hi guys:
I was reading about subversion an in fact installed one svn server because I think that I could benefict from using a versioning system even doing non collaborative programming. Now the part that is related with ReactOS is that svn can be used locally, lite svnserve and (apache + svn modules) concurrently. I beleive you are using only or mostly:
svn://svn.reactos.com/
Are there any chances for us the firewalled to get an apache 2.x listening on port 80? I know you are using apache 1.3.x in www.reactos.com but the configuration should be very similar. I never mentioned anything like this when CVS because it was probably too wuch work for those administrating CVS but hey SVN is modern so it comes ready for it with little effort. So it won´t affect those using the subversion protocol directly. I always had intention to collaborate but never got the chance. I could never do proper checkouts from CVS using tunnels but this way will be direct so probably this could be my chance to get in and maybe get write acces after learning more about svn using it locally on my machine.
Thanks in advance
Regards Waldo Alvarez