Ludo Brands wrote:
TApplication.HandleException Illegal character in format string
Stack trace:
$000736FC STOREFORMAT, line 978 of
/export/home/local-src/fpc/fpcbuild-2.4.4/fpcsrc/rtl/objpas/sy
sutils/dati.inc
$00072E20 FORMATDATETIME, line 796 of
/export/home/local-src/fpc/fpcbui
> TApplication.HandleException Illegal character in format string
>Stack trace:
>$000736FC STOREFORMAT, line 978 of
> /export/home/local-src/fpc/fpcbuild-2.4.4/fpcsrc/rtl/objpas/sy
> sutils/dati.inc
>$00072E20 FORMATDATETIME, line 796 of
> /export/home/local-src/fpc/fpcbuild-2.4
Marco van de Voort wrote:
On Thu, Jul 28, 2011 at 03:33:47PM +0200, Ludo Brands wrote:
Ludo, in your instructions for Intel you've got an FPC= shell
variable:
should that be PPC=?
FPC= is a synonym of PP=, no?
No. PP= the compiler. "ppc*.exe" with *=target architecture
FPC= the frontloade
On Thu, Jul 28, 2011 at 03:33:47PM +0200, Ludo Brands wrote:
> > Ludo, in your instructions for Intel you've got an FPC= shell
> > variable:
> > should that be PPC=?
> >
>
> FPC= is a synonym of PP=, no?
No. PP= the compiler. "ppc*.exe" with *=target architecture
FPC= the frontloader binary t
> Ludo, in your instructions for Intel you've got an FPC= shell
> variable:
> should that be PPC=?
>
FPC= is a synonym of PP=, no?
> I think we might need to point out that export is a Bashism.
>
It is posix (http://www.unix.com/man-page/POSIX/1posix/export/). You're
right sh in Oracle doe
