This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Wed, 2006-02-22 at 22:19 +0200, Kai Ruottu wrote: > David Fernandez kirjoitti: > > Hi there, > > > > I'm trying to build a cross-compiler from Linux to msdos, I'm trying > > the i686-pc-msdosdjgpp target. > > > > After some problems I've discovered that, among other things, the used > > to apply some patches to the gcc sources, but that was 3.x.x; I'm now > > using 4.0.2, and seems that there is no patches file in DJGPP site for > > that. > > > A look into the 'ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/' told > that gcc-4.0.1 was there... Not so > much difference between two "bug-fix" releases so the DJGPP2 changes in > gcc-4.0.1 SHOULD be > easily movable to the gcc-4.0.2 sources too. In your case the patches > for the DJGPP2-target could be > enough unless your goal is to produce GCCs for the DJGPP2-host ! Then > there can be patches which > are for the DJGPP2-build system :-( Not installing anything which > could break the Linux-host/build > scheme would be important.... > > Generally I don't understand the current DJGPP2 idea... Since 1995 > there has been that Win32 host > with its "console", so a DOS/DJGPP2-hosted "native GCC" is a dinosaur. > It should have been replaced > with a Win32 hosted cross-GCC for the DJGPP2 target. The MinGW host > could have been suitable. > Then there could have been a GUI-based debugger for those DOS/DJGPP2 > apps running in the Win32 > "DOS subsystem" or whatever the environment is where those DOS apps will > run... The DJGPP2 > target being changed to be "only target", a'la those embedded targets > ("DOS is not an opsys and can > therefore not have any native GCC..."), could have bettered the > situation.... Actually, I don;t understand the situation too. All that I was trying to achieve is a cross-compiler built and hosted in Linux to produce msdos applications for the NATIVE MS-DOS (not the dos box in windows, which is just like the shell window in linux). That's what I thought the msdosdjgpp was for. What I don't understand is why the patches and all haven't been included in the configure/make scripts under the target ix86-pc-msdosdjgpp?. Anyway, I'll look again for the file in djgpp site... But, as you said, I wouldn't like to change anything in the gcc sources that could break the rest of the gcc matrix. > > Neither MinGW is the best available "Unix" for builds, so producing a > new cross-GCC for DJGPP2 > target and MinGW host would have happened on Linux after configuring like : > > --build=i686-linux-gnu --host=i686-mingw32 --target=i686-djgpp2.0.3 > > At least I would have appreciated this being the default... It has > taken almost 4 years since I last made > a djgpp2.0.3 targeted GCC for the Win32 (MinGW) host : > > E:\usr\local\bin>gcc-djgpp2-31 -v > Reading specs from e:\usr\local\lib\gcc-lib\i386-djgpp2.03\3.1\specs > Thread model: single > gcc version 3.1 20020506 (prerelease) > > Probably on Linux host I have something much newer but never duplicated > that for the Win32 host.... > > Could you tell "in a nutshell" what is the sanity in the > DOS-hosted/DOS-targeted GCC nowadays? > Why not a Win32-hosted/DOS-targeted GCC instead? > Actually, very little (The more dos attached people here have move into some kind of win32 host machines, so you're right). But, as mentioned above, what I intent is just what you said you have much newer stuff. > In those days when I produced some tens of DJGPP2-hosted (for the > DOS-box in Win3.1x/Win32s) > text-mode tools and their Win3.1x/Win32s-hosted GUI-mode companies > (Insight-debuggers for instance), > none of those text-mode apps was in any way "similar to" the distributed > native-GCC for DJGPP2 ! > It really was much, much easier to not care about its peculiarities and > then produce tens of toolchains > which "only worked on DOS and produced code for something, including DOS > itself", just as their > equivalents did on Linux and Win32 hosts.... Ok, those DJGPP2-hosted > tools were only "toys", in the > late 90's nobody any more thought DOS/Win3.1x being in any way sane > development environment > for anything... It only was fun to see GCCs and Insights running on a > 386/40 PC with 8 MB memory > and DOS/WfW3.11/Win32s as its opsys... > > But what I never succeeded to do, was a Win32-hosted Insight/GDB for > the DOS/DJGPP2 target, > ie. one which could have loaded a DJGPP2 application and then run it in > that "DOS subsystem", in the > "DOS-box" or something. Some DOS/Windoze-expert could have told how > that could work... Of > course I succeeded to produce something... A JPG-picture from that is > attached to tell what I'm > talking about... > > ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.org
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |