Am 11.01.2015 04:05 schrieb "Bee" :
>
> Hi,
>
> This morning I saw FPC's SVN was already marked for v.3.0. There must be
some reasons why it's not marked for v.2.8 (as successor for currently
v.2.6). May I ask... what are the targets and roadmap for FPC v.3.0?
>
> When I looked at the bugtracker, I
Hello,
I have some difficulties to compile my PASCAL code with external subroutine in
FORTRAN on MAC OS X Yosemite 10.10.1 using fpc 2.6.4.
The problem is the following: I need to run the program in Pascal containing
the external procedure in FORTRAN which uses the standard CERNLIB packages such
On 10/01/15 17:48, Vahe Sahakyan wrote:
> In the attached please find the code in PASCAL (as an example) with
> external procedure on FORTRAN which I’m training to compile. The names
> of these two programs are: “exmppas.p” and “exmpfrt.f”, and for
> compilation I'm using the following command
Hi Vahe
Am 11.01.2015 um 12:00 schrieb fpc-pascal-requ...@lists.freepascal.org:
> Message: 4
> Date: Sat, 10 Jan 2015 16:48:52 + (UTC)
> From: Vahe Sahakyan
> To: "fpc-pascal@lists.freepascal.org"
>
> Subject: [fpc-pascal] fpc2.6.4 compilation problem
> Message-ID:
>
> <2381777
On Sun, January 11, 2015 12:43, Schindler Karl-Michael wrote:
Hello Michael,
The original poster is apparently not subscribed to the list (although he
forgot to mention this fact in his post) - adding him. In Cc: now so that
he could see your response).
Tomas
> Am 11.01.2015 um 12:00 schrieb
Am 06.01.2015 23:46, schrieb Graeme Geldenhuys:
> Hi,
>
> Anybody know the status of MIPS32 support with Free Pascal?
>
> To be used on something like this board:
>
> http://shop.imgtec.com/uk/product/mips-creator-ci20/
>
Regression tests show that mipsel is working reasonably with linux:
ht
I see. So FPC development has no planned innovation and no vision what it
will become. It just takes whatever available. Alright. Thank you. :)
On Sun, Jan 11, 2015 at 3:30 PM, Sven Barth
wrote:
> Am 11.01.2015 04:05 schrieb "Bee" :
> >
> > Hi,
> >
> > This morning I saw FPC's SVN was already m
> The weird thing is that the linker only looks at /lib and /usr/lib, but not
/usr/lib32, which should be the location of 32-bit libraries on 64-bit
system. Using -Cn, I can see that link.res doesn't contain path to
/usr/lib32, and manually changing it makes the linking success.
OK, this one can b
