- Gpc - gnu.de

Using gpc and the Dev-Pas IDE in cygwin
by Brian Keener 03 Nov '06

03 Nov '06

Well the subject sort of says it all. I wonder if this is possible. I tried the Dev-Cpp IDE for C++ in Cygwin and it appears that it works and is smart enought to deal with the Windows path and of the file name and compiler program and still act like it wasd running in a Unix environment but... If I try the same thing in Dev-Pas in Cygwin and gpc when I try to compile the tetris example it seems the it finds windres properly but the file name for input gets jumbled because of windows slashes vs unix slashes: Compile lo tab Building resource file... C:\cygwin\bin\windres -i C:\dev-pascal\examples\tetris\rsrc.rc -o c:\dev-pa~1\examples\tetris\rsrc.o Resource Tab gcc: C:dev-pascalexamplestetrisrsrc.rc: No such file or directory gcc: warning: `-x c' after last input file has no effect gcc: no input files /usr/bin/windres: no resources This is probably OT for this group but I thought maybe since the Chief is involved in both I might sneak through. Any suggestion on this will be greatly appreciated. bk

2 1

SDL and GNU Pascal
by Andreas K. Foerster 01 Nov '06

01 Nov '06

Hello sdl4fp-users, As some of you might remember, I wanted to use the SDL also with GNU Pascal in my project AKFQuiz. I tried to fiddle with the source code of SDL4Freepascal. But there was too much code to change just to find out how it works... So I decided to leave SDL4fp away and implement the few things I need from scratch. My project now is fully functional with GPC and SDL. It is not yet in the released version, but you can check out the CVS as described on the homepage (see link at the end of this mail). Now I want to share my findings with you, so probably you can use it for SDL4Freepascal... First of all, the types for variables are very different. SDL4fp uses "LongInt" for what is "int" in C - because LongInt happens to be 32Bit wide in FPC. But in GPC a LongInt is "at least" :-) 64bit wide! So it doesn't fit. Older versions of GPC intentionally kept the variable types compatible to their counterparts in C. Newer versions broke with that and introduced speacial types, like CInteger or CLongInt. Another difference to FPC is, that in GPC you have a more fine grained access to determine attributes, so you have really control about the size of variables. Here is the code snipplet for the types (from my "qsys.pas"): ----------------------------------------------------------------------- {$IfDef __GPC__} type Uint8 = Cardinal attribute (Size = 8); Uint16 = Cardinal attribute (Size = 16); Sint16 = Integer attribute (Size = 16); Uint32 = Cardinal attribute (Size = 32); Sint32 = Integer attribute (Size = 32); pByte = ^Uint8; {$if __GPC_RELEASE__ < 20041218} type CInteger = Integer; {$EndIf} { __GPC_RELEASE__ } {$Else} { not __GPC__ } type CInteger = LongInt; { @@@ for 32-Bit systems } CString = PChar; Uint8 = byte; Uint16 = word; Sint16 = SmallInt; Uint32 = cardinal; Sint32 = LongInt; pByte = ^Uint8; {$EndIf} { not __GPC__ } ----------------------------------------------------------------------- Note that you have to change "LongInt" to "CInteger" and "PChar" to "CString" in SDL4fp. SDL4fp links to the library by using the name 'SDL' after the "external" modifier. This doesn't work in GPC (yet). In GPC you have to use the compiler directive "{$L SDL}". In FPC there's also a possability to use it in a similar way with "{$LinkLib SDL}"... well it works, but not in every situation. So I decided to keep the name after the external clause, but with "IfDef"s around it. GPC compiles it without the IfDef, but there are lot of warning messages then. In FPC you must use the modifier "cdecl". In GPC that is the default, so you don't need it there. You can however declare it with "attribute(cdecl)", so you can simply write a macro to modify the "cdecl": "{$Define cdecl attribute(cdecl)}". C is case sensitive, while Pascal is not. So in GPC all Pascal identifiers are converted to lowercase at an early stage, this includes the procedure names. So you have a problem when your C identifiers need uppercase letters. This can only be solved by using an attribute which mentions the name again with its capitalisation: "name 'Example'". This name isn't converted to lower case, since it's a string-constant. FPC doesn't need that, but it doesn't harm there either. putting everything together it looks like in this example: procedure SDL_WM_SetCaption(title, icon: CString); cdecl; external {$IfDef FPC}'SDL'{$EndIf} name 'SDL_WM_SetCaption'; Well I still have a problem with CString parameters. FPC needs a type cast, while GPC doesn't accept a type cast here. I "solved" it again with "IfDef"s. Does anybody know a better solution? Please have a look at my source code for more information: http://cvs.sv.nongnu.org/viewcvs/akfquiz/srcbin/?root=akfquiz The relevant units are "sdlgrph.pas" and "sdlsnd.pas". The type definitions are in "qsys.pas". If you use my findings in SDL4fp, it would be nice, if you would mention me there as "AKFoerster". Related Links: GNU Pascal: http://www.gnu-pascal.de/ Free Pascal: http://www.freepascal.org/ SDL: http://www.libsdl.org/ SDL4Freepascal: http://sdl4fp.sourceforge.net/ AKFQuiz: http://akfquiz.nongnu.org/ -- AKFoerster

4 15

Problems after install
by Frank McCormick 30 Oct '06

30 Oct '06

Hello I am back trying my hand at Pascal again after a couple of years absence...and am relatively new to Linux so please bear with me. Just installed GPC with the built-in 3.3.3 GCC...but I can't compile any of the units in the units directory. I am using the commandline "gpc --automake crt.pas" I keep getting errors like this: /usr/lib/crt1.o: In function `_start': (.text+0x18): undefined reference to `main' /tmp/ccOU5D50.o: In function `Textmode': crt.pas:(.text+0x125): undefined reference to `crt_Check_WinChanged' crt.pas:(.text+0x1a3): undefined reference to `crt_SetMonochrome' crt.pas:(.text+0x1b5): undefined reference to `crt_SetScreenSize' crt.pas:(.text+0x1e0): undefined reference to `crt_Window' crt.pas:(.text+0x1e5): undefined reference to `crt_ClrScr' /tmp/ccOU5D50.o: In function `crt_GetScreenSize': crt.pas:(.text+0x201): undefined reference to `crt_Check_WinChanged' //snip// What am I doing wrong ??? Thanks Cheers Frank in Montreal

2 2

Internal compiler error with non-matching method signatures
by Gale Paeper 27 Oct '06

27 Oct '06

While helping someone port a MacPascal Object Pascal program to GPC, an internal compiler error was encountered when an object method heading signature type declaration didn't match the method implementation's heading signature. A distilled down test program that reproduces the internal compiler error: {$mac-objects} program MethodParameterMismatchBug; type UInt8 = Byte; Str255 = record sLength: UInt8; sChars: packed array[1..255] of char; end; xButton = object procedure SetUp (name: Str255); end; procedure xButton.Setup(name: string); {WRONG} begin end; begin end. When you compile it with "gpc -c MethodParameterMismatchBug.pas", you get: MethodParameterMismatchBug.pas:17: internal compiler error: Bus error Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu-pascal.de/todo.html> for instructions. The GPC used for compiling is the Mac OS X GPC that Adriaan is distributing from his web site. The specs are: Reading specs from /Developer/Pascal/gpc345u2/lib/gcc/powerpc-apple-darwin8/3.4.5/specs Configured with: ../gcc-3.4.5/configure --enable-languages=pascal,c --enable-threads=posix --target=powerpc-apple-darwin8 --host=powerpc-apple-darwin8 --build=powerpc-apple-darwin8 --prefix=/Developer/Pascal/gpc345u2 Thread model: posix gpc version 20051116, based on gcc-3.4.5 It is obvious in this test program's small context that the parameter types are different between the declared method heading and the implementation method heading so the compiler should find an error since the two signatures don't match exactly. However, the error shouldn't be an internal compiler error. I'll mention there was a duplication of that parameter type mismatch with another object type's method heading in a larger code context that resulted in an error message something like the compiler was too confused to continue. However, I can't reproduce it with a small test program. Gale Paeper gpaeper(a)empirenet.com

2 1

Reading strings for old Pascal implementations
by Glenn Howes 27 Oct '06

27 Oct '06

if you had a Type like the following: ====================== Type TString12 = String[12]; ======================= and you had some old (PowerPC) code which read one in from a file as in: ====================== Procedure ReadStrings(FromFile:String); Var fToFile:Text; dataToRead: TString12; begin Open(fTextAbout, FromFile); ReadBytes:=ByteRead(fTextAbout, dataToRead,SizeOf (TString12)); ===================== Then how would you read it in using code that will work on both PowerPC and x86 processors? I looked at the data file, and it appears to be mainly text separated by null characters and occasionally null+linefeeds. Thanks. --glenn

1 1

gpc (MinGW) fails to compile
by Frank Kelly 20 Oct '06

20 Oct '06

Hi there, On attempting to compile Pascal code with gpc I get this message: >> gpc -v -c my_alg_boolv2.p Using built-in specs. Configured with: ../configure --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable-languages=pascal --disable-win32-registry --disable-shared --enable-sjlj-exceptions --without-x --enable-interpreter --enable-hash-synchronization Thread model: win32 gpc version 20051116, based on gcc-3.4.4 (mingw special) gpc1 -v -iprefix c:/mingw/bin/mingw32/3.4.4/ my_alg_boolv2.p -quiet -dumpbase my_alg_boolv2.p -famtmpfile=C:\Temp/cckFaaaa.gpa -version -o C:\Temp/ccuabaaa.s gpc: installation problem, cannot exec `gpc1': No such file or directory --------------------------------- I have these installed: gpc 20051116, based on gcc-3.4.4 (mingw special) gcc (GCC) 3.4.4 (mingw special) I had thought that these two were meant to be compatible with each other?!! Have checked and the actual path for gpc1.exe is C:\mingw\libexec\gcc\mingw32\3.4.4 Is there any way to fix this? Thanks in advance. -Frank

3 3

mingw - module/unit `gpc' could not be compiled
by Andreas Wirooks 20 Oct '06

20 Oct '06

Hello, i'm a beginner at MinGW and Pascal and i've downloaded and searched through the archived mailbox fo a long time but i found no solution. And generally i find no useful information for setting up mingw and gpc. I wanted to use the latest gpc snapshop and so downloaded the corresponding mingw files. I used the candidate ones that the MinGW 5.0.2 installation program because these are the only ones wich have gcc 3.4.4 wich is the latest gpc snapshot is based. So the files i installed in C:\MinGW are these: These were downloaded by MinGW 5.0.2 installation program mingw-runtime-3.8.tar.gz w32api-3.5.tar.gz binutils-2.16.91-20050827-1.tar.gz gcc-core-3.4.4-20050522-1.tar.gz gcc-g++-3.4.4-20050522-1.tar.gz gcc-g77-3.4.4-20050522-1.tar.gz gcc-ada-3.4.4-20050522-1.tar.gz gcc-java-3.4.4-20050522-1.tar.gz gcc-objc-3.4.4-20050522-1.tar.gz mingw32-make-3.80.0-3.tar.gz Theses i downloaded from MinGW.org download page in the current section: gdb-5.2.1-1.exe mingw-utils-0.3.tar.gz These from gnu-pascal.de: gpc-20051116.i386-pc-mingw32.tar.gz pdcurs24.beta-i386-pc-mingw32.zip gmp-2.0.2-i386-pc-mingw32.zip rx-1.5-i386-pc-mingw32.zip I found no other MinGW setupinformation than putting C:\MinGW\bin to the path. I already know that with the --automake --autobuild options because without these i got the "module/unit interface `GPC' could not be imported" error. But with one of these options i get the error listed in the subject line. Here is the output for "gpc -v --autobuild statfsdemo.pas -o statfsdemo.exe" wich is a demo program from the doc\gpc\demos directory: C:\MinGW\doc\gpc\demos>gpc -v --autobuild statfsdemo.pas -o statfsdemo.exe Reading specs from C:/MINGW/BIN/../lib/gcc/mingw32/3.4.4/specs Configured with: ../configure --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable-languages=pascal --disable-win32-registry --disable-shared --enable-sjlj-exceptions --without-x --enable-interpreter --enable-hash-synchronization Thread model: win32 gpc version 20051116, based on gcc-3.4.4 (mingw special) C:/MINGW/BIN/../libexec/gcc/mingw32/3.4.4/gpc1.exe -quiet -v -iprefix C:\MINGW\BIN\../lib/gcc/mingw32/3.4.4/ statfsdemo.pas -quiet -dumpbase statfsdemo.pas -auxbase statfsdemo -famtmpfile=C:\WINDOWS\TEMP/ccbxkigb.gpa -fautobuild -version -o C:\WINDOWS\TEMP/ccWldggb.s GNU Pascal version 20051116, based on gcc-3.4.4 (mingw special) (mingw32) compiled by GNU C version 3.4.4 (mingw special). GGC heuristics: --param ggc-min-expand=47 --param ggc-min-heapsize=32543 GNU Pascal Compiler PreProcessor version 20051116, based on gcc-3.4.4 (mingw special) statfsdemo.pas:30: error: module/unit `gpc' could not be compiled I've searched and experienced for ours. I remember, when i tried to learn c years ago (i tried to learn pascal with turbo pascal 6.0 12 years ago), that for emx (yes, the os/2 box is still lying around here) i had to setup many environment variables for the include and library pathes so that i was able to run it. I now compiled gpc.pas by hand and copied all files (.o, .gpi etc.) in the demos directory and it worked doing the commandline above. Can some hacker point me to the solution? I don't think that i have an broken installation. Befor this constellation i used different mingw's with nearly all gpc incarnations from gnu-pascal and mingw but this with this one i came at least to an exe file. Alles Gute and Thanks, Andy _________________________________________________________________ Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden!

4 4

static linking of libgpc
by Peter Norton 18 Oct '06

18 Oct '06

Hello, A few years ago I was managed to create dynamically linked executables with statically linked libgpc (or even only some objects from the lib the program used). Now I have needs to make it again but unfortunately I cann't recall the process :-( The only things I remember - the program was compilled as object first and then linked with ld to executable. I still have system.o and gpc.o in that program's folder and beleive they was involved in process somehow. Could anyone help me with ideas? Thanks in advance, Peter __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 4

Re: indirect jmp
by Nestor Aguilera 17 Oct '06

17 Oct '06

Hi, coming back from my trip, I can now go to Gale's suggestions: > Nestor, could you check the versions of as (the assembler), ld (the > linker), and Xcode and report back? > > The coomand lines for as and ld version checking are: > > as -v Apple Computer, Inc. version cctools-622.3.obj~2, GNU assembler version 1.38 > > (You'll need a control c to get back to the command line) > > ld -v Apple Computer, Inc. version cctools-622.3.obj~2 > For Xcode, from the Xcode menu select About Xcode and you'll get a > info > window with line like: > > Xcode Version: 2.4 > Component versions Xcode IDE: 759.0 Xcode Core: 757.0 ToolSupport: 733.0 > If you could fill in the question mark information, that might help > figure out a things. Hope it helps, and thanks for the concern. Nestor

1 0

Re: [GPC]: daily digest (#942)
by Ken G. Brown 10 Oct '06

10 Oct '06

><> >Date: Sat, 07 Oct 2006 17:59:41 -0700 >From: Gale Paeper <gpaeper(a)empirenet.com> <> ><> > > > In NumberFormatting.p >> > procedure NumToString(theNum: SInt32; var theString: Str255); external name '_NumToString'; > >You're using the wrong set of Mac OS X Pascal Interfaces here. Your >cite is from FPC's FPCPInterfaces Mac OS X Pascal Interfaces. Only >GPC's GPCPInterfaces Mac OS X Pascal Interfaces work correctly for GPC compiling. I was in fact using the correct ones, but had both open in BBEdit and copied the wrong one for the email > > > What do I need to do in this case? >> > >> > > First, when you ask for help you should post a complete example. I agree and I intend to do better next time. >Since this is really a Mac OS X Pascal Interfaces type problem, it would >probably be better to seek help for questions like this on the MacPascal >mailing list instead of this mailing list. You have a much better >chance of getting faster help with Mac OS X interfacing problems and the >reponders will be tailoring their help to a Mac OS X Pascal context. >snip> Ok, shall do. Thx for the help everyone. Got it compiling now and am sorting through the String manipulation issues keeping the GPCStrings as much as possible. Ken >same maximum character capacity as the fake "string" record type has. >The StringXX types are declared in the GPCStrings unit's interface. > >Gale Paeper >gpaeper(a)empirenet.com

1 0