From: Prof A. O. <Afr...@bi...> - 2002-05-09 21:12:32
|
On 9 May 2002 at 14:51, Earnie Boyd wrote: [...] > > But the 386 is a dead hardware platform for Win32. So is there any > > point scheduling or optimising code for the 386? > > > > No, 486 will do. Ok. So, I can now use "-march=i486 -mcpu=i686" ... PS: back to the GPC and "os-hacks.h" matter. The configure script for the GPC runtime system looks for "os-hacks.h". It can live without it, but things will be missing from the runtime library that are necessary for compatibility with certain Pascal standards. There is a version for Linux, and, there is my version for Mingw. It would really be helpful if this header could be supplied as standard with Mingw. It will not affect anything else (of course if people wish to use it in their C programs that is okay) but it will make life much easier for those who wish to build GPC for themselves, as it supplies many things needed for the runtime system. It is only a single header file, and shouldn't cause any disruption. Would you be willing to add it to the standard Mingw release? Thanks. Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.bigfoot.com/~African_Chief email: Afr...@bi... |
From: Prof A. O. <Afr...@bi...> - 2002-05-10 18:29:42
|
On 10 May 2002 at 7:23, Earnie Boyd wrote: [...] > > I presume that you are referring to <prefix>/include/gpc - if so, that > > should be fine. But I will confirm this with the others. Thanks. > > $prefix/include/gpc should be fine with me. It doesn't belong with the > runtime. Ok, how about "$prefix/include/non-ansi", or "$prefix/include/posix"? It seems that either of these is acceptable to others. This could of course become a repository for any additional posix stuff that may be contributed by people. It won't detract from the "minimalist" approach, because it can just be ignored by people who are only interested in ANSI stuff, while providing others who might need some of the posix stuff (without wanting to go to a full posix system like Cygwin) with a facility. Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.bigfoot.com/~African_Chief email: Afr...@bi... |
From: Earnie B. <ear...@ya...> - 2002-05-10 22:02:52
|
--- Prof Abimbola Olowofoyeku <Afr...@bi...> wrote: > On 10 May 2002 at 7:23, Earnie Boyd wrote: > > [...] > > > I presume that you are referring to <prefix>/include/gpc - if so, that > > > should be fine. But I will confirm this with the others. Thanks. > > > > $prefix/include/gpc should be fine with me. It doesn't belong with the > > runtime. > > Ok, how about "$prefix/include/non-ansi", or "$prefix/include/posix"? > It seems that either of these is acceptable to others. This could of > course become a repository for any additional posix stuff that may be > contributed by people. It won't detract from the "minimalist" approach, > because it can just be ignored by people who are only interested in > ANSI stuff, while providing others who might need some of the posix > stuff (without wanting to go to a full posix system like Cygwin) with a > facility. > I like the non-ansi as that can also mean non-posix. Earnie. ===== Earnie Boyd mailto:ear...@ya... --- <http://earniesystems.safeshopper.com> --- --- Cygwin: POSIX on Windows <http://gw32.freeyellow.com/> --- --- Minimalist GNU for Windows <http://www.mingw.org/> --- __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Mother's Day is May 12th! http://shopping.yahoo.com |
From: Prof A. O. <Afr...@bi...> - 2002-05-10 22:41:10
|
On 10 May 2002 at 15:02, Earnie Boyd wrote: [...] > > Ok, how about "$prefix/include/non-ansi", or "$prefix/include/posix"? > > It seems that either of these is acceptable to others. This could of > > course become a repository for any additional posix stuff that may be > > contributed by people. It won't detract from the "minimalist" > > approach, because it can just be ignored by people who are only > > interested in ANSI stuff, while providing others who might need some > > of the posix stuff (without wanting to go to a full posix system like > > Cygwin) with a facility. > > > > I like the non-ansi as that can also mean non-posix. Ok, thanks. Please let me know when you are about to make the next Mingw release, and I will forward to you the latest version of the header. Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.bigfoot.com/~African_Chief email: Afr...@bi... |
From: Earnie B. <ear...@ya...> - 2002-05-13 12:02:54
|
Prof Abimbola Olowofoyeku wrote: > On 10 May 2002 at 15:02, Earnie Boyd wrote: > > [...] > > > Ok, how about "$prefix/include/non-ansi", or "$prefix/include/posix"? > > > It seems that either of these is acceptable to others. This could of > > > course become a repository for any additional posix stuff that may be > > > contributed by people. It won't detract from the "minimalist" > > > approach, because it can just be ignored by people who are only > > > interested in ANSI stuff, while providing others who might need some > > > of the posix stuff (without wanting to go to a full posix system like > > > Cygwin) with a facility. > > > > > > > I like the non-ansi as that can also mean non-posix. > > Ok, thanks. Please let me know when you are about to make the next > Mingw release, and I will forward to you the latest version of the > header. > Ok. But don't expect me to remember. You should forward it to me now. Earnie. |
From: <dan...@ya...> - 2002-05-10 01:46:54
|
--- Prof Abimbola Olowofoyeku <Afr...@bi...> wrote: > On 9 May 2002 at 14:51, Earnie Boyd wrote: > > [...] > > > But the 386 is a dead hardware platform for Win32. So is there any > > > point scheduling or optimising code for the 386? > > > > > > > No, 486 will do. > > Ok. So, I can now use "-march=i486 -mcpu=i686" ... > > PS: back to the GPC and "os-hacks.h" matter. The configure script for > the GPC runtime system looks for "os-hacks.h". It can live without it, > but things will be missing from the runtime library that are necessary > for compatibility with certain Pascal standards. There is a version for > Linux, and, there is my version for Mingw. It would really be helpful > if this header could be supplied as standard with Mingw. It will not > affect anything else (of course if people wish to use it in their C > programs that is okay) but it will make life much easier for those who > wish to build GPC for themselves, as it supplies many things needed for > the runtime system. It is only a single header file, and shouldn't > cause any disruption. Would you be willing to add it to the standard > Mingw release? Thanks. > Could we put it in mingw subdirectory include/gpc and just modify gpc configure script to look there as well? > Best regards, The Chief > -------- > Prof. Abimbola A. Olowofoyeku (The African Chief) > web: http://www.bigfoot.com/~African_Chief > email: Afr...@bi... > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: ban...@so... > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr http://messenger.yahoo.com.au - Yahoo! Messenger - A great way to communicate long-distance for FREE! |
From: Prof A. O. <Afr...@bi...> - 2002-05-10 06:39:07
|
On 10 May 2002 at 11:46, Danny Smith wrote: [os-hacks.h] > Could we put it in mingw subdirectory include/gpc and just modify gpc > configure script to look there as well? I presume that you are referring to <prefix>/include/gpc - if so, that should be fine. But I will confirm this with the others. Thanks. Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.bigfoot.com/~African_Chief email: Afr...@bi... |
From: Earnie B. <ear...@ya...> - 2002-05-10 11:25:44
|
Prof Abimbola Olowofoyeku wrote: > On 10 May 2002 at 11:46, Danny Smith wrote: > > [os-hacks.h] > > Could we put it in mingw subdirectory include/gpc and just modify gpc > > configure script to look there as well? > > I presume that you are referring to <prefix>/include/gpc - if so, that > should be fine. But I will confirm this with the others. Thanks. $prefix/include/gpc should be fine with me. It doesn't belong with the runtime. Earnie. |
From: Prof A. O. <Afr...@bi...> - 2002-05-10 15:15:17
|
On 10 May 2002 at 11:46, Danny Smith wrote: [...] > Could we put it in mingw subdirectory include/gpc and just modify gpc > configure script to look there as well? Apparently, this is not acceptable to the responsible person. And putting it in the system include directory seems unacceptable to Earnie. So I guess I am on my own here. I guess I just have to release the header as a separate download. Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.bigfoot.com/~African_Chief email: Afr...@bi... |