[ros-dev] build system problem

Casper Hornstrup chorns at users.sourceforge.net
Sun Oct 3 18:35:55 CEST 2004


 

> -----Original Message-----
> From: ros-dev-bounces at reactos.com 
> [mailto:ros-dev-bounces at reactos.com] On Behalf Of Hartmut Birr
> Sent: 3. oktober 2004 15:02
> To: ReactOS Development List
> Subject: [ros-dev] build system problem
> 
> Hi,
> 
> it exist a variable TARGET_CPPAPP. If this variable is set to 
> yes, the object files for the real target are linked 
> directly. If the variable is not set, the object files are 
> prelinked to a single object file with the option 
> '--strip-debug'. User mode images are always linked with the 
> option '--strip-debug'. TARGET_CPPAPP has no effect. Kernel 
> mode images are not linked with '--strip-debug'. They 
> contains a large debug section if either TARGET_CPPAPP is set 
> to yes or if they are linked to a library which contains 
> debug symbols. Currently, Ntoskrnl contains a large debug section.
> I'm able to boot ros from a harddisk but I'm not able to 
> install ros from a cd. The pc reboots after loading the boot 
> files from the cd. In bochs I see a short debug message:
> 
> Page fault at high IRQL was 31
> KeBugCheckWithTf at ke/catch.c:164  
> 
> Something is different between freeldr and setupldr. This 
> occurs since ntoskrnl uses helper.mk. If I build ntoskrnl 
> with the option '--strip-debug', there exist no problem.
> 
> - Hartmut

I guess this only happens with DBG := 1. Maybe setupldr fails if
ntoskrnl.exe is too large?

There was a linker problem with an C++ application which
TARGET_CPPAPP solved, but I fail to remember which application.
It is possible that we can remove this variable now.

Casper



More information about the Ros-dev mailing list