Dave Parsons wrote:
> On Mon, 14 Aug 2006 18:01:10 +0200, Jonas Maebe wrote:
>> On 14 aug 2006, at 17:44, Peter Vreman wrote:
>>
>> > And you need GNU (cross)binutils for the
>> > target platform
>>
>> Or you can compile to assembler code, copy all assembler files and
>> the linker script to the ta
On 14 Aug 2006, at 18:28, Dave Parsons wrote:
Well, it should be possible then but are you really saying that the
original FPC was all written in assembler?
No, the original FPC was written in Turbo Pascal (i.e., for Dos/16
bit). From there the cross compilation to Dos/32 bit assembler, OS/
On Mon, 14 Aug 2006 18:01:10 +0200, Jonas Maebe wrote:
>
> On 14 aug 2006, at 17:44, Peter Vreman wrote:
>
> > And you need GNU (cross)binutils for the
> > target platform
>
> Or you can compile to assembler code, copy all assembler files and
> the linker script to the target machine and asse
> Jonas Maebe wrote:
> >
> > On 14 aug 2006, at 17:44, Peter Vreman wrote:
> >
> >> And you need GNU (cross)binutils for the
> >> target platform
> >
> > Or you can compile to assembler code, copy all assembler files and the
> > linker script to the target machine and assemble/link there (which
Jonas Maebe wrote:
>
> On 14 Aug 2006, at 18:31, Florian Klaempfl wrote:
>
>>> Or you can compile to assembler code, copy all assembler files and the
>>> linker script to the target machine and assemble/link there (which is
>>> what I always do).
>>
>> That's 1.x times technology :)
>
> But very
On 14 Aug 2006, at 18:31, Florian Klaempfl wrote:
Or you can compile to assembler code, copy all assembler files and
the
linker script to the target machine and assemble/link there (which is
what I always do).
That's 1.x times technology :)
But very fast and much less work than even just
Dave Parsons wrote:
> On Mon, 14 Aug 2006 13:15:51 +0200 (CEST), Tomas Hajny wrote:
>> Dave Parsons wrote:
>> > On Sun, 13 Aug 2006 23:08:29 +0200, Tomas Hajny wrote:
.
.
> I realize that OS/2 and OpenVMS are fringe operating systems so I
> expect to have to do some development of both fpc & Laza
Jonas Maebe wrote:
>
> On 14 aug 2006, at 17:44, Peter Vreman wrote:
>
>> And you need GNU (cross)binutils for the
>> target platform
>
> Or you can compile to assembler code, copy all assembler files and the
> linker script to the target machine and assemble/link there (which is
> what I always
On 14 aug 2006, at 17:44, Peter Vreman wrote:
And you need GNU (cross)binutils for the
target platform
Or you can compile to assembler code, copy all assembler files and
the linker script to the target machine and assemble/link there
(which is what I always do).
Jonas
_
> I realize that OS/2 and OpenVMS are fringe operating systems so I
> expect to have to do some development of both fpc & Lazarus there
> myself, the question is really how much work i.e. time is required.
>
> To help me, I would like to know for instance how to bootstrap fpc
> on a new platform. W
On Mon, 14 Aug 2006 13:15:51 +0200 (CEST), Tomas Hajny wrote:
Hello Tomas,
> Dave Parsons wrote:
> > On Sun, 13 Aug 2006 23:08:29 +0200, Tomas Hajny wrote:
>
> Hello Dave,
> > I'm new to this list and my interests are in Lazarus under
> > OS/2 and Linux and therefore by inference fpc.
>
> Laza
Graeme Geldenhuys wrote:
On 8/14/06, Vincent Snijders <[EMAIL PROTECTED]> wrote:
You miss the point: Delphi compatibility mode is for people who
develop for FPC, but
want to compile occasionally in Delphi. In the current situation they
are not aware
of this weakness of Delphi (no support of $EN
On 14 aug 2006, at 13:14, Vincent Snijders wrote:
Is valgrind support broken or do
I have to do something beyond setting the valgrind compiler switch?
You don't have to do anything but compile all your program's units
and the program itself with the -gv switch.
Note: all includes the RTL.
Dave Parsons wrote:
> On Sun, 13 Aug 2006 23:08:29 +0200, Tomas Hajny wrote:
Hello Dave,
>> I'd like to announce that the third (and
>> hopefully last) release candidate for FPC 2.0.4
>> is available for download for most platforms
>> (i386-linux, x86_64-linux, i386-win32, powerpc-
>> macosx, i38
Jonas Maebe schreef:
On 14 aug 2006, at 13:06, Helmut Hartl wrote:
Is valgrind support broken or do
I have to do something beyond setting the valgrind compiler switch?
You don't have to do anything but compile all your program's units and
the program itself with the -gv switch.
Note: all i
On Mon, 14 Aug 2006 11:39:29 +0200, Vincent Snijders wrote:
>
> Most of the lazarus snapshots are built with fpc 2.0.4-rc3 too.
>
> For download locations of those test builds, see
> http://wiki.lazarus.freepascal.org/index.php/Lazarus_Snapshots_Downloads
>
Hi,
Thanks, I downloaded the sourc
On Mon, 14 Aug 2006 11:23:28 +0200 (Romance Daylight Time), Michael Van Canneyt
wrote:
>
>
> On Mon, 14 Aug 2006, Dave Parsons wrote:
>
> > So, thanks for this rc which I have downloaded and built
> > under OS/2. I'm still feeling my way around so I'm not sure
> > that everything compiled that
On 14 aug 2006, at 13:06, Helmut Hartl wrote:
If memory is acquired through:
"Getmem(x,size)"
and Freed through
"Freemem(x,size)"
I have a leak because Getmem reserves occasionally
more mem as specified in size?
No. Well, it will round up all allocations to a multiple of X bytes
(X depend
>
> I'll look into the bug report the next days.
>
Hello Florian,
Thanks for fixing the first bug, but
i am afraid, that there exist other memory related problems in
FPC 2.0.3 (fixes branch). Our applications are not memory stable.
(Related Bugs 7174, 7209)
I am in the moment not able to repro
On 8/14/06, Daniël Mantione <[EMAIL PROTECTED]> wrote:
mode. To write new code that is compilable by both FPC and Delphi, Objpas
mode should suit as well as Delphi mode.
Not quite! The project I am working on (tiOPF) is mainly used by
Delphi developers, as I mentioned before. My first thought
On Mon, 14 Aug 2006, Daniël Mantione wrote:
Op Mon, 14 Aug 2006, schreef Vincent Snijders:
You miss the point: Delphi compatibility mode is for people who develop for
FPC, but want to compile occasionally in Delphi.
It can be used that way, but its main purpose is to support Delphi
const
Op Mon, 14 Aug 2006, schreef Vincent Snijders:
> You miss the point: Delphi compatibility mode is for people who develop for
> FPC, but want to compile occasionally in Delphi.
It can be used that way, but its main purpose is to support Delphi
constructions that we consider broken and therefore
On 8/14/06, Vincent Snijders <[EMAIL PROTECTED]> wrote:
You miss the point: Delphi compatibility mode is for people who develop for
FPC, but
want to compile occasionally in Delphi. In the current situation they are not
aware
of this weakness of Delphi (no support of $ENDIF for $IF), until they
Daniël Mantione schreef:
Op Mon, 14 Aug 2006, schreef Graeme Geldenhuys:
On 8/14/06, Peter Vreman <[EMAIL PROTECTED]> wrote:
Is this a feature or a FPC bug? FPC allows the $IF to be closed
with
the $ENDIF as well as the $IFEND. This is not Delphi compatible.
The closing tag for $IF is $IFE
Op Mon, 14 Aug 2006, schreef Graeme Geldenhuys:
> On 8/14/06, Peter Vreman <[EMAIL PROTECTED]> wrote:
> > > Is this a feature or a FPC bug? FPC allows the $IF to be closed
> > > with
> > > the $ENDIF as well as the $IFEND. This is not Delphi compatible.
> > >
> > > The closing tag for $IF is
Tomas Hajny schreef:
Hello,
I'd like to announce that the third (and
hopefully last) release candidate for FPC 2.0.4
is available for download for most platforms
(i386-linux, x86_64-linux, i386-win32, powerpc-
macosx, i386-go32v2, arm-linux and powerpc-
linux). You can download it from
ftp:
On 8/14/06, Peter Vreman <[EMAIL PROTECTED]> wrote:
> Is this a feature or a FPC bug? FPC allows the $IF to be closed with
> the $ENDIF as well as the $IFEND. This is not Delphi compatible.
>
> The closing tag for $IF is $IFEND
> The closing tag for $IFDEF is $ENDIF
Feature.
Maybe this shoul
On Mon, 14 Aug 2006, Dave Parsons wrote:
On Sun, 13 Aug 2006 23:08:29 +0200, Tomas Hajny wrote:
Hello,
I'd like to announce that the third (and
hopefully last) release candidate for FPC 2.0.4
is available for download for most platforms
(i386-linux, x86_64-linux, i386-win32, powerpc-
macosx
> Looking at the code below...
>
> {$if defined(ver2_0)}
> {$note This is not delphi compatible. }
> {$endif}
>
>
> Is this a feature or a FPC bug? FPC allows the $IF to be closed with
> the $ENDIF as well as the $IFEND. This is not Delphi compatible.
>
> The closing tag for $IF is $IFEND
> The
On Sun, 13 Aug 2006 23:08:29 +0200, Tomas Hajny wrote:
> Hello,
>
> I'd like to announce that the third (and
> hopefully last) release candidate for FPC 2.0.4
> is available for download for most platforms
> (i386-linux, x86_64-linux, i386-win32, powerpc-
> macosx, i386-go32v2, arm-linux and p
Looking at the code below...
{$if defined(ver2_0)}
{$note This is not delphi compatible. }
{$endif}
Is this a feature or a FPC bug? FPC allows the $IF to be closed with
the $ENDIF as well as the $IFEND. This is not Delphi compatible.
The closing tag for $IF is $IFEND
The closing tag for $IF
On 8/14/06, Marco van de Voort <[EMAIL PROTECTED]> wrote:
> {$if defined(ver1) or (defined(ver2_0) and (fpc_patch<2))}
> {$fatal tiOPF2 requires at least FPC 2.0.2}
> {$ELSEIF (defined(ver2_0) and (fpc_patch=2))}
> {$DEFINE FPC202}
> {$ELSE}
> {$DEFINE FPC202OrAbove}
> {$IFEND
Thanks for clearing this up.
Regards,
- Graeme -
On 8/13/06, Marco van de Voort <[EMAIL PROTECTED]> wrote:
My take:
The documentation uses a macro (see fpcdocs/fpc.sty)
\newcommand{\fpc}{Free Pascal\xspace}
The contraction freepascal is only for places where spaces are not desirable
(file
> What is the correct spelling of FPC???
>
> * FreePascal
> * Free Pascal
> * freepascal
>
> The www.freepasal.org uses both spellings. In the web browser title
> bar it is Free Pascal, but in the text heading it is freepascal,
> etc... I am trying to get my documentation in order
My take
> On 8/13/06, Darius Blaszijk <[EMAIL PROTECTED]> wrote:
> I have the same issue... Chicken and Egg situation. Changes have been
> added to FPCUnit after FPC 2.0.2, but I need them now in Lazarus. I
> applied a few patches, but most of them I am holding off until after
> the the FPC 2.0.4 release
Jonas Maebe wrote:
On 13 aug 2006, at 21:46, Felipe Monteiro de Carvalho wrote:
1. Add symbian target to the compiler
How exactly do I add symbian target to the compiler? I mean, which
files should I start altering?
compiler/system.pas, compiler/systems/i_symbian.pas,
compiler/systems/t_s
36 matches
Mail list logo
