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