Hi,
since some days (weeks?), I get a nice error message during compilation, if I add the '-ftracer' switch:
gcc -c hal\halx86\mp\mpconfig.c -o .\up\obj-i386\hal\halx86\mp\mpconfig.o -Ihal\halx86\include -Intoskrnl\include
-D_DISABLE_TIDENTS -DCONFIG_SMP -D_NTHAL_ -D__USE_W32API -Iinclude -Iinclude\reactos -Iinclude\libs -Iinclude\drivers
-Iinclude\subsys -Iw32api\include -Iw32api\include\ddk -D_M_IX86 -DDBG -Wall -ftracer -Wpointer-arith -g -pipe -Werror
-D_SEH_NO_NATIVE_NLG
hal\halx86\mp\mpconfig.c: In function `HaliScanForMPConfigTable':
hal\halx86\mp\mpconfig.c:552: internal compiler error: in cfg_layout_merge_blocks, at cfgrtl.c:2631
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.mingw.org/bugs.shtml> for instructions.
_make: *** [.\up\obj-i386\hal\halx86\mp\mpconfig.o] Error 1
I can fix the problem
a) if I remove one of the case statements after line #514 in mpconfig.c or
b) if I remove the return statement at line #542 in mpconfig.c.
I'm using gcc 3.4.2 for windows.
Does someone see the same bug?
- Hartmut
Hi,
A lot of people have requested to see try out the new ws2_32.dll binary.
It's not complete yet, and I know the following applications don't work:
- Possibly all cygwin apps that use fork() and sockets
- tracert, and other XP applications which use getnameinfo().
IE6, Filezilla, Thunderbird, Firefox, MIRC, MSN, Outlook Express all
work for me, but I'd be interested in other big applications that have
trouble.
Instructions:
1) Unzip zip file contents to the directory of the program you wish to test
2) Create a blank file in that directory, named program.exe.local,
where program is the name of your app. Example: iexplore.exe.local
Please make sure that you are using Microsoft Windows XP or higher for
your tests.
I'd be happy to receive any news of application crashes or
incompatibilities. I'm most interested in games.
Best regards,
Alex Ionescu
PS. This is a debug build. It prints out a lot of debug messages if you
have a debugger attached and is also built without any optimizations. As
such, network throughput might be slower. This is normal.
hpoussin(a)svn.reactos.com wrote:
> Revert r18628, as we don't have any RTL8139 driver in ReactOS repository
>
>
> Added files:
> trunk/reactos/media/inf/netamd.inf
>
> Updated files:
> trunk/reactos/media/inf/inf.xml
>
> Deleted files:
> trunk/reactos/media/inf/netrtsnt.inf
>
I was able to install successfully the realtek 8138 nic using the
customized "netrtsnt.inf" file provided by hpoussin and to ping
www.reactos.org
The wiki driver page has to be updated accordingly as this is the
new/required method to install this nic with head
Note : Still issue around ipconfig which does not display properly (
Registry setting ? )
Regards
Gge
hpoussin(a)svn.reactos.com wrote:
> Big Plug-and-Play patch for ReactOS:
> - Install drivers for devices at first boot
> - Remove now useless entries in hivesys.inf
> At the moment, driver installation only uses .inf files in ReactOS\Inf directory, and the needed files have to be in ReactOS\Inf or their final location (ReactOS\system32 or ReactOS\system32\drivers) + the user can't provide a custom driver
> Plug-and-Plays devices are only USB controllers (OHCI and UHCI) and serial ports now.
>
>
> Updated files:
> trunk/reactos/bootdata/hivesys.inf
> trunk/reactos/ntoskrnl/io/driver.c
> trunk/reactos/services/umpnpmgr/umpnpmgr.c
>
How the nic driver ( realtek 8139 for example ) can be installed now ?
Upto now , it was installed manually by adding "rtl8139 entries" in the
registry ( hiveinst.inf file) as per wiki driver page.
Regards
Gge
Aleksey Bragin wrote:
> I regret really that Steven don't have time
> right now, since he's best suited to this position (at least by a number
of
> expos he's taken part in :-))
I also wish Steven could find the time to take on this role.
It's unfortunate as this role seemed to be almost written for him.
************************************************************************
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
I'm currently preparing the doc on how to publish ROS.
Since I did this a several times I made a QnD script which I want to
reference in my description. It's quite not a real solution, but better
than nothing on the way until rbuild gets that feature/target.
Where do you think I should check that in?
I think of a subdirectory at reactos/tools
thanks
Hi,
I was just fiddling around with reactos and am interested in getting
some stuff to compile with msvc. (I tried 2003 and 2005 express beta 2)
However, the sln workspace files don't seem to open properly on neither
visual studio. The vcproj do; just wondering whether you guys use other
versions of visual studio?
Jurgen