Menu
▾
▴
reactos-kernel
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(64) |
Oct
(438) |
Nov
(183) |
Dec
|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
(132) |
May
(466) |
Jun
(366) |
Jul
(392) |
Aug
(31) |
Sep
(18) |
Oct
|
Nov
|
Dec
|
|
From: David K. <kr...@mb...> - 2002-05-19 20:50:34
|
Machine is 2*866 PIII, 1024 MB RAM
booted with aboot.bat, config: kdbg=1, dbg=1, acpi=1.
There are two problems with sectest.
The first :
The makefile of sectest breaks the build process:
make -C apps/sectest implib
: Invalid argument
: No such file or directoryk
'. Stop.*** No rule to make target `tools/helper.mk
make[1]: Entering directory `C:/ros/reactos/apps/sectest'
make[1]: Leaving directory `C:/ros/reactos/apps/sectest'
make: *** [sectest_implib] Error 2
If I copy there makefile from directory isotest and remade it for sectest
build process goes its way.
Perhaps wrong EOF or EOLN ? I don`t know.
make -d :
make -C apps/sectest implib
CreateProcess(c:mingwbinmake.exe,make -C apps/sectest implib,...)
Putting child 0x003d9d38 (sectest_implib) PID 10437696 on the chain.
Live child 0x003d9d38 (sectest_implib) PID 10437696
GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
Built for mingw32
Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 2000
Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Report bugs to <bug...@gn...>.
Reading makefiles...
: Invalid argument
: No such file or directoryk
Reading makefile `Makefile'...
' (search path) (no ~ expansion)...
make[1]: Entering directory `C:/ros/reactos/apps/sectest'
' (search path) (no ~ expansion)...
Updating makefiles....
'.onsidering target file `tools/helper.mk
' does not exist.per.mk
'.Looking for an implicit rule for `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.o'.ying implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.c'.ying implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.cc'.ing implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.C'.ying implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.cpp'.ng implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.p'.ying implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.f'.ying implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.F'.ying implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.r'.ying implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.s'.ying implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.S'.ying implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.mod'.ng implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.sh'.ing implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
,v'.ying implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
,v'.ying implicit prerequisite `tools/RCS/helper.mk
'.Trying pattern rule with stem `helper.mk
'.Trying implicit prerequisite `tools/RCS/helper.mk
'.Trying pattern rule with stem `helper.mk
'.Trying implicit prerequisite `tools/s.helper.mk
'.Trying pattern rule with stem `helper.mk
'.Trying implicit prerequisite `tools/SCCS/s.helper.mk
'.Trying pattern rule with stem `helper.mk
.o'.ying implicit prerequisite `tools/helper.mk
.o'.oking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
'. Trying pattern rule with stem `helper.mk
.c'.rying implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.cc'.ying implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.C'.rying implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.cpp'.ing implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.p'.rying implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.f'.rying implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.F'.rying implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.r'.rying implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.s'.rying implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.S'.rying implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.mod'.ing implicit prerequisite `tools/helper.mk
.o'.rying pattern rule with stem `helper.mk
.o,v'.ing implicit prerequisite `tools/helper.mk
.o'.rying pattern rule with stem `helper.mk
.o,v'.ing implicit prerequisite `tools/RCS/helper.mk
.o'.rying pattern rule with stem `helper.mk
.o'.rying implicit prerequisite `tools/RCS/helper.mk
.o'.rying pattern rule with stem `helper.mk
.o'.rying implicit prerequisite `tools/s.helper.mk
.o'.rying pattern rule with stem `helper.mk
.o'.rying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.c'.rying implicit prerequisite `tools/helper.mk
.c'.ooking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
'. Trying pattern rule with stem `helper.mk
.y'.Trying implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.l'.Trying implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.w'.Trying implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.w'.Trying implicit prerequisite `tools/helper.mk
.c'.Trying pattern rule with stem `helper.mk
.c,v'.ying implicit prerequisite `tools/helper.mk
.c'.Trying pattern rule with stem `helper.mk
.c,v'.ying implicit prerequisite `tools/RCS/helper.mk
.c'.Trying pattern rule with stem `helper.mk
.c'.Trying implicit prerequisite `tools/RCS/helper.mk
.c'.Trying pattern rule with stem `helper.mk
.c'.Trying implicit prerequisite `tools/s.helper.mk
.c'.Trying pattern rule with stem `helper.mk
.c'.Trying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.y'.Trying implicit prerequisite `tools/helper.mk
.y'.Looking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
.y'. Trying pattern rule with stem `helper.mk
.y,v'.rying implicit prerequisite `tools/helper.mk
.y'. Trying pattern rule with stem `helper.mk
.y,v'.rying implicit prerequisite `tools/RCS/helper.mk
.y'. Trying pattern rule with stem `helper.mk
.y'. Trying implicit prerequisite `tools/RCS/helper.mk
.y'. Trying pattern rule with stem `helper.mk
.y'. Trying implicit prerequisite `tools/s.helper.mk
.y'. Trying pattern rule with stem `helper.mk
.y'. Trying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.l'.Trying implicit prerequisite `tools/helper.mk
.l'.Looking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
.l'. Trying pattern rule with stem `helper.mk
.l,v'.rying implicit prerequisite `tools/helper.mk
.l'. Trying pattern rule with stem `helper.mk
.l,v'.rying implicit prerequisite `tools/RCS/helper.mk
.l'. Trying pattern rule with stem `helper.mk
.l'. Trying implicit prerequisite `tools/RCS/helper.mk
.l'. Trying pattern rule with stem `helper.mk
.l'. Trying implicit prerequisite `tools/s.helper.mk
.l'. Trying pattern rule with stem `helper.mk
.l'. Trying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.w'.Trying implicit prerequisite `tools/helper.mk
.w'.Looking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
.w'. Trying pattern rule with stem `helper.mk
.w,v'.rying implicit prerequisite `tools/helper.mk
.w'. Trying pattern rule with stem `helper.mk
.w,v'.rying implicit prerequisite `tools/RCS/helper.mk
.w'. Trying pattern rule with stem `helper.mk
.w'. Trying implicit prerequisite `tools/RCS/helper.mk
.w'. Trying pattern rule with stem `helper.mk
.w'. Trying implicit prerequisite `tools/s.helper.mk
.w'. Trying pattern rule with stem `helper.mk
.w'. Trying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.w'.Rejecting impossible implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.cc'.ying implicit prerequisite `tools/helper.mk
.cc'.oking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
.cc'.rying pattern rule with stem `helper.mk
.cc,v'.ing implicit prerequisite `tools/helper.mk
.cc'.rying pattern rule with stem `helper.mk
.cc,v'.ing implicit prerequisite `tools/RCS/helper.mk
.cc'.rying pattern rule with stem `helper.mk
.cc'.rying implicit prerequisite `tools/RCS/helper.mk
.cc'.rying pattern rule with stem `helper.mk
.cc'.rying implicit prerequisite `tools/s.helper.mk
.cc'.rying pattern rule with stem `helper.mk
.cc'.rying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.C'.rying implicit prerequisite `tools/helper.mk
.C'.ooking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
.C'.Trying pattern rule with stem `helper.mk
.C,v'.ying implicit prerequisite `tools/helper.mk
.C'.Trying pattern rule with stem `helper.mk
.C,v'.ying implicit prerequisite `tools/RCS/helper.mk
.C'.Trying pattern rule with stem `helper.mk
.C'.Trying implicit prerequisite `tools/RCS/helper.mk
.C'.Trying pattern rule with stem `helper.mk
.C'.Trying implicit prerequisite `tools/s.helper.mk
.C'.Trying pattern rule with stem `helper.mk
.C'.Trying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.cpp'.ing implicit prerequisite `tools/helper.mk
.cpp'.king for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
.cpp'.ying pattern rule with stem `helper.mk
.cpp,v'.ng implicit prerequisite `tools/helper.mk
.cpp'.ying pattern rule with stem `helper.mk
.cpp,v'.ng implicit prerequisite `tools/RCS/helper.mk
.cpp'.ying pattern rule with stem `helper.mk
.cpp'.ying implicit prerequisite `tools/RCS/helper.mk
.cpp'.ying pattern rule with stem `helper.mk
.cpp'.ying implicit prerequisite `tools/s.helper.mk
.cpp'.ying pattern rule with stem `helper.mk
.cpp'.ying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.p'.rying implicit prerequisite `tools/helper.mk
.p'.ooking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
'. Trying pattern rule with stem `helper.mk
.web'.ying implicit prerequisite `tools/helper.mk
.p'.Trying pattern rule with stem `helper.mk
.p,v'.ying implicit prerequisite `tools/helper.mk
.p'.Trying pattern rule with stem `helper.mk
.p,v'.ying implicit prerequisite `tools/RCS/helper.mk
.p'.Trying pattern rule with stem `helper.mk
.p'.Trying implicit prerequisite `tools/RCS/helper.mk
.p'.Trying pattern rule with stem `helper.mk
.p'.Trying implicit prerequisite `tools/s.helper.mk
.p'.Trying pattern rule with stem `helper.mk
.p'.Trying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.web'.ying implicit prerequisite `tools/helper.mk
.web'.oking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
.web'.rying pattern rule with stem `helper.mk
.web,v'.ing implicit prerequisite `tools/helper.mk
.web'.rying pattern rule with stem `helper.mk
.web,v'.ing implicit prerequisite `tools/RCS/helper.mk
.web'.rying pattern rule with stem `helper.mk
.web'.rying implicit prerequisite `tools/RCS/helper.mk
.web'.rying pattern rule with stem `helper.mk
.web'.rying implicit prerequisite `tools/s.helper.mk
.web'.rying pattern rule with stem `helper.mk
.web'.rying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.f'.rying implicit prerequisite `tools/helper.mk
.f'.ooking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
'. Trying pattern rule with stem `helper.mk
.F'.Trying implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.r'.Trying implicit prerequisite `tools/helper.mk
.f'.Trying pattern rule with stem `helper.mk
.f,v'.ying implicit prerequisite `tools/helper.mk
.f'.Trying pattern rule with stem `helper.mk
.f,v'.ying implicit prerequisite `tools/RCS/helper.mk
.f'.Trying pattern rule with stem `helper.mk
.f'.Trying implicit prerequisite `tools/RCS/helper.mk
.f'.Trying pattern rule with stem `helper.mk
.f'.Trying implicit prerequisite `tools/s.helper.mk
.f'.Trying pattern rule with stem `helper.mk
.f'.Trying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.F'.Trying implicit prerequisite `tools/helper.mk
.F'.Looking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
.F'. Trying pattern rule with stem `helper.mk
.F,v'.rying implicit prerequisite `tools/helper.mk
.F'. Trying pattern rule with stem `helper.mk
.F,v'.rying implicit prerequisite `tools/RCS/helper.mk
.F'. Trying pattern rule with stem `helper.mk
.F'. Trying implicit prerequisite `tools/RCS/helper.mk
.F'. Trying pattern rule with stem `helper.mk
.F'. Trying implicit prerequisite `tools/s.helper.mk
.F'. Trying pattern rule with stem `helper.mk
.F'. Trying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.r'.Trying implicit prerequisite `tools/helper.mk
.r'.Looking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
'. Trying pattern rule with stem `helper.mk
.l'. Rejecting impossible implicit prerequisite `tools/helper.mk
.r'. Trying pattern rule with stem `helper.mk
.r,v'.rying implicit prerequisite `tools/helper.mk
.r'. Trying pattern rule with stem `helper.mk
.r,v'.rying implicit prerequisite `tools/RCS/helper.mk
.r'. Trying pattern rule with stem `helper.mk
.r'. Trying implicit prerequisite `tools/RCS/helper.mk
.r'. Trying pattern rule with stem `helper.mk
.r'. Trying implicit prerequisite `tools/s.helper.mk
.r'. Trying pattern rule with stem `helper.mk
.r'. Trying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.F'.ejecting impossible implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.r'.ejecting impossible implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.s'.rying implicit prerequisite `tools/helper.mk
.s'.ooking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
'. Trying pattern rule with stem `helper.mk
.S'.Trying implicit prerequisite `tools/helper.mk
.s'.Trying pattern rule with stem `helper.mk
.s,v'.ying implicit prerequisite `tools/helper.mk
.s'.Trying pattern rule with stem `helper.mk
.s,v'.ying implicit prerequisite `tools/RCS/helper.mk
.s'.Trying pattern rule with stem `helper.mk
.s'.Trying implicit prerequisite `tools/RCS/helper.mk
.s'.Trying pattern rule with stem `helper.mk
.s'.Trying implicit prerequisite `tools/s.helper.mk
.s'.Trying pattern rule with stem `helper.mk
.s'.Trying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.S'.Trying implicit prerequisite `tools/helper.mk
.S'.Looking for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
.S'. Trying pattern rule with stem `helper.mk
.S,v'.rying implicit prerequisite `tools/helper.mk
.S'. Trying pattern rule with stem `helper.mk
.S,v'.rying implicit prerequisite `tools/RCS/helper.mk
.S'. Trying pattern rule with stem `helper.mk
.S'. Trying implicit prerequisite `tools/RCS/helper.mk
.S'. Trying pattern rule with stem `helper.mk
.S'. Trying implicit prerequisite `tools/s.helper.mk
.S'. Trying pattern rule with stem `helper.mk
.S'. Trying implicit prerequisite `tools/SCCS/s.helper.mk
'. Trying pattern rule with stem `helper.mk
.S'.ejecting impossible implicit prerequisite `tools/helper.mk
'. Trying pattern rule with stem `helper.mk
.mod'.ing implicit prerequisite `tools/helper.mk
.mod'.king for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
.mod'.ying pattern rule with stem `helper.mk
.mod,v'.ng implicit prerequisite `tools/helper.mk
.mod'.ying pattern rule with stem `helper.mk
.mod,v'.ng implicit prerequisite `tools/RCS/helper.mk
.mod'.ying pattern rule with stem `helper.mk
.mod'.ying implicit prerequisite `tools/RCS/helper.mk
.mod'.ying pattern rule with stem `helper.mk
.mod'.ying implicit prerequisite `tools/s.helper.mk
.mod'.ying pattern rule with stem `helper.mk
.mod'.ying implicit prerequisite `tools/SCCS/s.helper.mk
'.Trying pattern rule with stem `helper.mk
.c'.jecting impossible implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.cc'.ecting impossible implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.C'.jecting impossible implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.cpp'.cting impossible implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.p'.jecting impossible implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.f'.jecting impossible implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.F'.jecting impossible implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.r'.jecting impossible implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.s'.jecting impossible implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.S'.jecting impossible implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.mod'.cting impossible implicit prerequisite `tools/helper.mk
'.Trying pattern rule with stem `helper.mk
.sh'.ing implicit prerequisite `tools/helper.mk
.sh'.king for a rule with intermediate file `tools/helper.mk
Avoiding implicit rule recursion.
.sh'.ying pattern rule with stem `helper.mk
.sh,v'.ng implicit prerequisite `tools/helper.mk
.sh'.ying pattern rule with stem `helper.mk
.sh,v'.ng implicit prerequisite `tools/RCS/helper.mk
.sh'.ying pattern rule with stem `helper.mk
.sh'.ying implicit prerequisite `tools/RCS/helper.mk
.sh'.ying pattern rule with stem `helper.mk
.sh'.ying implicit prerequisite `tools/s.helper.mk
.sh'.ying pattern rule with stem `helper.mk
.sh'.ying implicit prerequisite `tools/SCCS/s.helper.mk
'.No implicit rule found for `tools/helper.mk
'.Finished prerequisites of target file `tools/helper.mk
'.ust remake target `tools/helper.mk
'. Stop.*** No rule to make target `tools/helper.mk
make[1]: Leaving directory `C:/ros/reactos/apps/sectest'
Reaping losing child 0x003d9d38 PID 10437696
make: *** [sectest_implib] Error 2
Removing child 0x003d9d38 PID 10437696 from chain.
C:rosreactos>
The second :
After runnig sectest I got :
Section Test
Bug detected code: 0x1D
Divide Error Exception: 0(0)
ntoskrnl.exe: _ObFindObject
cr2 0 cr3 3f7ef000
ntoskrnl.exe: _ObCreateObject@20
_MmCreateDataFileSection
_NtCreateSection@28
_interrupt_handler2e
David
|
|
From: Steven E. <Ste...@ya...> - 2002-05-19 19:04:26
|
> Now edit exits without error. > > But after edit exits, the console is adding ` before > chars readed from the keyboard. > > Terminal is unusable for that. Typing reboot results in : > > Unknown command `r > Unknown command `e > Unknown command `b > Unknown command `o > Unknown command `o > Unknown command `t > > or in second > > Unknown command `r` > Unknown command `e` > Unknown command `b` > Unknown command `o` > Unknown command `o` > Unknown command `t`. > > Backround in edit is not redrawing while menu exits or moves. This used to happen all the time with edit/dflat. I was working on breaking dflat in to a dll so we could use it for other console applications before I Started working on the wine stuff. You want to take it over? Or anyone else? I don't really have the time to Mess with it right now and it still needs to be fixed. Thanks Steven "Every revolution was once a thought in one man's mind" - Ralph Waldo Emerson |
|
From: KJK::Hyperion <no...@li...> - 2002-05-19 18:26:16
|
At 02.09 19/05/2002, you wrote: >>>Would not suprise me if there is a switch to turn this off. >>AFAIK, no. I've examined the whole output of gcc -v --help, found nothing >>useful >You should check the info page for gcc to be sure there is not a flag. Negative. I had to explore the internals manual. I found out that, for executable formats not supporting initialization sections, __main calls the constructors for static C++ objects at startup, and the destructors before shutdown. I knew of this requirement for static CRTs (I read an article of Pietrek on MSDN Magazine on rolling your own CRT), but GCC is the only compiler I know of that inserts an explicit call to the initializator, instead of simply doing the initialization before calling main() >Also, just name your entry point something besides main perhaps? That's what I did. But this doesn't make the problem go away: sometime in the future, we'll need to provide a static CRT for POSIX+ programs. I'll try to add -lgcc, like the documents suggest, and implement atexit() in psxdll. That should do the trick >And by the way, I've had my share of problems with Borland's C compiler. We're not talking about Borland C |
|
From: David K. <kr...@mb...> - 2002-05-19 16:25:18
|
Now edit exits without error. But after edit exits, the console is adding ` before chars readed from the keyboard. Terminal is unusable for that. Typing reboot results in : Unknown command `r Unknown command `e Unknown command `b Unknown command `o Unknown command `o Unknown command `t or in second Unknown command `r` Unknown command `e` Unknown command `b` Unknown command `o` Unknown command `o` Unknown command `t`. Backround in edit is not redrawing while menu exits or moves. David Casper Hornstrup wrote: > søn, 2002-05-19 kl. 17:10 skrev David Welch: > >>On Sun, May 19, 2002 at 03:46:05PM +0200, Casper Hornstrup wrote: >> >>>Fixed, please try again. >>> >> >>I do not think this fix is correct; we can certainly try to lock an >>fast mutex when the current thread doesn't already own it but if the >>current thread does already own it then we will deadlock since fast >>mutexes aren't recursive. The real problem is locking the address space >>when we already own it so I had have reverted your changes and modified >>section.c not to do this. > > > Yes, you are right, I wasn't thinking there. > > > > _______________________________________________________________ > Hundreds of nodes, one monster rendering program. > Now that's a super model! Visit http://clustering.foundries.sf.net/ > > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel > |
|
From: Casper H. <ch...@us...> - 2002-05-19 16:10:09
|
s=F8n, 2002-05-19 kl. 17:21 skrev Nick J. Date: > Just as an aside, IMHO WinNT driver/app compatibility doesn't even mean > trying to write an NTFS driver.=20 I agree, that drivers are not necesarry for compatibility, but ReactOS will not be as fun without certain drivers like IDE VGA, TCP/IP, etc. MS provided helper drivers and support library libraries like NDIS and storage stack support libraries would be necesarry because OEM drivers depend on them and nobody will create them.=20 A Linux type filesystem would be just as > compatible (providing your not using any disk fixing/editing programs) an= d > would have all the security of a Linux box's FS. Ext2fs security will be enough for some, but not for all. |
|
From: Nick J. D. <nic...@ya...> - 2002-05-19 15:22:20
|
Hi guys, ----- Original Message ----- From: <we...@cw...> To: <rea...@li...> Sent: Tuesday, May 14, 2002 2:23 PM Subject: Re: [ros-kernel] Fwd: Reorganizing the cvs repository before starting reactos.org > Quoting Casper Hornstrup <ch...@us...>: > > > > I consider win32k.sys as part of the Windows NT executive architecture > > and not part of the Win32 subsystem. Therefore I believe win32k.sys > > should be in the reactos module. I however, see no reason for building > > the Win32 subsystem if you are not developing or distributing this > > part, so the Win32 subsystem should go in it's own module. > > > I think that's an artifical distinction: win32k is useless without user32 > or gdi32 both of which require kernel32 and indirectly csrss and so on. The > project ought to recognize that, if reactos has a use at all, then running > win32 programs is it. POSIX and OS/2 subsystems are interesting but if this > functionality is all that is required then there are already operating systems > that do it better. I know I've been away for a while and I'm butting straight in, but I see exactly what David means. The aim of ReactOS is to provide an open source operating system that is compatible with Windows NT apps and drivers. In my interpretation this means that anything else is nice, but by the by. I have no problem with people creating other subsystems (a POSIX subsystem for example would be great), but I think the focus should be kept on getting the WIN32 API up and running and making the kernel as bug free as possible. If an OS/2 project wants to use the ROS kernel and write an OS/2 compatible API then fine. But it won't be ROS. ROS is an NT compatible OS. Full stop. Just as an aside, IMHO WinNT driver/app compatibility doesn't even mean trying to write an NTFS driver. A Linux type filesystem would be just as compatible (providing your not using any disk fixing/editing programs) and would have all the security of a Linux box's FS. Well, that's my twopence worth. ;-) Nick. -- Nick Date Bath, England, United Kingdom --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.362 / Virus Database: 199 - Release Date: 07/05/2002 _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
|
From: Casper H. <ch...@us...> - 2002-05-19 14:24:25
|
s=F8n, 2002-05-19 kl. 17:10 skrev David Welch: > On Sun, May 19, 2002 at 03:46:05PM +0200, Casper Hornstrup wrote: > > Fixed, please try again. > >=20 > I do not think this fix is correct; we can certainly try to lock an=20 > fast mutex when the current thread doesn't already own it but if the > current thread does already own it then we will deadlock since fast=20 > mutexes aren't recursive. The real problem is locking the address space > when we already own it so I had have reverted your changes and modified=20 > section.c not to do this. Yes, you are right, I wasn't thinking there. |
|
From: David W. <we...@cw...> - 2002-05-19 14:09:51
|
On Sun, May 19, 2002 at 03:46:05PM +0200, Casper Hornstrup wrote: > Fixed, please try again. > I do not think this fix is correct; we can certainly try to lock an fast mutex when the current thread doesn't already own it but if the current thread does already own it then we will deadlock since fast mutexes aren't recursive. The real problem is locking the address space when we already own it so I had have reverted your changes and modified section.c not to do this. |
|
From: Casper H. <ch...@us...> - 2002-05-19 13:49:30
|
s=F8n, 2002-05-19 kl. 14:21 skrev David Kredba: > Curren cvs tree, config kdbg=3D1,dbg=3D1,acpi=3D1, booted with aboot.bat,= =20 > 1024MB RAM. >=20 > When I run edit.exe and try to open menu I get this: >=20 > Pid: 7 <edit> >=20 > PageFaultException: 14(4) Assertion FastMutex -> Owner !=3D=20 > KeGetCurrentThread() failed at ex /fmutex.c: 41 Fixed, please try again. |
|
From: David K. <kr...@mb...> - 2002-05-19 12:22:05
|
Curren cvs tree, config kdbg=1,dbg=1,acpi=1, booted with aboot.bat, 1024MB RAM. When I run edit.exe and try to open menu I get this: Pid: 7 <edit> PageFaultException: 14(4) Assertion FastMutex -> Owner != KeGetCurrentThread() failed at ex /fmutex.c: 41 Pid: 6 <shell> Frames : ntoskrnl.exe : _KeBugCheck@4 _ExUnregisterCallback@4 _MmLockAddressSpace _MmUnmapViewOfSection@8 _MmReleaseMemoryArea _MmReleaseMmInfo _PiDeleteProcess@4 _ObpPerformRetentionChecks _ObpPerformRetentionChecks _PiDeleteThread@4 _ObpPerformRetentionChecks _ObpPerformRetentionChecks _NtClose@4 _interrupt_handler2e hal.dll: _HalpStartEnumerator Bug detected code: 0x1D Divide Error Exception: 0(0) Frames: ntoskrnl.exe: _DbgBreakPoint@0 _KeBugCheckEx@20 _KeBugCheck@4 _ExUnregisterCallback@4 _MmLockAddressSpace _MmUnmapViewOfSection@8 _MmReleaseMemoryArea _MmReleaseMmInfo _PiDeleteProcess@4 _ObpPerformRetentionChecks _ObpPerformRetentionChecks _PiDeleteThread@4 _ObpPerformRetentionChecks _ObpPerformRetentionChecks _NtClose@4 _interrupt_handler2e hal.dll: _HalpStartEnumerator David |
|
From: Casper H. <ch...@us...> - 2002-05-19 10:04:03
|
s=F8n, 2002-05-19 kl. 00:13 skrev KJK::Hyperion: > That's not the problem. crthybrid.c, in my case, implements the entry poi= nt=20 > (__PdxLdrEntry, with the same signature as NtProcessStartup), then calls=20 > exit() with the return value of main() as parameter, because it's, as the= =20 > name suggests, a static CRT for Win32-POSIX+ hybrids, that converts/impor= ts=20 > the Win32 environment, invocation, standard file descriptors, current=20 > directory, etc. and then calls main() >=20 > The idea is to have something clean and self-contained, and containing=20 > exactly what the code says, no more no less, because it's easier to debug >=20 > The problem is that the C frontend of GCC *always* inserts a call to=20 > _main() at the beginning of all functions called main(), without me askin= g=20 > for, or even *wanting* it. I'll just insert a dummy _main() in crthybrid.= c=20 > until it's fixed, but I *really* hate this Try bringing this up on the gcc mailing lists. They probably have a reason for doing it. |
|
From: Steven E. <Ste...@ya...> - 2002-05-19 00:21:58
|
> You should see about getting some drugs for this stress > before you have a > stroke. Or laying off the drugs before your have a stroke =P "Every revolution was once a thought in one man's mind" - Ralph Waldo Emerson |
|
From: Rex J. <re...@lv...> - 2002-05-19 00:09:32
|
At 12:20 AM 5/19/02 +0200, you wrote: >At 22.47 18/05/2002, you wrote: > >>Would not suprise me if there is a switch to turn this off. > >AFAIK, no. I've examined the whole output of gcc -v --help, found nothing >useful You should check the info page for gcc to be sure there is not a flag. Also, just name your entry point something besides main perhaps? And by the way, I've had my share of problems with Borland's C compiler. >>Only happens once per process activation so its not really a performance >>issue > >Of course no. But I can't accept a C compiler doing this You should see about getting some drugs for this stress before you have a stroke. Rex Jolliff re...@lv... |
|
From: KJK::Hyperion <no...@li...> - 2002-05-18 22:23:22
|
At 22.47 18/05/2002, you wrote:
>>Why the hell does it do this? Why does the compiler try to be smarter
>>than me? How can I tell the compiler to compile *exactly* what I say, and
>>not generate useless/superfluous code? Borland C++ doesn't do it, for example:
>Just add an "extern int _main() { return 0; };" (or whatever the call
>signature is).
I'll do that, then. But I hate this
>Would not suprise me if there is a switch to turn this off.
AFAIK, no. I've examined the whole output of gcc -v --help, found nothing
useful
>Only happens once per process activation so its not really a performance issue
Of course no. But I can't accept a C compiler doing this
|
|
From: KJK::Hyperion <no...@li...> - 2002-05-18 22:23:18
|
At 23.02 18/05/2002, you wrote: > > > > testfork.o(.text+0x43):testfork.c: undefined reference to `__main' > > > > make: *** [testfork.nostrip.exe] Error 1 > > >well, you need your custom __main function then. > > erm... why exactly? I checked, and it's the damn *compiler* that inserts a > > "call ___main" just after the stack frame setup in main(): >Try examining the way drivers on ReactOS are built. They have no main >symbol. smss.exe is a native application and has no gcc runtime library >linked with it. It's entry point is NtProcessStartup. That's not the problem. crthybrid.c, in my case, implements the entry point (__PdxLdrEntry, with the same signature as NtProcessStartup), then calls exit() with the return value of main() as parameter, because it's, as the name suggests, a static CRT for Win32-POSIX+ hybrids, that converts/imports the Win32 environment, invocation, standard file descriptors, current directory, etc. and then calls main() The idea is to have something clean and self-contained, and containing exactly what the code says, no more no less, because it's easier to debug The problem is that the C frontend of GCC *always* inserts a call to _main() at the beginning of all functions called main(), without me asking for, or even *wanting* it. I'll just insert a dummy _main() in crthybrid.c until it's fixed, but I *really* hate this |
|
From: Casper H. <ch...@us...> - 2002-05-18 21:05:43
|
l=F8r, 2002-05-18 kl. 21:42 skrev KJK::Hyperion: > At 19.17 18/05/2002, you wrote: > > > testfork.o(.text+0x43):testfork.c: undefined reference to `__main' > > > make: *** [testfork.nostrip.exe] Error 1 > >well, you need your custom __main function then. >=20 > erm... why exactly? I checked, and it's the damn *compiler* that inserts = a=20 > "call ___main" just after the stack frame setup in main(): Try examining the way drivers on ReactOS are built. They have no main symbol. smss.exe is a native application and has no gcc runtime library linked with it. It's entry point is NtProcessStartup. |
|
From: Rick P. <rfm...@sw...> - 2002-05-18 20:51:56
|
KJK::Hyperion wrote:
> Why the hell does it do this? Why does the compiler try to be smarter
> than me? How can I tell the compiler to compile *exactly* what I say,
> and not generate useless/superfluous code? Borland C++ doesn't do it,
> for example:
Just add an "extern int _main() { return 0; };" (or whatever the call
signature is). Would not suprise me if there is a switch to turn this off.
Only happens once per process activation so its not really a
performance issue
-rick
|
|
From: KJK::Hyperion <no...@li...> - 2002-05-18 20:40:11
|
At 19.17 18/05/2002, you wrote:
> > testfork.o(.text+0x43):testfork.c: undefined reference to `__main'
> > make: *** [testfork.nostrip.exe] Error 1
>well, you need your custom __main function then.
erm... why exactly? I checked, and it's the damn *compiler* that inserts a
"call ___main" just after the stack frame setup in main():
.file "testmain.c"
gcc2_compiled.:
___gnu_compiled_c:
.def ___main; .scl 2; .type 32; .endef
.text
.align 4
.globl _main
.def _main; .scl 2; .type 32; .endef
_main:
pushl %ebp
movl %esp,%ebp
subl $8,%esp
call ___main
xorl %eax,%eax
jmp L2
.align 4
L2:
leave
ret
Why the hell does it do this? Why does the compiler try to be smarter than
me? How can I tell the compiler to compile *exactly* what I say, and not
generate useless/superfluous code? Borland C++ doesn't do it, for example:
.386p
ifdef ??version
if ??version GT 500H
.mmx
endif
endif
model flat
ifndef ??version
?debug macro
endm
endif
?debug S "testmain.c"
?debug T "testmain.c"
_TEXT segment dword public use32 'CODE'
_TEXT ends
_DATA segment dword public use32 'DATA'
_DATA ends
_BSS segment dword public use32 'BSS'
_BSS ends
DGROUP group _BSS,_DATA
_TEXT segment dword public use32 'CODE'
_main proc near
?live1@0:
;
; int main(void)
;
push ebp
mov ebp,esp
;
; {
; return (0);
;
@1:
xor eax,eax
;
; }
;
@3:
@2:
pop ebp
ret
_main endp
_TEXT ends
public _main
?debug D "testmain.c" 11442 44081
end
|
|
From: Patrick M. <ox...@st...> - 2002-05-18 17:19:02
|
On Sat, May 18, 2002 at 07:15:11PM +0200, KJK::Hyperion wrote: > At 07.00 15/05/2002, you wrote: > >On Wed, May 15, 2002 at 01:33:11AM +0200, KJK::Hyperion wrote: > >> ... that I forgot to ask: > >> - is there some --do-exactly-what-i-say-and-not-what-you-think-i-need > >> switch? because no matter how many -no this and -fno that I put in the > >> command line, if a program happens to have a procedure called main, a > gcc -I../../../include -nostdinc -fno-builtin -I./ -I../../../../../include > -pipe -march=i386 -c crthybrid.c -o crthybrid.o > gcc -I../../../include -nostdinc -fno-builtin -I./ -I../../../../../include > -pipe -march=i386 -c testfork.c -o testfork.o > gcc -nostartfiles -nostdlib -Wl,--subsystem,console \ > -Wl,--entry,___PdxLdrEntry@4 \ > -o testfork.nostrip.exe \ > crthybrid.o testfork.o ../../../../../dk/w32/lib/ntdll.a > ../../../../../dk/w32/lib/kernel32.a ../../../lib/psxdll/psxdll.a > testfork.o(.text+0x43):testfork.c: undefined reference to `__main' > make: *** [testfork.nostrip.exe] Error 1 well, you need your custom __main function then. usually it is in libgcc.a or crt0.o (dunno for sure and it depends on the version of gcc) and it sets up some stack and calls main(). and it seems like it uses atexit on mingw32 patrick mauritz -- ,------------------------------------------------------------------------. > In the Beginning there was nothing, which exploded - Yeah right... < |------------------------------------------------------------------------| > Moonlight 3D Resurrected | www.moonlight3d.net < `------------------------------------------------------------------------' do what thou whilst shall be the whole of the law love is the law, love under will there is no law beyond do what thou whilst |
|
From: KJK::Hyperion <no...@li...> - 2002-05-18 17:13:43
|
At 07.00 15/05/2002, you wrote:
>On Wed, May 15, 2002 at 01:33:11AM +0200, KJK::Hyperion wrote:
> > ... that I forgot to ask:
> > - is there some --do-exactly-what-i-say-and-not-what-you-think-i-need
> > switch? because no matter how many -no this and -fno that I put in the
> > command line, if a program happens to have a procedure called main, a big,
> > annoying static library is linked to the executable, adding an unnecessary
>doesn't "gcc -nostartfiles" work (probably with -nostdlibs or something
>like that? if not, it seems you have found a bug in the gcc-win32 port as
>that is how it should work...
here's the build log:
gcc -I../../../include -nostdinc -fno-builtin -I./ -I../../../../../include
-pipe -march=i386 -c crthybrid.c -o crthybrid.o
gcc -I../../../include -nostdinc -fno-builtin -I./ -I../../../../../include
-pipe -march=i386 -c testfork.c -o testfork.o
gcc -nostartfiles -Wl,--subsystem,console \
-Wl,--entry,___PdxLdrEntry@4 \
-o testfork.nostrip.exe \
crthybrid.o testfork.o ../../../../../dk/w32/lib/ntdll.a
../../../../../dk/w32/lib/kernel32.a ../../../lib/psxdll/psxdll.a
../../../../../tools/rdel temp.exp
nm --numeric-sort testfork.nostrip.exe > testfork.sym
../../../../../tools/rcopy testfork.nostrip.exe testfork.exe
If testfork.c contains a function named main, testfork.exe is 15.7 KB, and
it imports MSVCRT!atexit. If the function is named, for example, mymain,
testfork.exe is 7.44 KB, and imports only functions I actually use. If I
use -nostdlib, that doesn't stop gcc from trying to slip in its static
library, but the compilation fails:
gcc -I../../../include -nostdinc -fno-builtin -I./ -I../../../../../include
-pipe -march=i386 -c crthybrid.c -o crthybrid.o
gcc -I../../../include -nostdinc -fno-builtin -I./ -I../../../../../include
-pipe -march=i386 -c testfork.c -o testfork.o
gcc -nostartfiles -nostdlib -Wl,--subsystem,console \
-Wl,--entry,___PdxLdrEntry@4 \
-o testfork.nostrip.exe \
crthybrid.o testfork.o ../../../../../dk/w32/lib/ntdll.a
../../../../../dk/w32/lib/kernel32.a ../../../lib/psxdll/psxdll.a
testfork.o(.text+0x43):testfork.c: undefined reference to `__main'
make: *** [testfork.nostrip.exe] Error 1
|
|
From: Robert K. <ro...@ko...> - 2002-05-18 12:53:08
|
> > It is the opposite way around. If the low-level user-mode modules are > shared between subsystem, then there will be less redundancy. E.g. One > winsock stack (with a thin subsystem specific wrapper) vs. x (= > #subsystems) winsock stacks communicating with network protocols using a > TDI (Transport Driver Interface) which is very generic and hard to work > with. One user-mode graphics library for all subsystems. Etc. > This is an argument. Reimplementing a socket lib is not trivial and a windowing system requires a common lib (and window space ). Up to now my plans for allowing PM-os2-apps are to use a win32 server program, which wouldn't be required with user32 as native dll. In that far I'd prefer Casper's suggestion > > _______________________________________________________________ > Hundreds of nodes, one monster rendering program. > Now that's a super model! Visit http://clustering.foundries.sf.net/ > > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel |
|
From: Casper H. <ch...@us...> - 2002-05-18 12:34:39
|
l=F8r, 2002-05-18 kl. 14:19 skrev Robert K.: > I would prefer to use NTdll to implement the OS/2 API. > But maybe I get lazy some day. However I dont like more and even more red= undancy, > that will come with flipping these bits It is the opposite way around. If the low-level user-mode modules are shared between subsystem, then there will be less redundancy. E.g. One winsock stack (with a thin subsystem specific wrapper) vs. x (=3D #subsystems) winsock stacks communicating with network protocols using a TDI (Transport Driver Interface) which is very generic and hard to work with. One user-mode graphics library for all subsystems. Etc. |
|
From: Robert K. <ro...@ko...> - 2002-05-18 12:23:30
|
> > Please read this again: > http://www.reactos.com/rosdocs/tutorials/bk01pt01ch01.html > > The original goal was to clone Windows 95 to run Windows applications. > This was later changed to clone Windows NT because it was superior to > Windows 95. > > What good is Windows NT driver compatibility, if you cannot run Windows > applications? IMO ReactOS should of course implement a win32ss and all necesary services and so on in win32 but I'd like to see a minimal ReactOS system as well. This minimal system should be something like the mach-kernel. An OS-Kernel with a big range of drivers and without a GUI and services. This is a thing for a subsystem / OS -architect. |
|
From: Robert K. <ro...@ko...> - 2002-05-18 12:18:37
|
I would prefer to use NTdll to implement the OS/2 API. But maybe I get lazy some day. However I dont like more and even more redundancy, that will come with flipping these bits Casper Hornstrup schrieb: > fre, 2002-05-17 kl. 18:57 skrev KJK::Hyperion: > > At 14.15 17/05/2002, you wrote: > > > > About Win32: let's leave it to the Wine guys. They've done an impressive > > > > job, and they're undoubtably way ahead of us on this. I'm talking not only > > > > of code, but also experience: the extensive research on undocumented > > > > features and bugs they've done > > >You earlier said that you were not trying to turn ReactOS into a *nix like > > >OS. Well I still get the feeling that you are. > > > > Sorry, but I think you don't get the difference between "ReactOS not having > > Win32" and "ReactOS not needing Win32" > > Maybe I did not explain it correctly before. I said we could turn the > low-level Win32 DLLs into native DLLs so that subsystem programmers had > the *option* of using their services and thus make it easier to > implement new subsystems. I never said that every subsystem should use > these DLLs. They are optional because you can always reimplement the > functionality in kernel32, user32, etc. in your own subsystem libraries > and thus not need these modules. > > _______________________________________________________________ > > Hundreds of nodes, one monster rendering program. > Now thats a super model! Visit http://clustering.foundries.sf.net/ > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel |
|
From: Casper H. <ch...@us...> - 2002-05-18 11:55:47
|
This may be of interrest to some. Remember that this MinGW release is considered a beta release. I have not tried it yet, but I can successfully compile reactos with both GCC 3.0 and GCC 3.2 so there is a good chance it will work with GCC 3.1. Have fun, Casper fre, 2002-05-17 kl. 22:26 skrev Danny Smith: > GCC 3.1 for mingw has been released. > You can download it from: >=20 > https://sourceforge.net/project/showfiles.php?group_id=3D2435 >=20 > Please read the release notes (reproduced below) >=20 > The new features of GCC 3.1 are documented in the GCC release notes at: > http://gcc.gnu.org/gcc-3.1/ >=20 > For mingw-specific modifications, refer to the ChangeLog. >=20 > One major change is that GCC now uses Dwarf2 exception handling=20 > (a table approach) rather than setjump-longjump. >=20 > The __fastcall features that were in later snapshots of GCC-2.95.3 > have also been incorporated. >=20 >=20 > This is a beta. If you want a stable release, use gcc-2.95.3.=20 >=20 > This release contains: >=20 > 1) Source distribution, with mingw-local patches incorporated:=20 > gcc-3_1-20020516-1-src.tar.gz. >=20 > 2) The diff from official FSF sources (also included in full source distr= o.): > gcc-3_1-20020516-1-src.diff.gz. >=20 > 3) Info files in html format: > gcc-3_1-info-html.tar.gz. >=20 > 4) Html version of the libstdc++-v3 documentation: > libstdc++-html-USERS-3.1.tar.gz. >=20 > 5) Binaries for C,C++,ObjC and G77 bundled together: > gcc-3_1-core-20020516-1.tar.gz. >=20 > 6) Binaries for the Gnat Ada compliler: > gcc-3_1-Ada-20020516-1.tar.gz. >=20 > 7) A dummy libmingex.a for those who need it. >=20 > 8) This file. >=20 > Sorry, no Java yet. >=20 > Please don't stop reading yet: >=20 > At the bare minimum you will need > 5) gcc-3_1-core-20020516-1.tar.gz. >=20 > If you don't have the mingw-runtime 2.0 snapshot > and don't intend to download it you will need a dummy=20 > libmingwex in your library path. One is > provided here (7). >=20 >=20 > Highly recommended are: > 3) Documentaion in gcc-3_1-info-html.tar.gz. > and if you work in C+++ > 4) libstdc++-html-USERS-3.1.tar.gz. >=20 > If you want to try out the Ada compiler > grab these binaries:=20 > 6) gcc-3_1-Ada-20020516-1.tar.gz >=20 > Finally, developer types might be interested in the > patch (2) And reading the source (1) is always a good > character building exercise.=20 >=20 >=20 > This package does _not_ contain binutils, the runtime or > the w32api. >=20 >=20 > Okay, before doing anything else make a copy or archive > your current installation of mingw. >=20 > Danny=20 > 2002-05-17 >=20 > http://briefcase.yahoo.com.au - Yahoo! Briefcase > - Save your important files online for easy access! >=20 > _______________________________________________________________ >=20 > Hundreds of nodes, one monster rendering program. > Now that=92s a super model! Visit http://clustering.foundries.sf.net/ > _______________________________________________ > MinGW-users mailing list > Min...@li... >=20 > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users >=20 |
8 messages has been excluded from this view by a project administrator.
