[fpc-devel] Re: FPC for Linux-ARM
Hi, My 2 cents. 1) bintutils: I created a number of fink packages with crosscompilers on Mac OS X, including one for arm-linux. When doing so, informations about building crossbinutils would have been very helpful. Although arm-linux seems to be fairly straight forward, please document the configure options for building the cross binutils. 2) Cross compilers on Mac OS X In particular with a working version on linux, it is straight forward for me to setup a fink package (fink works similar to synaptic on linux), which does the whole job of installing a crosscompiler on Mac OS X from the sources of the release version of fpc, i.e. 2.4.2 at the moment, with one command (for example: fink install fpc-cross-arm-linux) or even simpler through a GUI. This includes the dependance on the binutils created from current release sources. Therefore, you can add respective hints/documentation about Mac OS X as host platform on any page about crosscompiling for arm-linux. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Re: fpc 2.5.1. broken for arm-wince
> Hi, > > I get the following error while compiling fpc 2.5.1 for arm-wince: > > c:/lazarus/source/fpcbuild/trunk/fpcsrc/compiler/ppcrossarm.exe > -Twince -Parm -XParm-wince- -Xr -Ur -Xs -O2 -n -S2h > -FuC:/lazarus/source/fpcbuild/trunk/fpcsrc/rtl/units/arm-wince > -Fisrc/wince -Fisrc -Fisrc/win -FDc:\lazarus\source\binutils\arm-wince > -FE. -FUunits/arm-wince -darm -dRELEASE src/eventlog.pp > eventlog.inc(35,37) Error: Identifier not found "OpenEventLog" > eventlog.inc(43,16) Error: Identifier not found "CloseEventLog" > eventlog.inc(66,21) Error: Identifier not found "ReportEvent" > eventlog.inc(149,31) Error: Identifier not found "EVENTLOG_INFORMATION_TYPE" > eventlog.inc(149,31) Error: Illegal expression > eventlog.inc(150,27) Error: Identifier not found "EVENTLOG_WARNING_TYPE" > eventlog.inc(150,27) Error: Illegal expression > eventlog.inc(150,47) Error: Identifier not found "EVENTLOG_ERROR_TYPE" > eventlog.inc(150,47) Error: Illegal expression > eventlog.inc(151,28) Error: Identifier not found "EVENTLOG_AUDIT_SUCCESS" > eventlog.inc(151,28) Error: Illegal expression > eventlog.pp(343) Fatal: There were 11 errors compiling module, stopping > Fatal: Compilation aborted > make.exe[2]: *** [eventlog.ppu] Error 1 > make.exe[2]: Leaving directory > `C:/lazarus/source/fpcbuild/trunk/fpcsrc/packages/fcl-base' > make.exe[1]: *** [fcl-base_all] Error 2 > make.exe[1]: Leaving directory > `C:/lazarus/source/fpcbuild/trunk/fpcsrc/packages' > > Does anybody else get this error? > > Vincent svn from today version 17569 make all CPU_TARGET=arm OS_TARGET=wince on Mac OS X 10.6, starting with fpc-2.4.4 gives the same error. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Re: Problems with building x86_64 on darwin
> Date: Mon, 25 Nov 2013 15:33:08 -0600 > From: Andrew Brunner > Subject: Re: [fpc-devel] Problems with building x86_64 on darwin > Message-ID: <5293c214.9070...@aurawin.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > >> Lazarus cannot yet be compiled for x86-64 on Mac OS X (except if you >> compile it for GTK or Qt, possibly). Unless you are editing files that >> are larger than 1.5GB, it's unlikely you'd notice any difference either. > > Ok. At least I know it's not supported yet. I had a try with 1.0.14 and with the following command, I can obtain a working version of a GTK2 based lazarus. The gtk2 libs are from fink. make all LCL_PLATFORM=gtk2 OPT="-gl -gw -dHasX -Fl/sw/lib/pango-ft219/lib/ -k-framework -kApplicationServices" I did not make extensive test, but a minimal example worked. With a different source for gtk2 libs, you may need some adjustments, for example replace /sw by /usr/local. MiSchi___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] avr-embedded
Hi. I tried to understand where to continue the development of the avr-embedded target, but got stuck. I know that the architecture-specific files are under compiler/avr and rtl/avr (the latter do not seem to be relevant, yet) and someone (fpk?) mentioned strings in the past, but that is basically it. Could someone give my some hints, like more details about the task, corresponding files or solutions for other platforms? Michael aka MiSchi signature.asc Description: Message signed with OpenPGP using GPGMail ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] avr port: avrsim.pp
> Am 12.04.2015 um 12:00 schrieb fpc-devel-requ...@lists.freepascal.org: > > Date: Sun, 12 Apr 2015 10:38:00 +0200 > From: Jeppe Johansen > To: FPC developers' list > Subject: Re: [fpc-devel] avr port: avrsim.pp > Message-ID: <552a2ee8@j-software.dk> > Content-Type: text/plain; charset=windows-1252; format=flowed > > On 04/12/2015 02:11 AM, Georg Hieber wrote: >> A few days ago the file avrsim.pp - startup code for an avr simulator >> appeared. >> >> Has anybody actually run (and debugged) code produced with fpc on an >> avr simulator? If yes, a few hints about how the whole thing is set up >> would be highly appreciated. >> >> Thanks, Georg > It's for an AVR Simulator that I ported a while ago. It has only > exitcode and output registers so it can be used to run the testsuite. > > You can find it here: http://j-software.dk/avrsim.zip > > Might put it on github soon though It does not need lazarus. It builds and runs nicely with „fpc -Mobjfpc avrsim.lpr“ on Mac OS X. signature.asc Description: Message signed with OpenPGP using GPGMail ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
[fpc-devel] tuples
> Date: Sun, 19 Jul 2015 10:33:56 +0200 (CEST) > From: Michael Van Canneyt > To: FPC developers' list > Subject: Re: [fpc-devel] Pascal Standard, and what we can do. > > … snippet … > > You can start e.g. by adding the tuples idea which was discussed on the > mailing list several years ago. > I have 28 years of Pascal experience which is completely at your disposal... > > Michael. Recently, I read about tuples and their use in linda for parallel programming and would like to read some more. So, can you give me a hint to the mailing list? Maybe even the year? Michael S., aka mischi. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
[fpc-devel] fpc iso mode
Hi. With fpc 3.0.0 supporting iso7185 mode I made contact to the people of standard pascal and the p4/p5 compilers and i like to forward their congratulations to you: > It looks good now, the differences are allowed by the standard (precision, > case). > > I'll try to formalize the results and put them up on the > www.standardpascal.org > web site. > > I'll try to compile P5 with it this weekend. If that works out, I'll modify > the configure > script to use fpc as an alternate host compiler. > > I recommend you use an option such as -Miso7185. ISO refers to a lot of > standards, > including other Pascal standards. > > Congratulations on FPC compliance with ISO 7185! Please carry my > congradulations > to all the crew who worked on that. > > Scott Franco With the current status of gpc, fpc has become a much valued alternative, for example for bootstrapping p4/p5. How about his suggestion about renaming the mode to iso7185? Too late? How about calling ExtendedPascal iso10206 instead of extpas? Michael Schindler signature.asc Description: Message signed with OpenPGP using GPGMail ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] fpc iso mode
> Am 04.02.2016 um 02:40 schrieb fpc-devel-requ...@lists.freepascal.org: > > Date: Wed, 3 Feb 2016 20:00:11 +0100 > From: Sven Barth > Subject: Re: [fpc-devel] fpc iso mode > Message-ID: <56b24e3b.4040...@googlemail.com> > >>> It looks good now, the differences are allowed by the standard (precision, >>> case). > > Does anyone know what he means with "precision" and "case"? The output differs from the reference output. Some real numbers may have some more or different, but insignificant digits. Also the case of some letters is different. Michael. signature.asc Description: Message signed with OpenPGP using GPGMail ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] fpc iso mode
> Am 05.02.2016 um 12:00 schrieb mar...@stack.nl (Marco van de Voort): > > Date: Thu, 4 Feb 2016 12:56:14 +0100 (CET) > From: mar...@stack.nl (Marco van de Voort) > Subject: Re: [fpc-devel] fpc iso mode > Message-ID: <20160204115614.2fc8073...@toad.stack.nl> > > Btw, ISO is not in -h, not even in trunk. This sounds like the best solution, iso and extpas are easier to remember and to distinguish, but add the details, iso7185 and iso10206, to the help text. signature.asc Description: Message signed with OpenPGP using GPGMail ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
[fpc-devel] iso 7185 compliance statement
Hi An ISO compiler should make a compliance statement in a defined way. My suggestion would be to extend the output of fpc -i with this statement: Supported ISO modes: The Free Pascal compiler fpc complies with the requirements of level 1 of ISO/IEC 7185. As option to get it individually I suggest -iISO. Before starting to code, I thought to ask for remarks, suggestions. Michael. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 3.0.2 release target
Hi. Could revision 32125 please be merged. Without it mode iso would still be broken. See http://bugs.freepascal.org/view.php?id=28862 Thanks - MiSchi. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] fpc-devel Digest, Vol 156, Issue 16
> Date: Mon, 24 Apr 2017 14:17:46 +0200 > From: Bart > To: fpc-devel > Subject: [fpc-devel] Request for an interim release of the 3.0 branch > Message-ID: > > Content-Type: text/plain; charset=UTF-8 > > Hi, > > The 3.0.2 release has a serious regression: it does not generate > lineinfo, at least on linux i386/x86-64. > > See: http://bugs.freepascal.org/view.php?id=31629 and this discussion > on this ML: > http://lists.freepascal.org/pipermail/fpc-devel/2017-April/037695.html > > The issue makes the 3.0.2 compiler almost useless for development on > the affected platforms. > > The issue is fixed by merging r33007, 33008, 33561 and 34384 (unit exeinfo). > Probably r35886 should be merged as well. > > I would propose to release a 3.0.2a version for the affected platforms > which includes the above revisions (and probably nothing else, since > AFAIK this is the only major regression). > > Personally I have solved it by rebuilding fpc from the 3.0.2 source > with exeinfo patched. > Not everybody is able to do so though, nor should we insist that an > average user (let alone a novice) does so. > > There has been a long time period between the release of 3.0.0 (sep > 2015) and 3.0.2 (feb 2017). > A 3.0.4 release does not seem to be scheduled yet. > > Further more Lazarus also ships with the 3.0.2 release (since the > Lazarus 1.6.4 release). > > Not being able to have proper debugging info might reflect poorly on > both FreePascal and Lazarus and scare away new users, especially if it > would take a long time to release a fix. > > The only alternative would be to advise *nix users to use the 3.0.0 > release instead. > > Bart my two cents: 1) Why not call it 3.0.4? 2) arm-nds and arm gba do not build with 3.0.2: Apply the patches from issue http://bugs.freepascal.org/view.php?id=30405 and http://bugs.freepascal.org/view.php?id=26847 MiSchi ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
[fpc-devel] readme.txt of test suite
Hi, I tried the test suite and found that the readme should be improved. This is what I did: 1) Put the usage paragraph to the top. 2) Add the now required make option TEST_FPC=path_to_your_compiler 3) corrected "make rundigest" to "make digest" 3) several small layout and wording changes This file should replace fpc/tests/readme.txt Usage - To start the test suite execute: make full TEST_FPC=path_to_your_compiler This should run all tests, scan the created log file and output some statistics. make digest TEST_FPC=path_to_your_compiler scans the created log file and outputs some statistics make digest USESQL=YES TEST_FPC=path_to_your_compiler sends the results to an SQL database When the tests are performed, first the units (e.g. rtl) needed by the tests are compiled in a clean determined way and put in the units directory. Then webtbs/webtbf/test/tbs/tbf are searched for t*.pp to be compiled and executed as tests. Directories --- webtbs...Tests for web-bug-database bugs (should compile/run) Digits in filename refer to bug database entry webtbf...Tests for web-bug-database bugs (should not compile/run) Digits in filename refer to bug database entry test.Test suites for different aspects of the compiler/rtl etc tbs..Tests for other bugs, added by the fpc core team (success in compilation) Digits in filename is a serial no tbf..Tests for other bugs, added by the fpc core team (fail compile) Digits in filename is a serial no unitsHelper units for doing the tests utilsUtilities for processing tests packages.Tests for packages: to run these tests, the full fpc sources must be built Writing a test -- A test should have a name on the form t*.pp, to be recognized as a test. It should return 0 on success, any other value indicates failure. Test directives --- At the top of the test source code, some directives can be used to determine how the tests will be processed (if processed automatically via make), e.g. {%CPU=i386}: OPTCompiler option required to compile CPUOnly for these CPU's (i386,m68k,etc). Might be a list. SKIPCPUNot for these CPU's (i386,m68k,etc). Might be a list. TARGET.Only for these OS targets (win32,MacOS,etc). Might be a list. SKIPTARGET.Not for these OS targets (win32,MacOS,etc). Might be a list. VERSIONCompiler with at lest this version number required. MAXVERSION.Compiler with at most this version number required. RESULT.Exit code of execution of test expected TIMEOUTTimeout indication for test in seconds (only used if enabled by defining TEST_TIMEOUT) FILES..List of files (separated by spaces) required by test, will be copied to remote before execution GRAPH..Requires graph unit FAIL...Compilation must fail RECOMPILE..After compiling a test, recompile the test for a second time. This is needed to test ppu loading issues. NORUN..Do not execute test, only compile it INTERACTIVEDo not execute test, as it requires user intervention NOTE...Output note when compiling/executing test NEEDLIBRARYAdds -rpath to the linker for unix. This is needed to test runtime library tests. The library needs the -FE. option to place the .so in the correct directory. KNOWNRUNERROR..Known bug, which manifest itself at runtime. To the right of the equal sign is the expected exit code, followed by an optional note. Will not be logged as a bug. KNOWNCOMPILEERROR..Known bug, which manifest itself at compile time. To the right of the equal sign is the expected exit code from compiler, followed by an optional note. Will not be logged as a bug. NOTE: A list consists of comma separated items, e. g. CPU=i386,m68k,powerpc No space between the elements and the comma. Controling testing in more detail - Calling "make full" will perform tests in a standard manner. To have more control of the test process one must distinguish between: * Driver enviroment: compiler/rtl etc. to be used by the tools which runs and analyze the tests. All normal options to make, like FPC OS_TARGET, OPT etc. controls this. * Test environment: compiler/rtl etc. to be tested, to be used *in* the tests. Ususal options, prepended with TEST_ , controls this. If no such options are given, test and driver environment will be the same. This differentiation also enables cross testing. The following test options can be given: TEST_FP
[fpc-devel] SDL on Mac OS X 10.5 and fpc 2.3.1
Hi all, SDL is used in the program Ultrastar. on macosx 10.5 and fpc 2.3.1 sdl_init leads to a large number of warnings. This is the line with sdl_init: SDL_Init(SDL_INIT_VIDEO or SDL_INIT_TIMER); This is the related part of the output: 2008-05-05 01:17:26.689 UltraStar[22982:807] *** _NSAutoreleaseNoPool(): Object 0x121f0d0 of class NSCFNumber autoreleased with no pool in place - just leaking Stack: (0x9609d12f 0x95fa9ec2 0x9577ede1 0x92059b78 0x920584f9 0x92068736 0x957db1aa 0x957d93b0 0x957d90f5 0x957d8aa4 0x957d85e3 0x957d65df 0x4dbc96 0x4d1d0b 0x4a5f70 0x4a5fa7 0x55977 0x2540 0x1cbc5 0x250b 0x2439) 2008-05-05 01:17:26.691 UltraStar[22982:807] *** _NSAutoreleaseNoPool(): Object 0x121f550 of class NSCFNumber autoreleased with no pool in place - just leaking Stack: (0x9609d12f 0x95fa9ec2 0x9577ee19 0x92059b78 0x920584f9 0x92068736 0x957db1aa 0x957d93b0 0x957d90f5 0x957d8aa4 0x957d85e3 0x957d65df 0x4dbc96 0x4d1d0b 0x4a5f70 0x4a5fa7 0x55977 0x2540 0x1cbc5 0x250b 0x2439) and about 50 more. the program continues. later this line screen := SDL_SetVideoMode(W, H, (Depth+1) * 16, SDL_OPENGL or SDL_RESIZABLE) gives similar output: 2008-05-05 01:17:27.301 UltraStar[22982:807] *** _NSAutoreleaseNoPool(): Object 0x12520c0 of class NSMutableParagraphStyle autoreleased with no pool in place - just leaking Stack: (0x9609d12f 0x95fa9ec2 0x9578cf64 0x92059b78 0x92059a4c 0x920584f9 0x92068996 0x9578ff52 0x9578fa7a 0x9578f4fe 0x4deb2f 0x4dc2ac 0x4d204e 0x51322 0x50dc1 0x55f90 0x2540 0x1cbc5 0x250b 0x2439) 2008-05-05 01:17:27.302 UltraStar[22982:807] *** _NSAutoreleaseNoPool(): Object 0x12525b0 of class NSCFDictionary autoreleased with no pool in place - just leaking Stack: (0x9609d12f 0x95fa9ec2 0x91b98e5c 0x9578cfa8 0x92059b78 0x92059a4c 0x920584f9 0x92068996 0x9578ff52 0x9578fa7a 0x9578f4fe 0x4deb2f 0x4dc2ac 0x4d204e 0x51322 0x50dc1 0x55f90 0x2540 0x1cbc5 0x250b 0x2439) going on until the final crash: 2008-05-05 01:17:27.342 UltraStar[22982:807] *** _NSAutoreleaseNoPool(): Object 0x1256e30 of class NSCFData autoreleased with no pool in place - just leaking Stack: (0x9609d12f 0x95fa9ec2 0x95fbe2a5 0x95fbde81 0x91b9c1e2 0x9205d0fb 0x95874b81 0x95790683 0x9578fb41 0x9578f4fe 0x4deb2f 0x4dc2ac 0x4d204e 0x51322 0x50dc1 0x55f90 0x2540 0x1cbc5 0x250b 0x2439) 2008-05-05 01:17:27.343 UltraStar[22982:807] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Error (1002) creating CGSWindow' 2008-05-05 01:17:27.344 UltraStar[22982:807] Stack: ( 2444870219, 2449854715, 2444869675, 2444869738, 2508676964, 2508671815, 2507736707, 2507733825, 250773, 5106479, 5096108, 5054542, 332578, 331201, 352144, 9536, 117701, 9483, 9273 ) Trace/BPT trap Any help or hints? - Michael Schindler aka mischi. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] replacement for msgdif utility
Hi, When updating the error message file and using the msgdif utility, I remembered that a new utility for working on error message files was mentioned in the mailing list or the irc channel, or so. However, searching and browsing (for example the mailing lists and irc channel logs) did not reveal anything. Any hints? All the best Michael Schindler aka mischi. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Cross compile to linux
If you use fink for the installation of fpc, you can install everything you need with fink install fpc-i386-linux then compiling with -Tlinux should work. this installs also the linux binutils as dependicies. I haven't tested it heavily, so I am interested in feedback. Best wishes - Michael ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Re: FPC + Haiku: how good is it?
Hi, My 2 cents regarding crosscompiling to Haiku: The original binutils from gnu do not support haiku directly. The point is that the Haiku project hosts its own modified version of the binutils, which have not been backported to the gnu source. The Haiku binutils are also not the most recent version. However, the modifications are minor. Using a diff of the Haiku and the original version, I was able to patch the recent version of the binutils. I did this on Mac OS X, but it should serve as a base of a crosscompiler on any other platform. I did not do any further tests, since there was no real feed back, that actually anyone was interested in this and i had some other stuff to do. If anyone is interested in building a crosscompiler, I could still provide the patch file. Michael.___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Re: fcl-web example and new testsuite website
Hi In the buttons the ALL selection (for example in cpu, os or version) selects none. Screenshot of Safari: http://img338.imageshack.us/f/bildschirmfoto20100531u.png/ Mischi. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Re: Purpose of "uses ... in"?
> Marco van de Voort wrote on Mon, 12 Jul 2010: > >> In our previous episode, Hans-Peter Diettrich said: >>> >>> Then we could start by immediately flagging all uses of "in" as >>> deprecated, unless e.g. TP7 or Delphi mode is selected. When the users >>> can demonstrate that they still need such a feature, we could think >>> again about other (more compatible) solutions for not yet covered >>> special cases, before dropping it from the FPC syntax. >> >> See http://www.stack.nl/~marcov/porting.pdf paragraph 7 ("avoid paths...") >> >> I originally wrote that in 2003-2004. >> >> Even for portability purposes it often doesn't work, since usually the build >> systems and files for FPC/Lazarus and Delphi differ anyway (and you noticed >> the working dir difference) > > The working dir difference is a Lazarus difference, not an FPC > difference. Afaict, that feature works identically in FPC and in Delphi. > > Furthermore, at least two of "the users" have already posted in this > thread saying that they use this functionality (both in FPC and in > Delphi). Therefore I don't think it is a good idea to remove or change > it. > > If different functionality is desired, I think it's better to add a > different construct rather than using the same construct but with a > different meaning. When checking, I found that it is used for all files in UltraStar Deluxe. I was not aware that this part of the code is problematic also have no idea about the actual reason. Maybe relates to compiling with Delphi. In any case I would definitely hate to have the code broken. Nevertheless, I will raise the topic. P.S. This will probably end up in the wrong thread, because I answer to the dictionary. At least it did in the past. Any hints? Michael___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Re: Purpose of "uses ... in"?
> Date: Tue, 13 Jul 2010 11:48:27 +0200 (CEST) > From: mar...@stack.nl (Marco van de Voort) > Subject: Re: [fpc-devel] Re: Purpose of "uses ... in"? > To: "FPC developers' list" > Message-ID: <20100713094827.af1ac17...@turtle.stack.nl> > Content-Type: text/plain; charset="US-ASCII" > > In our previous episode, Schindler Karl-Michael said: >>> thread saying that they use this functionality (both in FPC and in >>> Delphi). Therefore I don't think it is a good idea to remove or change >>> it. >>> >>> If different functionality is desired, I think it's better to add a >>> different construct rather than using the same construct but with a >>> different meaning. >> >> When checking, I found that it is used for all files in UltraStar Deluxe. > > With or without paths? IOW does it only change casing? Then it might not be > that bad. (though it doesn't deserve a beauty price either). > > Probably that is because of Kylix, that doesn't have FPC's "in case of > doubt, just lowercase all filenames" escape, resulting in the need to > micromanage it manually using IN. I have no solid idea about why it is used in the first place. Fortunately, only relative paths are given. I have to check, whether it changes casing. If so, it should be easy to fix, in particular since Delphi is used for Windows only, whereas Linux and Mac OS X are fpc. I'll investigate, whether we can actually get rid of it. Thanks for pointing out the issue. MiSchi___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] tests/test/cg/obj/darwin/powerpc/tcext5.o
Hi I tried to do the fpc tests and encountered a bug. The file "tests/ test/cg/obj/darwin/powerpc/tcext5.o" was missing. I created it with gcc -c cext5.c from tests/test/cg/obj/tcext5.c. Then the test run went through. However, I am not sure how cext5.c should be compiled. The notes in /trunk/tests/test/cg/obj/readme.txt also need an update for darwin both processors. Probably an all Jonas task. Best wishes - Michael. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] 2.0.4-rc2 macosx stuff
Hi, The bootstrap compiler and the .info files for fink installation are ready. Can someone please upload them? http://michael-ep3.physik.uni-halle.de/fpc-2.0.4.powerpc- darwin.bootstrap.tar.bz2 should go to: fpc/beta/2.0.4-rc2/source/ http://michael-ep3.physik.uni-halle.de/fpc.info and http://michael-ep3.physik.uni-halle.de/fpc-doc.info I think the .info files should go to fpcbuild/tags/release_2_0_4_rc2/ install/macosx ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] 2.0.4-rc2 macosx stuff
Hi Am 20. Jul 2006 um 22:33 schrieb Tomas Hajny: On 20 Jul 06, at 21:11, Jonas Maebe wrote: On 20 Jul 2006, at 15:18, Schindler Karl-Michael wrote: . . http://michael-ep3.physik.uni-halle.de/fpc.info and http://michael-ep3.physik.uni-halle.de/fpc-doc.info I think the .info files should go to fpcbuild/tags/ release_2_0_4_rc2/install/macosx Tomas, can you this since you are doing all the RC tagging? Right. This is little bit chicken and egg problem, isn't it? If I understand it correctly, you need to have the complete exported sources zipped before you can create these files (otherwise the MD5 checksum cannot be created). However, you want to add that file to the tree afterwards. Once you do it, nobody can re-create your zipped file from the tree again, because the checksum changes and thus the file (or the included checksum at least) becomes invalid... Correct me if I understand it wrongly. Definitely correct. The included checksum of the fpcbuild tarball becomes invalid. Until now, I have no idea about a "clean" solution. The result is a warning dialog after the download with fink, which might lead the uninformed user into downloading the tar ball again and again. To circumvent this, I would submit an updated version to fink. If my assumptions above regarding how it works are correct, my suggestion would be: 1) Add current files to trunk and merge to fixes. I am not sure about trunk. I thought trunk is 2.1.* and this is 2.0.4 only. But you know better. 2) As part of preparation for the next round (depending on whether that becomes RC3 or the final version - I currently expect the former), the files in SVN get updated with new directories and filenames (I'd add this to the release template to make sure this step isn't skipped). The checksum is _not_ updated at that stage (it isn't known anyway). 3) The files get tagged and exported as before (let me know whether you prefer .tar.gz or .zip sources in future builds - we can have both if needed). I would prefer tar.gz, since it is smaller. 4) If needed, the files might get updated with new checksums and committed to SVN (but not to the release branch - only trunk and fixes) by somebody. That sounds ok. The main point is to submit updated versions (paths and names of tar balls and MD5sums) to fink, which I would do after the final 2.0.4 version is ready. Keeping the updated version in the fixes branch would serve for documentation. However, this is their only purpose, since the versions in fpcbuild are not used in any way. Note: Committing of the updated version to SVN in the last step probably isn't strictly necessary (possibly not even useful). Instead of doing that, you might supply a script for update of the checksums instead (and include that script in /fpcbuild/install too), or put this functionality to Makefile. I have a script that supports me when preparing the bootstrap compiler tar ball, which also calculates the MD5sums. I hardly dare to publish that, since it is more like a ToDo list (:-) Basically, putting final version to trunk and fixes should be good enough. Comments, opinions? It would be easier, to keep the .info files somewhere else, outside of fpcbuild. Is this possible/feasable? I do not know, who put them in fpcbuild in the first place and for what reasons. Tomas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] OS X make cycle compilation broken
Am 11. Dez 2006 um 14:13 schrieb Jonas Maebe: On 11 dec 2006, at 13:59, Jonas Maebe wrote: Hard to do with i386-darwin, no ;)? I didn't break the cycle when starting with 2.1.1 :) Besides, this person is using ppc anyway: /usr/local/bin/ppcppc -dNOMOUSE -dFPC_USE_LIBC -Fi../inc -Fi../ powerpc -Fi../unix -Fi../bsd -Fi../bsd/powerpc -Fi../darwin/ powerpc -FE. -FU../../rtl/units/powerpc-darwin -dpowerpc -Us - Sg ../bsd/system.pp Free Pascal Compiler version 2.1.1 [2006/01/20] for powerpc Copyright (c) 1993-2005 by Florian Klaempfl Target OS: Darwin for PowerPC Free Pascal Compiler version 2.1.1 [2006/01/20] for powerpc [2006/01/20] should be a fairly dated version. Probably easier to pick up a snapshot compiler or use fink for the 2.0.4 compiler Michael aka Mischi. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Problem when doing a make -C ide install on macosx
Hi There is no libgdb support for macosx yet. but make or make nodbg produces a usable ide. However, make install issues a $(MAKE) -C ../packages/base/gdbint which fails with libgdb.a not found, using default GDB GDB_V6 /usr/local/bin/ppc386 -Fu../../../rtl/units/i386-darwin -Fl../../../ libgdb/darwin -Fo../../../libgdb/darwin -FE. -FUunits/i386-darwin - di386 -dGDB_V6 gdbint.pp gdbint.pp(191,4) Fatal: User defined: This OS is not yet supported !!! Fatal: Compilation aborted make: *** [gdbint.ppu] Error 1 the above line was added to Makefile.fpc in revission 5504l. Maybe there is a way to pass nogdb and install, but I could not figure it out. Happy coding - Michael ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Linux kernel behaviour change regarding keyboard
Am 19. Jul 2007 um 12:16 schrieb Tomas Hajny: Marco van de Voort wrote: Op Wed, 18 Jul 2007, schreef Michael Van Canneyt: Under the assumption a setuid root program is the only possible option: The safest - and in my opinion only correct - way is to write a small setuid root program which sets the proper TTY stuff, and then executes the IDE as the normal user. The program can easily be audited, as it'll be maybe 50 lines of code... If the user switches VT, the keyboard needs to be unpatched. So this approach won't fully work. However, a solution that can work is to make the keyboard unit execute a setuid root helper to which it communicates through a pipe. This would introduce quite some linux specific code on a lot of already complicated points to the IDE. I'm not so sure - refreshing the keyboard and video status after coming back from a spawned program or shell should be provided as a standard functionality within InitKeyboard and InitVideo calls, shouldn't it? Last time i tried I was not able to get the state the terminal is in, for example white on black or black on white. Consequently, you can only reset it to its default state, when you are done, which might be different from what is was before you started. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.2 online documentation problem
Hi Am 5. Sep 2007 um 09:44 schrieb Graeme Geldenhuys: Hi Looking at the online documentation at: http://www.freepascal.org/docs-html/prog/prog.html The html navigation seems to be broken. I remember a few months back someone also raised such a issue and was under the impression it was fixed. It was me reporting it. However, I did not check or remember, whether it has been fixed since then. Is this a recurring problem or was the original issue never fixed? Let me explain. Using the above website. : Details of the problem explained deleted. 7 Linking issues Michael, I'm not dissing your documentation efforts. :) The content is great. I just think the LaTeX to HTML conversion has some major issues? DocBook HTML navigation seems to be much simpler. Isn't there a LaTeX to DocBook to HTML path we could follow? Or use a different LaTeX to HTML converter? When I tried the make html locally, the result was perfect. So, I do not think there is a general problem and a different tool/way is needed. Regards, - Graeme - Regards - Michael Schindler aka mischi. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.2 online documentation problem
Hi Am 5. Sep 2007 um 10:44 schrieb Michael Van Canneyt: On Wed, 5 Sep 2007, Graeme Geldenhuys wrote: Hi Looking at the online documentation at: http://www.freepascal.org/docs-html/prog/prog.html The html navigation seems to be broken. I remember a few months back someone also raised such a issue and was under the impression it was fixed. Is this a recurring problem or was the original issue never fixed? [cut] No idea. It seems that the tex4ht conversion is not very good after all :/ hm, as I said. When I tried it locally, the result was perfect. Maybe, it is simply a question of the tex4ht version. I am too busy these days, to look further into it, but in about 10 days time, I can have another look at it. Michael, I'm not dissing your documentation efforts. :) The content is great. I just think the LaTeX to HTML conversion has some major issues? DocBook HTML navigation seems to be much simpler. Isn't there a LaTeX to DocBook to HTML path we could follow? Or use a different LaTeX to HTML converter? In the beginning we used latex2html. The problem is that the documentation is simply too big. It takes days to convert (what do you expect from a perl program...) so we switched to tex4ht. Personally, I would drop the HTML support completely and simply provide PDF for the manuals. I must spend far too much time on it. And unless someone takes over the conversion effort, this probably is what will happen. Note that I do not propose to drop HTML support for the unit reference guides; The HTML support of fpdoc is not under question. Michael. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Re: FPC 2.2 HTML docs issues
Hi, As I said, I had some problems to get tex4ht running. After contacting the maintainer he pointed me to a new version of tex4ht, which ran out of the box. However, the new version produced screwed up links. I have to check, whether it is a question of the tex4ht version or my previous suspicion that the result depends on the sequence of make command (make pdf, make ps, make html). All the best - Michael ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Free Pascal 3.0.4
> Am 03.09.2017 um 12:00 schrieb fpc-devel-requ...@lists.freepascal.org: > > Date: Sun, 3 Sep 2017 11:37:27 +0200 > From: Mattias Gaertner > To: fpc-devel@lists.freepascal.org > Subject: Re: [fpc-devel] [Lazarus] Free Pascal 3.0.4-rc1 released! > Message-ID: <20170903113727.27f40...@limapholos.matflo.wg> > Content-Type: text/plain; charset=US-ASCII > > Hi, > > Are there already plans for the final 3.0.4 release? > > Mattias As much as I can see from the commit tags/release_3_0_4, the targets arm-gba and arm-nds are still broken. rtl/gba/rtl.cfg (a simple copy from trunk) is missing and the commits 30017 and 30023 need to be applied for arm-nds (see https://bugs.freepascal.org/view.php?id=32144). MiSchi. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
[fpc-devel] Free Pascal 3.0.4
> Am 04.09.2017 um 12:00 schrieb fpc-devel-requ...@lists.freepascal.org: > > Date: Sun, 3 Sep 2017 14:53:08 +0200 (CEST) > From: mar...@stack.nl (Marco van de Voort) > To: "FPC developers' list" > Subject: Re: [fpc-devel] Free Pascal 3.0.4 > Message-ID: <20170903125308.2918a50...@toad.stack.nl> > Content-Type: text/plain; charset="US-ASCII" > > In our previous episode, Schindler Karl-Michael said: >> As much as I can see from the commit tags/release_3_0_4, the targets arm-gba >> and arm-nds are still broken. rtl/gba/rtl.cfg (a simple copy from trunk) is >> missing and the commits >> 30017 and 30023 need to be applied for arm-nds (see >> https://bugs.freepascal.org/view.php?id=32144). > > Done I hope. Fix confirmed. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
[fpc-devel] Array assignment operator
Hi I would like to use a simple assignment operator for arrays, with which all elements of an array are assigned to the same value, similar to an extended initialize, not to zero but to a value of choice. A simple example for an integer array would be: myArray := 5; With arrays with defined bounds, it works, but i was not able to do it with a dynamic array. My test case is this: program arrayAssign; type TmyArray = array of integer; var myArray: TmyArray; index: integer; operator := (const number: integer) theResult: TmyArray; var i: integer; begin for i := low(theResult) to high(theResult) do theResult[i] := number; end; begin setlength(myArray, 10); writeln ('myArray: ', low(myArray), ', ', high(myArray)); myArray := 5; writeln ('myArray: ', low(myArray), ', ', high(myArray)); for index := low(myArray) to high(myArray) do writeln (index, ': ', myArray[index]); end. The output is: myArray: 0, 9 myArray: 0, -1 The problem is that in the declaration of the operator, the functions low and high seem to return the values of the type TmyArray, i.e. 0 and -1 and not the values of the variable of the assignment statement, i.e. myArray and the assignment nullifies the previous setlength. Is there any way around this and obtain the actual values of myArray? Michael, aka MiSchi. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] Array assignment operator
> Am 04.11.2018 um 12:00 schrieb Ben Grasset : > > From: Ben Grasset > To: FPC-Devel users discussions > Subject: Re: Array assignment operator > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > On Sat, Nov 3, 2018 at 4:44 PM Gennady Agranov > wrote: > >> Hi, >> >> Leaving aside the reason why the MiSchi's solution doesn't work the main >> question is still not answered :) >> >> If you have integer dynamic array "MyArray" is there a way for the >> following statement to compile and work correctly: >> >> MyArray := 5; >> > > Uh, yes? That's what my example showed. In your example the length of the array was set to the number and the elements of the array assigned to their index, whereas my intention is to keep the length of the array and fill all elements to the same number. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC trunk embedded avr build broken
> Am 01.08.2020 um 12:00 schrieb fpc-devel-requ...@lists.freepascal.org: > > Message: 1 > Date: Sat, 1 Aug 2020 02:20:49 +0300 > From: "Dimitrios Chr. Ioannidis" > To: FPC developers' list > Subject: [fpc-devel] FPC trunk embedded avr build broken > Message-ID: > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi, > > I tried unsuccessfully to build today's trunk reg. 45975 for target > embedded avr and I got this internal error : > > "G:/Programming/dimitris/tools/fpc-trunk/bin/x86_64-win64/gmkdir.exe -p > G:/Programming/dimitris/tools/svn/fpc/trunk/rtl/units/avr-embedded > G:/Programming/dimitris/tools/svn/fpc/trunk/compiler/ppcrossavr.exe > -Cpavr5 -Ur -Tembedded -Pavr -XPavr- -Xr -Ur -Xs -O2 -n -Fi../inc > -Fi../avr -FDG:\Programming\dimitris\tools\avr8-gnu-toolchain\bin -FE. > -FUG:/Programming/dimitris/tools/svn/fpc/trunk/rtl/units/avr-embedded > -davr -dRELEASE -g -gw2 -O1 -dDEBUG > -Us -Sg system.pp @system.cfg > sstrings.inc(1089,1) Fatal: Internal error 200309041 > Fatal: Compilation aborted" > > Using fpc trunk on windows 10 64bit with command line : > > G:\Programming\dimitris\tools\svn\fpc\trunk>G:\Programming\dimitris\tools\fpc-trunk\bin\x86_64-win64\make.exe > > clean crossall crossinstall CPU_TARGET=avr OS_TARGET=embedded > SUBARCH=avr5 INSTALL_PREFIX=G:\Programming\dimitris\tools\fpc-trunk > CROSSBINDIR=G:\Programming\dimitris\tools\avr8-gnu-toolchain\bin > CROSSOPT="-g -gw2 -O1 -dDEBUG" BINUTILSPREFIX=avr- > > regards, > > -- > > Dimitrios Chr. Ioannidis Already reported. See: https://bugs.freepascal.org/view.php?id=37421 MiSchi ___ fpc-devel maillist - fpc-devel@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel