I am trying to write a small program using the nano-x library.
-
Unit NanoX;
interface
{$mode objfpc}
Const
LibNanoX='nano-X';
function GrOpen:longint;cdecl;external LibNanoX;
implementation
end.
--
program Nanoxdemo;
uses
NanoX,linux,sysutils;
begin
if
On Thu, 20 Jul 2006, Carsten Bager wrote:
I am trying to write a small program using the nano-x library.
-
Unit NanoX;
interface
{$mode objfpc}
Const
LibNanoX='nano-X';
function GrOpen:longint;cdecl;external LibNanoX;
implementation
end.
--
program
You need to link to the C library as well.
So, add
{$linklib c}
_Never_ add linklib c or linklib gcc directly, always work via unit initc.
That's what it is for.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
On Thu, 20 Jul 2006, Marco van de Voort wrote:
You need to link to the C library as well.
So, add
{$linklib c}
_Never_ add linklib c or linklib gcc directly, always work via unit initc.
That's what it is for.
I thought the compiler did this automatically when it detects a link to
the
On 17 Jul 2006 at 21:12, Florian Klaempfl wrote:
I'am currently thinking about implementing OpenMP support in FPC.
However, there is currently (to my knowledge) no pascal syntax defined
for OpenMp support. Do you think we can find a common syntax to simplify
things for users? I've some ideas
Hello everybody
I have just started working with the fpc compiler, and everything is great
except that when I start up the ide, it doesn’t show the compiler message. I
can close and restart the program and after several tries the compiler
messages show up. It may take 5 - 15 tries. This is
On Thu, 20 Jul 2006, Marco van de Voort wrote:
You need to link to the C library as well.
So, add
{$linklib c}
_Never_ add linklib c or linklib gcc directly, always work via unit initc.
That's what it is for.
I thought the compiler did this automatically when it detects a
Florian Klaempfl wrote:
I'am currently thinking about implementing OpenMP support in FPC.
However, there is currently (to my knowledge) no pascal syntax defined
for OpenMp support. Do you think we can find a common syntax to simplify
things for users? I've some ideas how it be done, but I want
On Thu, 20 Jul 2006, Marco van de Voort wrote:
(libdl,libgettext,libgcc), and to encapsulate libc errno access.
There shouldn't be a {$linklib C or linklib gcc in any unit. _always_ via
unit initc.
If you really believe that:
I suggest you start working on the sources in SVN then,
On Thu, 20 Jul 2006, Marco van de Voort wrote:
On Thu, 20 Jul 2006, Marco van de Voort wrote:
(libdl,libgettext,libgcc), and to encapsulate libc errno access.
There shouldn't be a {$linklib C or linklib gcc in any unit. _always_ via
unit initc.
If you really believe that:
I suggest you
On Thu, 20 Jul 2006, Marco van de Voort wrote:
If you really believe that:
I suggest you start working on the sources in SVN then, because there are
_a lot_ of them.
But I don't think that it should be done like that...
Because?
Because firstly I think that what initc does behind
On Thu, 20 Jul 2006, Marco van de Voort wrote:
On Thu, 20 Jul 2006, Marco van de Voort wrote:
If you really believe that:
I suggest you start working on the sources in SVN then, because there are
_a lot_ of them.
But I don't think that it should be done like that...
Because?
Because
I'm just writing to say for the new people that if the Free Pascal IDE is
not working for you, the command line fpc command has all you need right out
the box! If it doesn't seem to do something you want - the programmer's
manual (PDF I used anyway) has a ton of command line options - that might
You need to link to the C library as well.
When I use initc I get thise errors
Linking nanoxdemo
L:\Lib\fpc202\arm-linux\cprt0.o: In function `_start':
: undefined reference to `__libc_start_main'
L:\Lib\fpc202\arm-linux\cprt0.o: In function `_haltproc'
: undefined reference to `_fini'
On Thu, 20 Jul 2006, Marco van de Voort wrote:
(snip water under the bridge)
As for your arguments:
You are 100% right that it may be a good thing to have a central place which
somehow regulates access to libc; It will make things clearer and more
maintainable. However, if you want to
On Thu, 20 Jul 2006, Carsten Bager wrote:
You need to link to the C library as well.
When I use initc I get thise errors
Linking nanoxdemo
L:\Lib\fpc202\arm-linux\cprt0.o: In function `_start':
: undefined reference to `__libc_start_main'
L:\Lib\fpc202\arm-linux\cprt0.o: In function
2006/7/20, Steve Williams [EMAIL PROTECTED]:
Florian Klaempfl wrote:
I'am currently thinking about implementing OpenMP support in FPC.
However, there is currently (to my knowledge) no pascal syntax defined
for OpenMp support. Do you think we can find a common syntax to simplify
things for
Isn't there a copascal that already has established concurent pascal syntax?
if not, the other wirthian languages look like logical providers?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
When I use initc I get thise errors
Linking nanoxdemo
L:\Lib\fpc202\arm-linux\cprt0.o: In function `_start':
: undefined reference to `__libc_start_main'
L:\Lib\fpc202\arm-linux\cprt0.o: In function `_haltproc'
: undefined reference to `_fini'
L:\Lib\fpc202\arm-linux\cprt0.o: In function
On Thu, 20 Jul 2006, Carsten Bager wrote:
You need to link to the C library as well.
When I use initc I get thise errors
Linking nanoxdemo
L:\Lib\fpc202\arm-linux\cprt0.o: In function `_start':
: undefined reference to `__libc_start_main'
L:\Lib\fpc202\arm-linux\cprt0.o: In
On Thu, 20 Jul 2006, Carsten Bager wrote:
On Thu, 20 Jul 2006, Carsten Bager wrote:
You need to link to the C library as well.
When I use initc I get thise errors
Linking nanoxdemo
L:\Lib\fpc202\arm-linux\cprt0.o: In function `_start':
: undefined reference to `__libc_start_main'
On Thu, 20 Jul 2006, =?koi8-r?Q?=F0=A3=D4=D2
=EB=CF=D3=C1=D2=C5=D7=D3=CB=C9=CA?= wrote:
How can I write inline assembler procedure?
(FPC accepts the word inline, but generates call instruction etc.)
If there is a way, could anyone point to an example, please?
Currently you cannot inline
Michael Van Canneyt wrote:
On Thu, 20 Jul 2006, =?koi8-r?Q?=F0=A3=D4=D2
=EB=CF=D3=C1=D2=C5=D7=D3=CB=C9=CA?= wrote:
How can I write inline assembler procedure?
(FPC accepts the word inline, but generates call instruction etc.)
If there is a way, could anyone point to an example, please?
Marco van de Voort wrote:
Isn't there a copascal that already has established concurent pascal syntax?
Yes, there is, but its syntax is very limited AFAICS.
if not, the other wirthian languages look like logical providers?
Ada tasking? Well, too much overkill, I think. ;)
My problem with
Currently you cannot inline assembler routines, it is a known restriction.
I didn't get this one message.
If nothing else, you can skip the stack frame generation using
nostackframe keyword. Not that it would help that much probably...
Tomas
Oh, well.
Thanks for the answers.
On Mon, 17 Jul 2006 21:12:31 +0200
Florian Klaempfl [EMAIL PROTECTED] wrote:
I'am currently thinking about implementing OpenMP support in FPC.
Florian,
Have you looked at Pascal-FC (a language developped based Pascal/0, I
believe, by Alan Burns)? I've used it to teach multiprogramming, and it
John Coppens wrote:
On Mon, 17 Jul 2006 21:12:31 +0200
Florian Klaempfl [EMAIL PROTECTED] wrote:
I'am currently thinking about implementing OpenMP support in FPC.
Florian,
Have you looked at Pascal-FC (a language developped based Pascal/0, I
believe, by Alan Burns)?
Alan Burns? That's a
Rainer Stratmann wrote:
Am Donnerstag, 20. Juli 2006 13:44 schrieb Jason P Sage:
I know most of you know this stuff and it's a no brainer - but - I just
wanted to say this because I see people having problems sometimes getting
started and sometimes its easier to go around the ditch than to
Пётр Косаревский wrote:
How can I write inline assembler procedure?
(FPC accepts the word inline, but generates call instruction etc.)
Inline is only a recommendation.
If there is a way, could anyone point to an example, please?
Inlining assembler procedures efficently is rather hard, so
On 20 Jul 06, at 22:41, Florian Klaempfl wrote:
Rainer Stratmann wrote:
Am Donnerstag, 20. Juli 2006 13:44 schrieb Jason P Sage:
.
.
In my view these simple things must have highest priority.
In the Linux installation routine there is an install-question
something like do you want
Tomas Hajny wrote:
On 20 Jul 06, at 22:41, Florian Klaempfl wrote:
Rainer Stratmann wrote:
Am Donnerstag, 20. Juli 2006 13:44 schrieb Jason P Sage:
.
.
In my view these simple things must have highest priority.
In the Linux installation routine there is an install-question
something
Tomas Hajny wrote:
;-) What would you think about distribution of
Win32 version with install.bat script asking you
to choose whether you want to put cygwin1.dll in
system32 or your new bin directory?
So all you're asking for is a If you don't know the answer, just press
ENTER? Isn't that
Steve Williams wrote:
Florian Klaempfl wrote:
I'am currently thinking about implementing OpenMP support in FPC.
However, there is currently (to my knowledge) no pascal syntax defined
for OpenMp support. Do you think we can find a common syntax to simplify
things for users? I've some ideas how
Marc Weustink wrote:
Steve Williams wrote:
Using some of the documented examples in the v2.5 spec:
Example A.1.1:
procedure a1(n: Integer; a: PSingleArray; b: PSingleArray);
var
i: Integer;
begin
{$omp parallel for}
for i := 1 to n - 1 do
b^[i] := (a^[i] + a^[i - 1]) / 2.0;
end;
On Thu, 20 Jul 2006 21:11:49 +0200
Vinzent Höfler [EMAIL PROTECTED] wrote:
Alan Burns? That's a name which rings a bell. You could have send the
URL, though. ;)
http://www-users.cs.york.ac.uk/~burns/pf.html
Hmm, and taking a peek look at the examples, it doesn't really surprise
me,
Marc Weustink wrote:
Steve Williams wrote:
I would suggest something along the lines of the C/C++ implementation,
but using the Pascal form of compiler directives.
Using some of the documented examples in the v2.5 spec:
Example A.1.1:
procedure a1(n: Integer; a: PSingleArray; b:
Steve Williams wrote:
Marc Weustink wrote:
Steve Williams wrote:
I would suggest something along the lines of the C/C++
implementation, but using the Pascal form of compiler directives.
Using some of the documented examples in the v2.5 spec:
Example A.1.1:
procedure a1(n: Integer; a:
37 matches
Mail list logo
