29 May
2005
29 May
'05
2:52 p.m.
Casper Hornstrup wrote:
I did not break anything, I merely fixed what was already broken. You
merged a crippled build system which could not build optimizations,
which is something we've done for ages. And I wasted my developer time
to fix that. I've already told you that I cannot boot the DBG = 1 build
either, so it has nothing to do with optimizations.
If anyone has the right to be annoyed, it's the developers, who since
yesterday, have been:
1) Fixing rbuild bugs (unrelated to optimizations)
2) Unable to boot ROS
3) Fixing GCC 4.0 bugs.
I know a minority have these issues, but a minority had GDB bugs too
when I broke it. And I took responsability for that. You can't outright
REMOVE features and then say "well Alex, it's your fault for adding them
back!".
Let's not mention the fact that almost all my release features have been
outright removed from rbuild, as if my work on them didn't even matter.
-----Original Message-----
From: ros-dev-bounces(a)reactos.com [mailto:ros-dev-bounces@reactos.com] On Behalf Of Alex
Ionescu
Sent: 29. maj 2005 01:40
To: ReactOS Development List
Subject: [ros-dev] More RBuild issues...
2) Can't boot ROS, whether or not dbg 1 or 0 is used.
I just built, installed, and booted revision 15650 just fine. I use GCC 3.4.2.
Let me just say that I'm increasingly annoyed by the way you "fix" things.
Revision 15583 both builds (at least with GCC 3.4.2),
installs and boots. Then you enable optimizations in revision 15588 and 15589 even though
I told you that it would cause build
errors. Of course you didn't even try to build or boot ReactOS before you committed
that change so you spend the next 6 commits
(15588, 15589, 15633, 15641, 15642, 15645) (+ filips 15600) making ReactOS build again. I
will accept responsibility for disabling
optimizations, but I WILL NOT accept responsibility for the breakage you've caused by
enabling optimizations.
Casper
Best regards,
Alex Ionescu