Back to home page

DOS ain't dead

Forum index page

Log in | Register

Search:  
Back to the forum
Board view  Mix view

just for testing..new version (Developers)

posted by Rugxulo Homepage, Usono, 18.11.2013, 23:03

> > Computers are a delicate art, and I'm not claiming to be an expert.
>
> Mhh, imagine the difficulty for me ;)
> As you know i've make many attempt before obtain a valid executable from
> DJGPP..
> And the help/FAQ for djgpp seem "tailored" for expert, not for very
> beginners
The FAQ is mostly Eli Z.'s work, probably needs a refresh, but he's busy with other things (like most DJGPP devs).

> I've try to compile under puppy linux with DOSemu + djgpp, but it's a
> P.i.t.a. to configure/install..
> So i've installed djgpp on my DOS only notebbok and on my workplace under
> win XP (no admin privileges).
Part of the problem (besides lack of volunteers) is that there is no preferred environment for DJGPP development. It used to be (by default) XP's NTVDM, but every Windows since has been much worse, and XP is almost (forcibly) obsolete, so there's little hope. I admit DOSEMU isn't perfect, esp. when clashing with SELinux, but it's better than nothing (or even raw DOS sometimes).

> I've download the packege from links download page.In package exist a
> mk-dos
> file for autoconfigure/make with 3 possibity : textual, graphic lite,
> graphic full.
> But on my djgpp don't work : chrashes at end of configure step.So i've
> created the sh script and on my dos only pc work random, on my workplace
> pc work fine (Djgpp love win , ever if is a DOs apps!)
DJGPP definitely doesn't love Windows and vice versa. Sure, DPMI was invented for Windows, but MS didn't keep it up, so it's very very buggy. (Though the same could be said about a lot of similar techs.) But it's true that a lot of DJGPP work was done successfully under XP. Unfortunately, that proved to be a dead end, and not enough focus was put on other environments (esp. rebuilding in pure DOS or DOSEMU or cross-building).

> As explained i don't have found in the net many info regarding swith in
> djgpp work.
> Example -o swith differs from gcc :max number it's -o3 , rather then -o6 in
> gcc
> regarding -march=pemtimpro -tune=generic : i've copy this setting from one
> of others autoconfigure-make files supplied with links package.
-O6 is from the '90s, not sure what (PGCC?). For instance, when Quake was GPL'd (1999?), it used -O6 in its makefile. But GCC hasn't supported anything beyond -O3 in a long time. Quite honestly, even official -O3 isn't really recommended, everyone usually just sticks to "-g -O2".

> > ./configure CPPFLAGS="-I/watt32/inc -L/watt32/lib" LDLIBS="-lwatt"
> > CFLAGS="-g -O2 -mtune=generic" --enable-graphics --without-utf8
> >
> Actually no makefiles are supplied, only mk-dos file for autoconfigure/make
> , but it's a good start!
If it doesn't use AutoTools, that's actually good! But if it just uses some other compile-time generation tools, that's not really much better. It really shouldn't be this hard to recompile something.

> Mikulas have reply to all my question (also the more stupid for a expert),
> unfortunly have a delay on reply time ( i suppose it' s busy for others
> work).
> Have you try to suggest this ideas to Mik?
I don't think he'd be interested, and I'm not much help anyways. But presumably I'd have to at least try rebuilding before wasting his time.

> Finally, i've build this version for test the reply of links on Pentium PC
> (386/486 hare Historical machine, also for dos users).
> So i choose to configure not for a specific Core , but for generic
> processor.
> I hope in the future to find a list of switch explained on web for "best
> optimize".
386/486/586 won't run the .EXE if you use "-march=pentiumpro". Only use -mtune if you are concerned about those older processors. Honestly, I doubt it helps much to use -march at all in most cases. The default value of -mtune differs on different GCC versions (Linux, Cygwin, DJGPP), so it's best to be explicit about what you want (if it really makes a difference, which it may not). DJGPP still uses -mtune=pentium (aka, i586) for unknown reasons. I'm pretty stubborn, but even I'd recommend DJGPP use -mtune=i686 by default (which is what generic used to be an alias for). But again, the speed difference is often very slight, so usually it doesn't matter too much (without profiling or benchmarking to prove otherwise).

Post reply
 

Complete thread:

Back to the forum
Board view  Mix view
22762 Postings in 2122 Threads, 402 registered users (0 online)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum