Re: [fpc-devel] negative TDateTime values and MinDateTime
On 08/03/2011 06:55 AM, LacaK wrote: Jonas Maebe wrote / napísal(a): On 02 Aug 2011, at 13:45, LacaK wrote: What do you think, can we change MinDateTime from -693593.0 to -693594.0; (to accept 01/01/0001 23:59:59.999) Negative dates are problematic as Year 0 officially does not exist. the first day of Year 1 is directly preceded by the last day of year 1 BC. Many years ago I wrote a set of date handling functions for Jedi. Those became obsolete when a newer Delphi VCL version included a much improved set of date function. Maybe some of my old stuff (e.g. handling of negative dates) might still be of some interest. -Michael ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
Hello, today I branched branches/fixes_2_6, the basis for a new fixes branch that will become 2.6.0 eventually. After branching I updated the trunk version to 2.7.1, which might need your build and package scripts to be adapted, as well as the symlinks of ppc386 on *nix. Before branching all makefiles were regenerated, so an update will be big. Marco ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
In our previous episode, Michael Schnell said: Before branching all makefiles were regenerated, so an update will be big. OK, But why does svn show many Makefiles as conflicting instead of just updating them ? Most likely because you have local modifications to those files, from own running of fpcmake. My checkouts on various (windows and *nix) machines updated flawlessly ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
On 08/03/2011 05:55 PM, Marco van de Voort wrote: Most likely because you have local modifications to those files, from own running of fpcmake. I never intentionally made modifications or used dpcmake. Nonetheless I often get one or two conflicts. I suppose I should delete everything and restore from the server. Or is the another option to have svn get the current version of everything ? -Michael ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
On 03 Aug 2011, at 18:03, Michael Schnell wrote: Or is the another option to have svn get the current version of everything ? Execute the following command in the top-level checkout directory: svn revert -R . Jonas___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] negative TDateTime values and MinDateTime
Michael Schnell schrieb: On 08/03/2011 06:55 AM, LacaK wrote: Jonas Maebe wrote / napísal(a): On 02 Aug 2011, at 13:45, LacaK wrote: What do you think, can we change MinDateTime from -693593.0 to -693594.0; (to accept 01/01/0001 23:59:59.999) Negative dates are problematic as Year 0 officially does not exist. the first day of Year 1 is directly preceded by the last day of year 1 BC. There exist other calendars than only the Gregorian one, with their own oddities (Maya!), and all of them should be based on an common internal date/time type. IMO a MinDateTime value should be private to every calendar, if ever needed, and the global constant should be removed. DoDi ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
On Wed, Aug 3, 2011 at 11:55 AM, Marco van de Voort mar...@stack.nl wrote: Hello, today I branched branches/fixes_2_6, the basis for a new fixes branch that will become 2.6.0 eventually. After branching I updated the trunk version to 2.7.1, which might need your build and package scripts to be adapted, as well as the symlinks of ppc386 on *nix. Before branching all makefiles were regenerated, so an update will be big. Hi Marco, I got the new sources and tried to compile on WinXP: ERROR -- W:/md/dev/freepascal/compiler/2.6.0/compiler/ppc386.exe -Ur -Xs -O2 -n -S2h -FuW :/md/dev/freepascal/compiler/2.6.0/rtl/units/i386-win32 -FuW:/md/dev/freepascal/ compiler/2.6.0/packages/fcl-base/units/i386-win32 -FuW:/md/dev/freepascal/compil er/2.6.0/packages/fcl-xml/units/i386-win32 -FuW:/md/dev/freepascal/compiler/2.6. 0/packages/fcl-passrc/units/i386-win32 -FuW:/md/dev/freepascal/compiler/2.6.0/pa ckages/chm/units/i386-win32 -FE. -FUunits/i386-win32 -di386 -dRELEASE fpclasscha rt.pp make[3]: Leaving directory `W:/md/dev/freepascal/compiler/2.6.0/utils/fpdoc' make -C fpcmkcfg all make[3]: Entering directory `W:/md/dev/freepascal/compiler/2.6.0/utils/fpcmkcfg' W:/md/dev/freepascal/binutils/i386-win32/gmkdir.exe -p units/i386-win32 __missing_command_DATA2INC -b -s fppkg.cfg fppkg.inc fppkg process_begin: CreateProcess((null), __missing_command_DATA2INC -b -s fppkg.cfg fppkg.inc fppkg, ...) failed. make (e=2): The system can not find the file specified. make[3]: *** [fppkg.inc] Error 2 make[3]: Leaving directory `W:/md/dev/freepascal/compiler/2.6.0/utils/fpcmkcfg' make[2]: *** [fpcmkcfg_all] Error 2 make[2]: Leaving directory `W:/md/dev/freepascal/compiler/2.6.0/utils' make[1]: *** [utils_all] Error 2 make[1]: Leaving directory `W:/md/dev/freepascal/compiler/2.6.0' make: *** [build-stamp.i386-win32] Error 2 W:\md\dev\freepascal\compiler\2.6.0 -- Marcos Douglas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
On Wed, Aug 3, 2011 at 2:31 PM, Marco van de Voort mar...@stack.nl wrote: In our previous episode, Marcos Douglas said: build and package scripts to be adapted, as well as the symlinks of ppc386 on *nix. Before branching all makefiles were regenerated, so an update will be big. Hi Marco, I got the new sources and tried to compile on WinXP: And you started with the last release in your %PATH%? Since that should contain data2inc.exe. I use ppc386 2.4.3 to compile and tools in /branches/fixes_2_4/install/binw32 With configuration I can compile /branches/fixes_2_4 and /trunk Where I got data2inc.exe and why I can compile trunk but not the 2.6.0 release? Thanks, Marcos Douglas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
On 03 Aug 2011, at 19:42, Marcos Douglas wrote: I use ppc386 2.4.3 to compile and tools in /branches/fixes_2_4/install/binw32 With configuration I can compile /branches/fixes_2_4 and /trunk Where I got data2inc.exe As Marco said, it is part of any default FPC installation that you download from our website. Compiling with just a compiler binary in your may work, but that is not a supported configuration for general use (a.o. reasons, because of the problem you have right now). Please always start from a *full* installation of the latest official release before reporting build problems. In 99.9% of the cases it solves all problems. and why I can compile trunk but not the 2.6.0 release? There is no 2.6.0 release yet. And the reason for your compilation error is that the time stamps on some include files in your fixes_2_6 branch are older than the files they are generated from. This can happen with a fresh svn checkout depending on the order in which files are downloaded and how much time passes in the mean time. Jonas___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
On Wed, Aug 3, 2011 at 2:47 PM, Jonas Maebe jonas.ma...@elis.ugent.be wrote: On 03 Aug 2011, at 19:42, Marcos Douglas wrote: I use ppc386 2.4.3 to compile and tools in /branches/fixes_2_4/install/binw32 With configuration I can compile /branches/fixes_2_4 and /trunk Where I got data2inc.exe As Marco said, it is part of any default FPC installation that you download from our website. Compiling with just a compiler binary in your may work, but that is not a supported configuration for general use (a.o. reasons, because of the problem you have right now). Please always start from a *full* installation of the latest official release before reporting build problems. In 99.9% of the cases it solves all problems. Sorry Jonas, but I always compile two versions (fixes_2_4 and trunk) using this script: http://wiki.freepascal.org/Installing_Lazarus#Compiling.2Finstalling_FPC_and_Lazarus_from_Sources_of_SVN_.28Win32.29 Always worked and some people used this script with success too. How I compiled before without having to compile the file data2inc? and why I can compile trunk but not the 2.6.0 release? There is no 2.6.0 release yet. And the reason for your compilation error is that the time stamps on some include files in your fixes_2_6 branch are older than the files they are generated from. This can happen with a fresh svn checkout depending on the order in which files are downloaded and how much time passes in the mean time. The sources are fresh. So, I will 'clean up' the sources and to try again... Marcos Douglas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
On 03/08/2011 19:01, Marcos Douglas wrote: On Wed, Aug 3, 2011 at 2:47 PM, Jonas Maebejonas.ma...@elis.ugent.be wrote: Please always start from a *full* installation of the latest official release before reporting build problems. In 99.9% of the cases it solves all problems. I had the same problem recently (data2inc) and also due to the same problem (not a *full* installation) And there are reasons why I don't have a full installation. I do not use linux often enough,a and I certainly haven't got around all the new build in installer systems. When I first started using fpc from SVN, my fpc knowledge wasn't good enough. And having an installation in the default location, would *always* lead to something pointing there, and my svn version not working, because stuff got mixed. Of course my fault. It would be some config, I didn't know, and hadn't fixed Now it's different, I can fix the fpc related config, If I need to. But I am using a very old distribution, I have no interest in spending time upgrading it, it still works. Neither do I want to spend time finding out how that installer system that came with it works, and how I can tell it to install the latest fpc version ( I have not tested, but I would suspect it still points to whatever version it was, when I installed the system / I usually, if I get the chance switch of all auto updates) I gues, I need to investigate installing the tar.gz release And then immediately remove all global config files and any ppu386 in the default path, since they have always affected my svn installations. Well, I can't complain, if the fpc compilation isn't always smooth, since I do not meet the requirements. --- data2inc seems to be part of fpc - I haven't seen any 3rd party package of this name (at least my older fedora does not offer it on it's own). So I wonder, if it is build from pascal source, then why can't that be part of the build process. I fit comes from somewhere else, then where from? Martin ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
On Wed, Aug 3, 2011 at 3:01 PM, Marcos Douglas m...@delfire.net wrote: On Wed, Aug 3, 2011 at 2:47 PM, Jonas Maebe jonas.ma...@elis.ugent.be wrote: On 03 Aug 2011, at 19:42, Marcos Douglas wrote: I use ppc386 2.4.3 to compile and tools in /branches/fixes_2_4/install/binw32 With configuration I can compile /branches/fixes_2_4 and /trunk Where I got data2inc.exe As Marco said, it is part of any default FPC installation that you download from our website. Compiling with just a compiler binary in your may work, but that is not a supported configuration for general use (a.o. reasons, because of the problem you have right now). Please always start from a *full* installation of the latest official release before reporting build problems. In 99.9% of the cases it solves all problems. Sorry Jonas, but I always compile two versions (fixes_2_4 and trunk) using this script: http://wiki.freepascal.org/Installing_Lazarus#Compiling.2Finstalling_FPC_and_Lazarus_from_Sources_of_SVN_.28Win32.29 Always worked and some people used this script with success too. How I compiled before without having to compile the file data2inc? and why I can compile trunk but not the 2.6.0 release? There is no 2.6.0 release yet. And the reason for your compilation error is that the time stamps on some include files in your fixes_2_6 branch are older than the files they are generated from. This can happen with a fresh svn checkout depending on the order in which files are downloaded and how much time passes in the mean time. The sources are fresh. So, I will 'clean up' the sources and to try again... Same error... I'm getting a fresh /fixes_2_4 to try to compile with the same script and tools in /branches /fixes_2_4/install/binw32... If it works, I will do the same with /trunk... If it works... well, IMHO, something is wrong in /branches/fixes_2_6 Marcos Douglas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
On Wed, Aug 3, 2011 at 3:27 PM, Marco van de Voort mar...@stack.nl wrote: In our previous episode, Marcos Douglas said: Sorry Jonas, but I always compile two versions (fixes_2_4 and trunk) using this script: http://wiki.freepascal.org/Installing_Lazarus#Compiling.2Finstalling_FPC_and_Lazarus_from_Sources_of_SVN_.28Win32.29 Always worked and some people used this script with success too. These kinds of issues are like the stockmarket: success in the past is no guarantee for the future. =) How I compiled before without having to compile the file data2inc? You simply didn't have encountered the situation that requires that file. But that situation is a definite possibility, which why it is packaged with every release for the past 10 years and longer. Sorry my question, but why data2inc can't that be part of the build process? If not possible, why don't put it in, eg, /install/binw32? Marcos Douglas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
On Wed, Aug 3, 2011 at 3:28 PM, Martin laza...@mfriebe.de wrote: --- data2inc seems to be part of fpc - I haven't seen any 3rd party package of this name (at least my older fedora does not offer it on it's own). So I wonder, if it is build from pascal source, then why can't that be part of the build process. I fit comes from somewhere else, then where from? Aha! +1 Marcos Douglas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
In our previous episode, Martin said: data2inc seems to be part of fpc - I haven't seen any 3rd party package of this name (at least my older fedora does not offer it on it's own). So I wonder, if it is build from pascal source, then why can't that be part of the build process. I fit comes from somewhere else, then where from? Because it is built relatively late, and couldn't be used in the buildprocess before. Moreover it is only occasionally needed (as Jonas said, in case of datestamp corruption, or when mistakes are made while committing) Note though that these problems are NOT even due to that. Both of you have explained that you have built snapshots (make all) successfully before. That means that this problem wouldn't be happening if those snapshots were properly installed. Every succesful make all generates a data2inc, and every make install installs it into the relevant bin directory. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
On Wed, Aug 3, 2011 at 3:55 PM, Marco van de Voort mar...@stack.nl wrote: In our previous episode, Martin said: data2inc seems to be part of fpc - I haven't seen any 3rd party package of this name (at least my older fedora does not offer it on it's own). So I wonder, if it is build from pascal source, then why can't that be part of the build process. I fit comes from somewhere else, then where from? Because it is built relatively late, and couldn't be used in the buildprocess before. Moreover it is only occasionally needed (as Jonas said, in case of datestamp corruption, or when mistakes are made while committing) Note though that these problems are NOT even due to that. Both of you have explained that you have built snapshots (make all) successfully before. That means that this problem wouldn't be happening if those snapshots were properly installed. Every succesful make all generates a data2inc, and every make install installs it into the relevant bin directory. So, I can put a old data2inc in /utils and to run 'make all'. It will use data2inc and, after, create a new data2inc binary, right? Marcos Douglas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
In our previous episode, Marcos Douglas said: Every succesful make all generates a data2inc, and every make install installs it into the relevant bin directory. So, I can put a old data2inc in /utils and to run 'make all'. In your PATH, or pass it with DATA2INC=(full path of data2inc binary) I always make install snapshots to a prefix, e.g. ~/builded and then symlink relevant binaries into my path (e.g. from ~/bin to ~/builded/bin/ and ~/builded/lib/fpc/x.y.z/ppc386) Typical binaries that I symlink are data2inc, fpcmake, fpcres, fpc and ppc386. On machines where I work on docs also fpdoc and makeskel ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
In our previous episode, Marcos Douglas said: This problem occurs just on Windows, ie, only Windows must have the data2inc.exe before run 'make all'? Sorry... but I never do this... I know, I know... 'stockmarket' right? No, it is universal. Some platforms (or better, filesystems) have a bigger chance of mutilating file dates though. I always make install snapshots to a prefix, e.g. ~/builded and then symlink relevant binaries into my path (e.g. from ~/bin to ~/builded/bin/ and ~/builded/lib/fpc/x.y.z/ppc386) My 'prefix' is the same directory, see the script: set myversion=%1 set myroot=%cd% set myFPC=%myroot%\compiler\%myversion% set mybinutils=%myroot%\binutils set PATH=%mybinutils%\i386-win32;%mybinutils%\x86_64-win64;%mybinutils%\arm-wince;%myFPC%\bin\i386-win32;%PATH% cd %myFPC% make clean all INSTALL_PREFIX=%myFPC% PP=%mybinutils%\ppc386.exe I have INSTALL_PREFIX=c:\ppversion and then have c:\ppversion\bin\i386-win32 in my path. I do this by having batchfiles like: @echo off if %OLDPATH% neq goto :nosave set OLDPATH=%PATH% :nosave SET PATH=%OLDPATH% PATH c:\pp251\bin\i386-win32;%PATH% for different versions and one separately for cygwin. This allows me to quickly change toolchains. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
On Wed, Aug 3, 2011 at 4:56 PM, Marco van de Voort mar...@stack.nl wrote: In our previous episode, Marcos Douglas said: This problem occurs just on Windows, ie, only Windows must have the data2inc.exe before run 'make all'? Sorry... but I never do this... I know, I know... 'stockmarket' right? No, it is universal. Some platforms (or better, filesystems) have a bigger chance of mutilating file dates though. I always make install snapshots to a prefix, e.g. ~/builded and then symlink relevant binaries into my path (e.g. from ~/bin to ~/builded/bin/ and ~/builded/lib/fpc/x.y.z/ppc386) My 'prefix' is the same directory, see the script: set myversion=%1 set myroot=%cd% set myFPC=%myroot%\compiler\%myversion% set mybinutils=%myroot%\binutils set PATH=%mybinutils%\i386-win32;%mybinutils%\x86_64-win64;%mybinutils%\arm-wince;%myFPC%\bin\i386-win32;%PATH% cd %myFPC% make clean all INSTALL_PREFIX=%myFPC% PP=%mybinutils%\ppc386.exe I have INSTALL_PREFIX=c:\ppversion and then have c:\ppversion\bin\i386-win32 in my path. The same for me: ... make clean all INSTALL_PREFIX=%myFPC% PP=%mybinutils%\ppc386.exe ... set PATH=%mybinutils%\i386-win32;%myFPC%\bin\i386-win32;%PATH% I do this by having batchfiles like: @echo off if %OLDPATH% neq goto :nosave set OLDPATH=%PATH% :nosave SET PATH=%OLDPATH% PATH c:\pp251\bin\i386-win32;%PATH% for different versions and one separately for cygwin. This allows me to quickly change toolchains. The same... but now only between /fixes_2_4 and /trunk I would like to override /fixes_2_4 to /fixes_2_6... just it! Marcos Douglas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 2.6.x branched, trunk becomes 2.7.1
On Wed, Aug 3, 2011 at 5:11 PM, Jonas Maebe jonas.ma...@elis.ugent.be wrote: On 03 Aug 2011, at 22:05, Marcos Douglas wrote: On Wed, Aug 3, 2011 at 4:56 PM, Marco van de Voort mar...@stack.nl wrote: I have INSTALL_PREFIX=c:\ppversion and then have c:\ppversion\bin\i386-win32 in my path. The same for me: ... make clean all INSTALL_PREFIX=%myFPC% PP=%mybinutils%\ppc386.exe ... set PATH=%mybinutils%\i386-win32;%myFPC%\bin\i386-win32;%PATH% If you installed an official fpc 2.4.4 from the website in %myFPC%\bin\i386-win32, then this directory will contain a data2inc.exe. If you did not install an official FPC 2.4.4 from the website or are not using that installation to compile new versions, then it is normal that things do not work as expected. Humm... the only difference between 2.4.5 and 2.6.0: the directory bin\i386-win32 does not exist (yet). I did not remember how I got the first version of my FPC... I'm sorry... Well, now works. I followed the Marco's tip: DATA2INC=(full path of data2inc binary) So, is possible to compile a new fresh source without a Official FPC. Thanks for your time, gentleman. Marcos Douglas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
