I hadn't noticed that. That's strange though as I'm using 3.4.2.
Not sure whets happened there, I'll rebuild my build environment tonight and
go from there.
Thanks.
-----Original Message-----
From: Ge van Geldorp [mailto:gvg@reactos.com]
Sent: 07 January 2005 09:47
To: 'ReactOS Development List'
Subject: RE: [ros-dev] explorer build failure
> From: Murphy, Ged (Bolton)
>
> E:/reactos/build/MinGW/include/c++/3.2.3/bits/stl_map.h:225:
Wrong gcc/g++ version, you need at least 3.3.1
Gé van Geldorp.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev
************************************************************************
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
Hi all,
I haven't tried building for a while and after installing SVN last night I
thought it a good a time as any.
This was last night so I'm guessing it was build 12857
Upon reaching explorer it tries to generate the depends but is failing as
shown
<--snip-->
cmd: [LD] cmd.exe
cmd.exe was successfully built.
explorer: [DEPENDS] utility/.xmlstorage.d
cc1plus: unrecognized option `-E'
explorer: [DEPENDS] utility/.shellbrowserimpl.d
cc1plus: unrecognized option `-E'
explorer: [DEPENDS] utility/.dragdropimpl.d
cc1plus: unrecognized option `-E'
explorer: [DEPENDS] utility/.window.d
</--snip-->
This then continues for all resulting in massive failure upon building
<--snip-->
E:/reactos/build/MinGW/include/c++/3.2.3/bits/stl_map.h:225: instantiated
from
`_Tp& std::map<_Key, _Tp, _Compare, _Alloc>::operator[](const _Key&) [with
_Key
= String, _Tp = ICON_ID, _Compare = std::less<String>, _Alloc =
std::allocator<
std::pair<const String, ICON_ID> >]'
explorer.cpp:398: instantiated from here
E:/reactos/build/MinGW/include/c++/3.2.3/bits/stl_pair.h:88: invalid use of
undefined type `struct String'
utility/utility.h:737: forward declaration of `struct String'
mingw32-make[1]: *** [explorer.o] Error 1
mingw32-make: *** [explorer] Error 2
E:\reactos\source\trunk\reactos>
</--snip-->
so I manually checked cc1plus with the -E option:
E:\reactos\source\trunk\reactos>cc1plus -E
cc1plus: unrecognized option `-E'
A quick search through the help showed that no -E existed for cc1plus:
E:\reactos\source\trunk\reactos>cc1plus --help | grep -e -E
E:\reactos\source\trunk\reactos>
Does anyone have any ideas what is happening here??
I've attached the full log as it was too big to paste here.
<<exp_fail.txt>>
Thanks,
Gedi
************************************************************************
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
ion(a)svn.reactos.com wrote:
>Remove /nt directory,
>
>
>
I should've placed zw.c in /ex, rather then in ke, since it's a much
more correct place. I'll make the change tomorrow morning (it's 2am).
Best regards,
Alex Ionescu
Hello,
I setup the audio card using the existing registry + snblst.sys +
snblst.dll from NT
The driver intialisation fails as per debug messages below , with a Ros
build from current SVN ?
Any idea/suggestion ?
--------------------------------------------------------------
DriverBase for \SystemRoot\system32\drivers\beep.sys: dcefc000
DriverBase for \SystemRoot\system32\drivers\sndblst.sys: dcf11000
(cm/ntfunc.c:243) NtDeleteKey(KeyHandle 48) called
(cm/ntfunc.c:280) PointerCount 1
(io/resource.c:721) IoReportResourceUsage is unimplemented
(io/resource.c:721) IoReportResourceUsage is unimplemented
---------------------------------------------------------------
Regards
Gerard
Hi,
How hard would it be to add the url pointing to the diff for each commit message? I don't want to
have to subscribe to another mailing list or have to go hunting in websvn if I want to view the
diff of a svn commit.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail - now with 250MB free storage. Learn more.
http://info.mail.yahoo.com/mail_250
After starting up Shell=Explorer and crashing the seemingly
not-enough-(P)SEH-using Explorer (trying to view the RPC Control branch of
the NT Objects namespace is a sure way), I get the following. Disregarding
the crashing Explorer that I only included for completeness, could this be
related to the recent work of having a separate thread doing the shutdown?
(KERNEL32:except/except.c:132) Unhandled exception
(KERNEL32:except/except.c:133) Address:
(KERNEL32:except/except.c:136) 44a912 C:\ReactOS\explorer.exe
CS:EIP 1b:44a912
DS 23 ES 23 FS 3b GS 23
EAX: 00000000 EBX: 000001dc ECX: 007af1fa
EDX: 00000250 EBP: 007ae448 ESI: 007afb1c ESP: 007ae440
EDI: 007afa78 EFLAGS: 00000202
(KERNEL32:except/except.c:139) Frames:
(KERNEL32:except/except.c:147) 421b2c C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 40f5cc C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 4170b4 C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 415871 C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 416c86 C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 44ffb5 C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 77e71ef4 C:\ReactOS\system32\user32.dll
(KERNEL32:except/except.c:147) 77e72833 C:\ReactOS\system32\user32.dll
(KERNEL32:except/except.c:147) 77ea5934 C:\ReactOS\system32\user32.dll
(KERNEL32:except/except.c:147) 77ea7604 C:\ReactOS\system32\user32.dll
(KERNEL32:except/except.c:147) 77ea7839 C:\ReactOS\system32\user32.dll
(KERNEL32:except/except.c:147) 77e71ef4 C:\ReactOS\system32\user32.dll
(KERNEL32:except/except.c:147) 77e72059 C:\ReactOS\system32\user32.dll
(KERNEL32:except/except.c:147) 450459 C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 422e9d C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 450404 C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 77e71ef4 C:\ReactOS\system32\user32.dll
(KERNEL32:except/except.c:147) 77e72152 C:\ReactOS\system32\user32.dll
(KERNEL32:except/except.c:147) 4518b5 C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 40447b C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 404bcd C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 40460c C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 40120d C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 401258 C:\ReactOS\explorer.exe
(KERNEL32:except/except.c:147) 7c8279c1
C:\ReactOS\system32\kernel32.dll
(ntuser/class.c:114) Failed to lookup class atom!
(ntuser/class.c:114) Failed to lookup class atom!
(ntuser/class.c:114) Failed to lookup class atom!
(ntuser/class.c:114) Failed to lookup class atom!
(ntuser/class.c:114) Failed to lookup class atom!
(ntuser/class.c:114) Failed to lookup class atom!
(smss.c:90) SM: NtWaitForMultipleObjects failed!
(ke/error.c:51) Hard error c000021a
(api/wapi.c:175) CSR: NtListenPort() failed
(ke/catch.c:149) Unhandled UserMode exc(api/wapi.c:120) CSR:
NtReplyWaitReceivePort failed
eption, terminating thread
(api/wapi.c:120) CSR: NtReplyWaitReceivePort failed
(api/wapi.c:120) CSR: Nt(api/wapi.c:120) CSR: NtReplyWaitReceivePort failed
ReplyWaitReceivePort failed
ex/power.c:91
--
/Mike
Safedisc installs a kernel service called secdrv.sys. As wine is a
user-space
only implementation of the win32 API, we need to implement part of the
windows kernel API (ntoskrnl.exe) in user-space, and emulate what can't be
implemented.
Our biggest problem is the I/O Manager. The kernel services is started by
StartService, which currently only supports user-space services. We need to
understand how kernel services work in windows to fix that.
When a kernel service is started, it's DriverEntry routine is called with a
DRIVER_OBJECT. In which thread does that happen ? Is a new kernel thread
started for that ? Can DriverEntry block or must it return immediately ? If
it can block, can the driver dispatch routines be called before it
returns ?
When it returns, if it has been started in a new kernel thread, what
happens
to the thread ? In which thread do the dispatch routines run when they are
called from user-space ?
The MSDN documentation is not very clear about all that. I suppose it
hasn't
been written with windows cloners in mind :-)
Devs,
I installed the win32 vim package from vim.org back around
0.2.3-0.2.4, and was quite surprised when the console vim.exe mostly
worked. Recently, while testing PuTTY, I tried the command line tools
(psftp specifically) and they would not accept input. I could ^C out
of it and then all the input I had typed showed up on the command
line. So, I tried the console vim again and it doesn't accept input
also. I checked both vim.exe and the command line putty tools under
0.2.4 and 0.2.5-rc2, and they both work, so it is something after the
0.2.5 branch.
I'm reporting this to the ML because I'm not very familiar with
the console code. Any ideas or pointers would be appreciated.
Andy
--
The cheese stands alone.
> From: hyperion(a)svn.reactos.com
>
> honor __USE_W32API
>
>
> Updated files:
> trunk/reactos/include/tchar.h
I made the same change about half a year ago, but it turns out that it
breaks compilation on Linux.
Gé van Geldorp.
Hi,
Most of the developers I've talked to (including myself) want to get rid
of the /nt directory, since it is architecturally incorrect and should
instead be migrated into other parts of the kernel. Since the nt
functions that were in the directory were part of the Executive (note
the ExXXXObjectType), I've placed the functions in \ex, and renamed all
Ntp stuff by Exp, with the exception of some LPC stuff which I've
renamed from Ni to Lpcp. profiles were harder, since both the Executive
and Kernel parts were in the nt file (actually we're not implementing
the Executive part properly imo, we don't even have EPROFILE, but that's
another story). Anyways, attached is the patch so you can see what was
changed and where it was displaced. I don't think anyone wants to keep
the /nt directory, based on previous discussions, but I want to make
sure people will be aware of it.
Best regards,
Alex Ionescu
Hello,
I got this while compiling svn tree with DBG=1, gcc-3.4.1 :
mingw32-gcc -Wall -Werror -D__USE_W32API -I. -I../../../include
-I../../../w32api/include -pipe -march=i486 -D_M_IX86 -g -c tickcount.c
-o tickcount.o
tickcount.c: In function `parse_print':
tickcount.c:143: warning: implicit declaration of function `_ttoi64'
Thanks, David
I installed the SVN and could make it work, i
downloaded MinGW-3.1.0-1.exe ,gcc-core 3.3.3 , gcc-g++
3.3.3 and nasm-0.98-win32.zip Installed them and set
the path.
i tried to build ReactOs (at the reactos folder) with
make (I did previously a make clean)
And i get the following error:
-----------------------------------------------
...win32k: [DLLTOOL] libwin32k.a
win32csr: [DLLTOOL] libwin32csr.a
notifyhook: [DLLTOOL] libnotifyhook.a
regtests: [DLLTOOL] libregtests.a
=====================================================
Compiling deptool
=====================================================
Compiling bin2c
Tools are up to date.
Tools are up to date.
=====================================================
Assembling dosmbr
=====================================================
Assembling fat
=====================================================
Assembling fat32
=====================================================
Assembling isoboot
=====================================================
Assembling ext2
=====================================================
Assembling arch/i386/fathe
lp
=====================================================
Assembling arch/i386/arch
=====================================================
Assembling arch/i386/i386i
dt
=====================================================
Assembling arch/i386/i386t
rap
=====================================================
Assembling arch/i386/i386c
pu
=====================================================
Assembling arch/i386/i386p
np
=====================================================
Assembling arch/i386/boot
=====================================================
Assembling arch/i386/linux
=====================================================
Assembling arch/i386/mb
=====================================================
Compiling arch/i386/i386rt
l
cc1.exe: unrecognized option
`-fno-zero-initialized-in-bss'
make[2]: *** [arch/i386/i386rtl.o] Error 1
make[1]: *** [all] Error 2
make: *** [freeldr] Error 2
C:\Internet\ReactOS\Subersion\trunk\reactos>
------------------------------------------------
Nevertheless i try to make install and get the
following error:
---------------------------------------
expat: [OBJDUMP] expat.map
expat: [LD] expat.dll
expat.dll was successfully built.
expat: [INSTALL] expat.dll to system32/expat.dll
fmifs: [DEPENDS] .media.d
fmifs: [DEPENDS] .label.d
fmifs: [DEPENDS] .init.d
fmifs: [DEPENDS] .format.d
fmifs: [DEPENDS] .extend.d
fmifs: [DEPENDS] .diskcopy.d
fmifs: [DEPENDS] .compress.d
fmifs: [DEPENDS] .chkdsk.d
fmifs: [RC] fmifs.rc
fmifs: [CC] chkdsk.c
fmifs: [CC] compress.c
fmifs: [CC] diskcopy.c
fmifs: [CC] extend.c
fmifs: [CC] format.c
fmifs: [CC] init.c
fmifs: [CC] label.c
fmifs: [CC] media.c
fmifs: [AR] fmifs.a
make[1]: *** No rule to make target
`../../dk/w32/lib/libvfatlib.a', needed by `
fmifs.nostrip.dll'. Stop.
make: *** [fmifs_install] Error 2
C:\Internet\ReactOS\Subersion\trunk\reactos>
---------------------------------------------------
I dont know what i am making wrong, any idea?
Thanks in advance and my best wishes for 2005.
______________________________________________
Renovamos el Correo Yahoo!: ¡250 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
The attached patch fixes "warnings + -Werror = not compile" for
rosapps/tests/tokentest/tokentest.c
tokentest.c: In function `CreateInitialSystemToken':
tokentest.c:359: warning: braces around scalar initializer
tokentest.c:359: warning: (near initialization for `authId.LowPart')
tokentest.c:359: warning: excess elements in scalar initializer
tokentest.c:359: warning: (near initialization for `authId.LowPart')
I think SYSTEM_LUID and similar macros for initial values are intended
as initializers of LUID variables, not LARGE_INTEGER ones.
I've posted this (and not commited it myself) because I can be missing
something important. Is there other issue with LUID <-> LARGE_INTEGER ?
<#secure method=pgpmime mode=sign>
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
Alex Ionescu wrote:
> >
> > Well, yes, win32. I've been setup before, but I haven't
> > kept up with the tool chain.
> >
> > Do we still need the djcc stuff for building freeloader?
> >
> > What would be really cool was an MSI that would get me
> > a complete 'ReactoOS' build environment in one simple
> > step. Maybe I'll look into it.
>
> I'm currently working on this exact project!
I'm a newbie. I'm looking for it. Can you tell me something about it?? Thanks.
yang
___________________
Come from China
ion(a)svn.reactos.com wrote:
> + DPRINT("Waiting on Critical Section: %x\n", CriticalSection);
> + if (CriticalSection->DebugInfo) CriticalSection->DebugInfo->EntryCount++;
I'm just reading the diffs here, so I could be way
off, but shouldn't this use an InterlockedIncrement...
otherwise you could get a context switch between
in the middle of your increment to another threading
attempting to lock the critical section. It is just
debug information, but still...
Also, looking at the rest of the code, I notice that
spin count doesn't appear to be implemented.
I don't have a build environment even setup, so
take the attached patch with a grain of salt.
The changes in RtlpCreateCriticalSEctionSem()
are because the InterlockCompareExchangePointer()
should already have written the new event into
the data structure.
Maybe on day I'll manage to get my build environment
setup again.
- Joseph
Index: C:/Users/galb/ReactOS/reactos/lib/ntdll/rtl/critical.c
===================================================================
--- C:/Users/galb/ReactOS/reactos/lib/ntdll/rtl/critical.c (revision 12774)
+++ C:/Users/galb/ReactOS/reactos/lib/ntdll/rtl/critical.c (working copy)
@@ -133,7 +133,17 @@
{
HANDLE Thread = (HANDLE)NtCurrentTeb()->Cid.UniqueThread;
- /* Try to Lock it */
+ /* Try for SpinCount times to Lock it */
+ for(LONG i = 0; i < CriticalSection->SpinCount; i++)
+ {
+ if ( RtlTryEnterCriticalSection(CriticalSection) )
+ return STATUS_SUCCESS;
+ }
+
+ /*
+ * Still didn't get it; we have to bump the LockCount, which
+ * might get it for us, and then wait
+ */
if (InterlockedIncrement(&CriticalSection->LockCount)) {
/*
@@ -398,12 +408,12 @@
/* Increase the Debug Entry count */
DPRINT("Waiting on Critical Section: %x\n", CriticalSection);
- if (CriticalSection->DebugInfo)
CriticalSection->DebugInfo->EntryCount++;
+ if (CriticalSection->DebugInfo)
InterlockedIncrement(&CriticalSection->DebugInfo->EntryCount);
for (;;) {
/* Increase the number of times we've had contention */
- if (CriticalSection->DebugInfo)
CriticalSection->DebugInfo->ContentionCount++;
+ if (CriticalSection->DebugInfo)
InterlockedIncrement(&CriticalSection->DebugInfo->ContentionCount);
/* Wait on the Event */
DPRINT("Waiting on Event: %x\n", CriticalSection->LockSemaphore);
@@ -523,21 +533,14 @@
return;
}
- if (!(hEvent =
InterlockedCompareExchangePointer((PVOID*)&CriticalSection->LockSemaphore,
- (PVOID)hNewEvent,
- 0))) {
-
- /* We created a new event succesffuly */
- hEvent = hNewEvent;
- } else {
-
- /* Some just created an event */
- DPRINT("Closing already created event!\n");
- NtClose(hNewEvent);
+
+ if (
InterlockedCompareExchangePointer((PVOID*)&CriticalSection->LockSemaphore,
+ (PVOID)hNewEvent,
+ 0)) != 0) {
+ /* Someone else just created the event */
+ NtClose(hNewEvent);
}
-
- /* Set either the new or the old */
- CriticalSection->LockSemaphore = hEvent;
+
DPRINT("Event set!\n");
}
Hi,
Attached is a patch with uses the proper PSID/PISID types. Also, I've
noticed that we currently have duplicated code between /lib/rtl and
/ntoskrnl/se. The removals are also in this patch. Is it OK to remove
them, or is there some reason they must be duplicated?
Best regards,
Alex Ionescu
Hi
I am a new comer.
I began to read codes a few days ago, now I installed reactos 0.2.4 in vmware, but it can't do any thing even if I want to copy a file(both command line and GUI), when I do this in GUI, it show me a blue face or do nothing. what do you make up your reactos develop system? It means read, edit, and compile code in reactos. I was on win 32, which emulater is better to run reactos on it? any idea would be appreciated.
Hi,
I've add the following line to my test driver:
extern __attribute__((dllimport)) POBJECT_TYPE* ExEventObjectType;
DbgPrint("%x %x %x %x\n",
ExEventObjectType,
*(PULONG)ExEventObjectType,
MmGetSystemRoutineAddress(&NameU),
*(PULONG)MmGetSystemRoutineAddress(&NameU));
Running on W2K, I get this result:
GCC: 81ebd540 81ebd440 8047a888 81ebd540
MSVC: 8047a888 81ebd540 8047a888 81ebd540
Running on ROS:
GCC: c0692ef8 54545645 c00e0760 c0692ef8
MSVC: c00e0760 c0692ef8 c00e0760 c0692ef8
It seems that GCC and MSVC does handle imported data symbols different.
In MSVC is an imported data symbol a pointer to the variable and in GCC
the value of the variable.
- Hartmut
royce(a)svn.reactos.com wrote:
>don't pass vector<pointer> by value unless you are looking for trouble, also fixed Assert() to take stdargs to make it's usage simpler and less error-prone. Also fixed IsTrue(), etc, to take file and line info by args and created macros to pass that info automatically.
>
>
>
Casper, I made some changes to Assert() and the code that calls it, in
the hope that this is what you really wanted. I apologize sincerely if
you had wanted to do something else with message[], but if you do, I
think it would be easier to do so from within Assert(). I will revert
that part of this patch if you needed the buffer in Assert()'s callers.
> Fix incorrect LPC Object export...we export pointers not the object itself!
Why?
Aren't DATA symbols exported by DLLs pointers?
Emanuele
____________________________________________________________
Libero ADSL: 3 mesi gratis e navighi a 1.2 Mega. E poi hai l'Adsl senza limiti a meno di 1 euro al giorno.
Abbonati subito senza costi di attivazione su http://www.libero.it
Hi,
if you want to replace the Makefile build system, please consider using bjam:
http://boost.org/tools/build/jam_src/
It has the following advantages:
- automatic dependency checking
- resolves dependencies in memory without invoking
multiple levels of Makefiles
- supports nearly every compiler toolset out there, see:
http://boost.org/more/getting_started.html#Tools
On 02.01.2005 23:17:03 chorns(a)svn.reactos.com wrote:
> Add sample build script.
> Added files:
> branches/xmlbuildsystem/reactos/ReactOS.xml
ion(a)svn.reactos.com wrote:
> Fix my previous patch and fix ACCESS_TOKEN being declared as a structure. This is incompatible with DDK/W32API because ACCESS_TOKEN is a PVOID. The real structure is TOKEN. Also, structure has been updated.
>
I think Microsoft declared PACCESS_TOKEN as a void pointer in order to
hide the internals of ACCESS_TOKEN because the average developer does
not need to access it or they don't want to reveal more information than
needed.
Please don't break what's working and revert this patch!
We are using our own set of headers because we need to fix crippled
declarations and add missing ones. If you want to build ReactOS using
the MS SDK and DDK fix them instead of breaking our headers and code.
Regards,
Eric