And now we all get back to a polite discussion about this topic and stop
comparing the lengths of our wieners, ok? I hate the way all this goes
to... last time we came to that point in the past, we lost some long
term devs and put the whole project into a big crisis. So PLEASE, I just
expect a mature talk and no kindergarten from you all. (OK, its a bit
funny that I say something like that :-P )
Ros Arm Devs: I understand that you don't wanna tell us who exactly you
are are, whatever your reasons are and I accept that, but you have to
understand that some here fear harm for the project if ppl noone ever
saw write risky components with the highest possibility to copyright
problems. Almost every kernel dev in here was suspected to write tainted
code at least once in their whole time here. That's the result of some
big crisis we had in the past, we became a bit afraid of great code
outta nowhere which just works. So don't take it personally, plz.
*fearabigdramacoming* Regarding the Devs in the header and the license.
Why not just readd the ppl if some of their code still exists in the
file? Noone would have any harm if there's one more guy in this list.
Lets discuss the relicense after the guys are in the headers again. But,
and this goes out to all ppl, in a kind and mature way.
You all, forget your "He stepped on my tail!!" behavior just for a
moment and think about the project we all code for and we try to get
mature. We can talk about anything, but not in this way.
Thank you very much.
Daniel Reimer
Not soo 1337 ReactOS Dev
"You may relicense my code as BSD" != "You make strip away copyright/ownership of my code".
Revert this.
On 2009-12-31, at 6:51 PM, ros-arm-bringup(a)svn.reactos.org wrote:
>
> - * PROGRAMMERS: Alex Ionescu (alex.ionescu(a)reactos.org)
> + * PROGRAMMERS: ReactOS Portable Systems Group
Best regards,
Alex Ionescu
On Jan 6, 2010, at 2:44 PM, dgorbachev(a)svn.reactos.org wrote:
> - // Always contigiously map low 1Mb of memory
> + // Always contiguously map low 1Mb of memory
Thanks for fixing my typos ;)
Hi,
I'm trying to compile React OS, however I encountered this error when I'm trying to compile:
[HOST-CC] lib/inflib/infcore.c
lib/inflib/infcore.c: In function `InfpAddSection':
lib/inflib/infcore.c:184: warning: implicit declaration of function `__builtin_offsetof'
lib/inflib/infcore.c:184: error: parse error before "INFCACHESECTION"
lib/inflib/infcore.c:184: error: parse error before ']' token
lib/inflib/infcore.c: In function `InfpAddFieldToLine':
lib/inflib/infcore.c:289: error: parse error before "INFCACHEFIELD"
lib/inflib/infcore.c:289: error: parse error before ']' token
make: *** No rule to make target `makefile.auto', needed by `all'. Stop.
Please help me, thanks.
Evans
Get your new Email address!
Grab the Email name you've always wanted before someone else does!
http://mail.promotions.yahoo.com/newdomains/aa/
I <3 this commit.
--
Matthieu Suiche
On Fri, Jan 1, 2010 at 6:31 PM, Alex Ionescu <ionucu(a)videotron.ca> wrote:
> "You may relicense my code as BSD" != "You make strip away
> copyright/ownership of my code".
> Revert this.
> On 2009-12-31, at 6:51 PM, ros-arm-bringup(a)svn.reactos.org wrote:
>
> - * PROGRAMMERS: Alex Ionescu (alex.ionescu(a)reactos.org)
> + * PROGRAMMERS: ReactOS Portable Systems Group
>
> Best regards,
> Alex Ionescu
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
To slow things down. ATM there is a fault created when the mouse moves
with updates, creates and destroying region handles. The kernel fault
occurs inside SEH which should not happen right?
What we need is a semaphore that is used for the whole handle manager.
This is my point over the years about the stability inside win32k. It
running full bore, spinning out of control. Surprised it still works
after turning everything on in my tree.
On Sun, Jan 3, 2010 at 3:26 AM, Timo Kreuzer <timo.kreuzer(a)web.de> wrote:
>
> Why the KeEnterCriticalRegion?
>
> jimtabor(a)svn.reactos.org wrote:
>> - if (pAttr) FreeObjectAttr(pAttr);
>> + if (pAttr)
>> + {
>> + KeEnterCriticalRegion();
>> + FreeObjectAttr(pAttr);
>> + KeLeaveCriticalRegion();
>> + }
>> break;
>>
>
Hi,
As far as I am aware, GCC 4.4.x now works on Linux through RosBE 1.5 (minus some missing patches for 64-bit hosts), and I've gotten it to work on SnowLeopard with some minor hacks -- ie, all that's missing is for Colin, when he has time, to integrate the little fixes for these non-standard hosts.
As for Windows, I think there is a fully working binary GCC 4.4.x/RosBE that builds trunk just fine.
So what's missing for 4.4.x to become official, RosBE 1.5 to RTM, and for the 4.4.x patch from BZ to be committed (The one that gets trunk building)?
Best regards,
Alex Ionescu