So and that everyone is happy on IRC: My answer on the TOP.
Regarding Nr 3. I used the suggestion of HTO from this bug, the ar line and his uploaded "fix" http://www.reactos.org/bugzilla/show_bug.cgi?id=4810
Alex Ionescu wrote:
So in other words, in a month minus 3 days:
- The release engineer has expressed a desire (to do something that
has already been attempted for 7 months and counting)
and
- A couple of developers (Stefan, mainly) have, at least, fixed a
couple dozen warnings (thank you!)
So:
- No Libgcc has been imported into the tree yet (to solve some of the
linker errors) as KJK has suggested he will do
- No additional attempts/efforts (expressing a desire/want does not
count as effort) have been made to recompile Mingw32-gcc-4.4 as Dmitry does.
- Two months after Aleksey promised me that "he will write something
about this", I still don't see any e-mail regarding GCC 4.4 (ie: I was bullshitted to).
I think more effort needs to be put into this, honestly.
Daniel, on the log:
- Could you please separate trunk vs rosapps/rostests errors?
- "In file included from modules\rosapps\applications\net\ncftp\sio\SClose.c:1:
modules\rosapps\applications\net\ncftp\sio/syshdrs.h:36:1: warning: "strncasecmp" redefined" is spamming half the log -- the actual error is only one (and pretty easy to fix, but that's another story), so I suggest you remove the 50 duplicate entries. 3) There used to be errors related to PSEH2 and executable stack -- have those been fixed or...?
Thank you.
Best regards, Alex Ionescu
On Sun, Sep 13, 2009 at 3:21 PM, Daniel Reimer daniel.reimer@stud-mail.uni-wuerzburg.de wrote:
Alex Ionescu wrote:
So? What's the status on this? It's almost been a month.
Best regards, Alex Ionescu
On Wed, Aug 26, 2009 at 6:33 AM, Daniel Reimer daniel.reimer@stud-mail.uni-wuerzburg.de wrote:
Alex Ionescu wrote:
Hi,
On 25-Aug-09, at 12:48 PM, Dmitry Gorbachev wrote:
> Overwriting constant strings is a very real error and should be > fixed. > Code like this would crash in Windows, for example. > > > These warnings do not mean overwriting, simply passing a string constant to a function which takes char *; a potential, not necessarily a real error. It is allowed in C, not in C++.
So they still deserve fixing :)
Of course, it would be good to check all warnings, some can be bugs. Not all useful warnings are included in -Wall. It may be worth to activate more.
But warnings should not deter from adoption of GCC 4.4.
I agree, but switching compilers is a great time to fix some warnings. It would take less then a day to fix the ones present today.
> So as I said, ReactOS need an in-tree version of libgcc with proper > support for __enable_execute_stack for kernel-mode. > > > It is not needed in user-mode, too. Nested functions are only used by PSEH2, and it works well without __enable_execute_stack()
Sure, but that's not the only reason why an in-tree libgcc is a good idea.
Is your GCC 4.4 built on Windows or Linux? If Windows, perhaps it could become part of RosBE -- they have not been able to figure out how to build the compiler, hence my idea to use the MinGW binaries.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Best regards, Alex Ionescu
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Maybe he can just look at our wiki: http://www.reactos.org/wiki/Compiling_GCC_From_Windows and fix it so that it works ;-)
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
- Colin wants to build a GCC with more optimal settings than the
official one when he got some spare time.
- I added a new log three days ago which shows the linking errors too.
- Some devs started to fix warnings and errors we get.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev