I did a fresh install and set the DJGPP environment variable and I can now
compile hello world with gcc.
To test perl, I just used *perl -de1* which should drop perl into a
debugger prompt, but I get this:
[image: image.png]
*@INC* is the include path where perl looks for its modules, and the
defa
On Sat, Dec 5, 2020 at 10:57 AM Jamie Le Tual
wrote:
> Hey there.
> I tried installing both 1.2 and 1.3rc and managed to get something with a
> command prompt, but GCC.EXE --version dies with a segfault and PERL.EXE
> seems to have been compiled to use a library path which looks like the
> mainta
Hello,
These past few days I was working on a new hobby project. It is called
AMB, and it is a simple hyperlink format that makes it possible to
create "books" that are easy to read even on very limited hardware.
The "books" can be viewed with a tool named AMB. It is only a few
kilobytes big
Hi!
If your GCC segfaults, try without EMM386
(JEMM386, JEMMEX etc.) or try more cautious
options for it. Maybe it has some conflicts
about some memory areas with your BIOS or
hardware. What exactly does PERL say? And
does MEM help you to get further insights?
Cheers, Eric
PS: Which type of dis
Hey there.
I tried installing both 1.2 and 1.3rc and managed to get something with a
command prompt, but GCC.EXE --version dies with a segfault and PERL.EXE
seems to have been compiled to use a library path which looks like the
maintainer's own development environment instead of the layout for Free
I was thinking something along these lines. There could be a "Classic" install
option which installs only the same components offered by MS-DOS, and a
"Modern" option which has the same content, but with significant components
swapped out for their more modern alternatives - e.g. a newer text ed
