Gpc September 1996

gpc@gnu.de

12 participants
49 discussions

dos and binary file IO: fixed
by J.J. van der Heijden 20 Sep '96

20 Sep '96

Hello folks, I fixed the problems of gpc/djgpp with binary file IO. An updated libgpc.a plus the patch can be downloaded from: ftp://agnes.dida.physik.uni-essen.de/home/janjaap/updates/rtsdjgpp.zip The patch also applies for win32 and emx who also treat text and binary files differently, unlike unix. (I have no libgpc.a for them though). Happy hacking, JanJaap --- Someone once asked me if they could use Open Windows on a Mac. I said, "I don't know. Let's find out." I went to the Mac, opened the window and threw out the Mac. "Yep, You can use Open Windows on a Mac." bofh(a)RedDragon.Empire.Net (Psycho Sysadmin)

1 0

Re: how to write binary datas in a file
by Peter Gerwinski 20 Sep '96

20 Sep '96

Hi Sven, hi everybody, > I can use only the "write" function - the result is all $0A will be > converted into "$0D $0A" - Yes, thats the CrLf - Yes, that's even true for "File of Integer"! Congratulations - you have discovered a serious bug in the Run Time Library. :-( > I think it's no problem > under UNIX, Linux, Ponyx, Limbux etc. :-) Yes, it isn't. Your diagnostics was right. > How can I write binary datas in a file? > It must be work in MS-DOS !!! I'd like to fix it as soon as possible, but I am out of time right now. :-( :-( Anybody out there to do it? The error must be in rts/rts-write.c, something with fopen() ... Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

2 1

Re: how to write binary datas in a file
by JanJaap van der Heijden 19 Sep '96

19 Sep '96

At 02:18 PM 9/17/96 +0200, you wrote: >Hi Sven, hi everybody, > >> I can use only the "write" function - the result is all $0A will be >> converted into "$0D $0A" - Yes, thats the CrLf - > >Yes, that's even true for "File of Integer"! Congratulations - you >have discovered a serious bug in the Run Time Library. :-( > >> I think it's no problem >> under UNIX, Linux, Ponyx, Limbux etc. :-) > >Yes, it isn't. Your diagnostics was right. > >> How can I write binary datas in a file? >> It must be work in MS-DOS !!! > >I'd like to fix it as soon as possible, but I am out of time right now. >:-( :-( > >Anybody out there to do it? The error must be in rts/rts-write.c, >something with fopen() ... > I fixed this problem with the MS-DOS files, but it broke some the "standard" files "Input" and "Output". I will think of something more elegant soon. Probably change the BSD style 'fopen()' calls to 'open()' too because then I can easily add an #ifdef MSDOS flags = flags | O_BINARY; #endif once, instead of #iddef-ing every instance of fopen which eats "r" , "w" arguments (which become "wb" etc for non-text files in dos & co.) greetings, JanJaap -- The latest & greates in software, hardware and manswear -- Bono Vox (U2)

1 0

Problems with DJGPP info files
by Peter Gerwinski 19 Sep '96

19 Sep '96

Subject: Re: gnu pascal info problems Newsgroups: comp.os.msdos.djgpp References: <323E879C.3047(a)blackmagic.tait.co.nz> Organization: Universitaet Essen, Germany Reply-To: peter.gerwinski(a)uni-essen.de Distribution: Bill Currie (billc(a)blackmagic.tait.co.nz) wrote: > I'm having problems getting info to browse the info files from gpc 2.7.2. > Info can't 'Top'. I've tried dtou, re-makeing the files with and without > splitting, and dtou-ing again, to no avail (trying before and after > dtou). This is a bug in the GPC info. Thank you for the report. To fix it, you can re-make the info with djgpp's "makeinfo", but you have to edit "gpc.txi" before and replace all "@include foo.texi" by "@include foo.txi". (Fortunately, the other files do not contain "@include" commands. :-) (Also posted to the GPC mailing list.) Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

Which version/location
by John Michael Black 18 Sep '96

18 Sep '96

Okay, we've upgraded to Linux 2.0 with gcc 2.7.2. We can use either ELF or a.out, (although we prefer ELF.) Which version would be best for this configuration? [At one time we had one problem with GPC lookng for "crt0.o". Our configuration doesn't even have this file, but perhaps (as Peter suggested) we had the wrong compiler version.] -john jm_black(a)csunix1.lvc.edu

1 0

Re: how to write binary datas in a file
by J.J. van der Heijden 18 Sep '96

18 Sep '96

On 17 Sep 1996 02:00:00 +0200, Sven Hilscher <Sven(a)rufus.central.de> wrote: > >Hi folks, > >another stupid problem: > >I tryed to write binary datas in a file. >I can use only the "write" function - the result is all $0A will be >converted into "$0D $0A" - Yes, thats the CrLf - I think it's no problem >under UNIX, Linux, Ponyx, Limbux etc. :-) > Yep - a bug. djgpp opens all files in textmode unless instructed otherwise, which the RTS _should_ do for all files not of type TEXT. Unfortunately, a quick fix broke the standard "Input" and "Output" so please wait a few more days 'till I have time to do this the right way. >How can I write binary datas in a file? >It must be work in MS-DOS !!! > Win32 affected too probably. Hey Peter, does OS/2 (EMX) discriminate between text and binary files like DOS, or not, like unix? JanJaap --- Someone once asked me if they could use Open Windows on a Mac. I said, "I don't know. Let's find out." I went to the Mac, opened the window and threw out the Mac. "Yep, You can use Open Windows on a Mac." bofh(a)RedDragon.Empire.Net (Psycho Sysadmin)

1 0

how to write binary datas in a file
by Sven＠rufus.central.de 17 Sep '96

17 Sep '96

Hi folks, another stupid problem: I tryed to write binary datas in a file. I can use only the "write" function - the result is all $0A will be converted into "$0D $0A" - Yes, thats the CrLf - I think it's no problem under UNIX, Linux, Ponyx, Limbux etc. :-) How can I write binary datas in a file? It must be work in MS-DOS !!! ___, ((__ o ,____)) V E N I

1 0

Re: SYSV vs BSD signal blues :-(
by J.J. van der Heijden 12 Sep '96

12 Sep '96

On 11 Sep 96 16:01:47 EDT, Berend de Boer <100120.3121(a)CompuServe.COM> wrote: >> I think I'll just rewrite the signal related stuff in rts-rt0.c, implement >> some BSD/SYSV independant routines that ONLY mask signals that are actually >> present on the target system. > >I don't have handson experience with signals, but it seems to me that POSIX >already did this. I suggest using signals according to the POSIX standard. > >And every unix box should come with some decent posix library these days. > POSIX describes a "minimum set" of signals that must be present in a system. It's the non-POSIX, system specific signals that caused the confusion here. Of course I could just remove all non-POSIX stuff from GPC, but I don't think that's necessary. It also shouldn't be hard to implement a runtime switch to turn signal catching off altogether to enable coredumps, like somebody else suggested. JanJaap --- The latest & greatest in software, hardware and manswear. Bono Vox (U2)

1 0

Re: I don't unterstand __byte__ :-(
by Peter Gerwinski 12 Sep '96

12 Sep '96

Hi all, > const > arHex : array[0..$0f] of char > = '0123456789abcdef'; Nice that this works. I was sure it wouldn't work. ;-) > a8 : array[0..max] of __byte__ Integer absolute a32; > > write(a8[i]: 10); > 1 1 34561 > > write(hexa(a8[i])); > 1 $00000001 $00000001 Symptoms: the value of a __byte__ Integer is written correctly via the "hexa" function, it's wrong when we simply "write" it. This is due to a BUG in GPC's run tims system (RTS) which doesn't (yet) know about type modifiers like __byte__ at all. :-( For the same reason, you get run time errors when you try to writeln __longlong__ (64-bit) Integers (\approx Comp in BP) or __long__ Reals (Extended in BP). To work around, do an explicit type cast: > write ( Integer ( a8 [ i ] ) : 10 ); > 1 1 1 Bye, Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

New win32 binaries almost done. please read.
by J.J. van der Heijden 11 Sep '96

11 Sep '96

Hello, I'm almost done building a cygwin32-beta16 compatible GPC. It fixes a number of problems, like the hanging of GPC1 in "automake" (fork() related problems) Also, the -pipe option is now supported. The current cygwin32 b16 toolchain is a 25Meg ZIP, eating up >80Meg disk when installed. For those who only want to do Pascal, this is a complete waist because you only need binutils and some libraries from it. So, shall I wrap these components in a seperate ZIP (windev.zip or whatever) and upload them too? JanJaap --- The latest & greatest in software, hardware and manswear. Bono Vox (U2)

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

Gpc September 1996