<html>
<blockquote>On 2024-02-27 13:08, Marģers . wrote:<br />
>>> Should I be able to compile DOS go32v2 target from DOS itself?<br />
>>><br />
>>> compiling trunk using "make" fall into infinite loop on this<br />
>> command<br />
>>><br />
>>> t:\sv\fpc331\compiler\ppc1.exe -Ur -Xs -O2 -n -Fi../inc -Fi../i386<br />
>>> -FE. -FUt:\sv\fpc331\rtl\units\go32v2 -vx -di386 -dRELEASE -Us -Sg<br />
>>> system.pp<br />
>>><br />
>>> Even thou executing it separately there is no problem.<br />
>><br />
>> Building the compiler under GO32v2 is not guaranteed. It might work<br />
>> if<br />
>> all the prerequisites are fulfilled, but it may not. What's the<br />
>> environment you used (operating system, etc.)?<br />
><br />
> FreeDos on real hardware and DoxBox-x with long filename support.<br />
> For FreeDos you need to clear environment variables to proceed<br />
> set dosdir=<br />
> set cfgfile=<br />
><br />
> I came to found out that booth failed the same way.<br />
> DoxBox-x has problems to delete some temp files. I got impression that<br />
> is known problem and not resolved one.<br />
<br />
I wouldn't spend too much time on DosBox-x, there's simply too much<br />
outside of your control.<br />
<br />
Regarding FreeDos - if it works with individual compilation, but it<br />
fails if running under make, you might:<br />
<br />
1) Make sure that there are no remaining files from previous compilation<br />
attempts (do not rely on "make clean", but really check if there are no<br />
.ppu and/or .o and/or .a files).<br />
<br />
2) Check memory and disk conditions - how much memory is there, how much<br />
free disk space?<br />
<br />
3) Check whether CWSDPMI is used, or whether there is some other DPMI<br />
provider in use (I don't remember if there's something else included in<br />
FreeDos). Note that some DPMI providers ignore the SIGSEGV condition<br />
(unlike CWSDPMI and unlike the DPMI requirements) and that may easily<br />
result in an endless loop if such a condition occurs due to some error.<br />
<br />
4) Increase the verbosity level - I'd try at least "OPT=-vvlx" to see if<br />
you find something interesting (either directly in the output on screen,<br />
or in the generated fpcdebug.txt - however, you need to be prepared for<br />
the fact that fpcdebug.txt may not be complete if you interrupt the<br />
compiler run forcibly).<br />
<br />
5) Disable optimizations ("OPT=O-") and check whether it makes any<br />
difference.</blockquote>
<br />
Thank you for advice<br />
<br />
3) CWSDPMI - from fpc 3.2.2 official release. Should be fine.<br />
4) i used -vxit and redirected output to file.<br />
5) O- optimization failed as well<br />
<br />
i will try little bit more. It juts takes a lot of time testing every possibility.<br />
<br />
Margers<br />
<br />
</html>