From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joel Sherrill To: Ian Lance Taylor Cc: gas2@cygnus.com Subject: Re: i386-go32 problem in gas-971208 Date: Thu, 11 Dec 1997 09:00:00 -0000 Message-id: References: <199712111635.LAA27755@subrogation.cygnus.com> X-SW-Source: 1997/msg00049.html On Thu, 11 Dec 1997, Ian Lance Taylor wrote: > > The go32 code was changed around by Robert Hoehne > . Part of that change was to > change the target name used by go32 to i386-pc-msdosdjgpp. This > doesn't work well with the RTEMS configuration triplet of > i386-go32-rtems. Got it. It is compiling OK now. > Actually, a triplet of i386-go32-rtems doesn't make much sense to me, > now that I think about it. I'm not sure what it is supposed to mean. > i386-*-rtems should have a single object file format. If you want to > support a different object file format, you should have a target like > i386-*-rtemself or whatever. RTEMS has a bunch of what I call "normal" configurations and a handful of oddities. It is the oddities I have trouble naming. i386-go32-rtems is based on djgpp v1 (yes old) and uses the go32 dos extender to go into protected mode and kick off the rtems application. It requires slightly different newlib configuration and crt0.o as well as some support libraries from the djgpp distribution. This toolset configuration is subtly different from the vanilla embedded i386-rtems configuration. I really do not know what this one should be named. This ignores the harder rtems configurations like the ports to unix (solaris, linux, and hpux) where you can test rtems applications without a cpu simulator or real hw. :) --joel