[fpc-pascal] Embedded ARM system unit

2005-08-23 Thread Carsten Bager
I am in the first stage of creating a system unit for
Embedded ARM. Things are working but I get a lot of
Warnings and Hints (See some of them below).
Should I be worried about this?
In the "fpc_InitializeUnits" procedure I have excluded the call
to the "fpc_cpuinit" procedure, my system cannot start if it is
included in the start up code. I cannot figure out the meaning
of this procedure. Dos anyone know what it is meant to do.

Regards

Carsten

(*
procedure fpc_cpuinit;
begin
  asm
rfs r0
and r0,r0,#0xffe0
orr r0,r0,#0x0002
wfs r0
  end;
end;
**)



---
generic.inc(595,13) Warning: Mixing signed expressions and longwords
gives a 64bit result
generic.inc(678,3) Hint: Type size mismatch, possible loss of data /
range check error
generic.inc(679,17) Hint: Type size mismatch, possible loss of data /
range check error
generic.inc(1094,8) Hint: Conversion between ordinals and pointers is
not portable
generic.inc(1095,40) Hint: Conversion between ordinals and pointers is
not portable
ostypes.inc(78,16) Hint: Local type "TStat" is not used
ostypes.inc(79,16) Hint: Local type "PStat" is not used
ostypes.inc(140,16) Hint: Local type "TDirent" is not used
ostypes.inc(169,16) Hint: Local type "TDir" is not used
ostypes.inc(178,16) Hint: Local type "TUtimBuf" is not used
ostypes.inc(179,16) Hint: Local type "pUtimBuf" is not used
ostypes.inc(181,16) Hint: Local type "FLock" is not used
ostypes.inc(200,16) Hint: Local type "TTms" is not used
ostypes.inc(201,16) Hint: Local type "PTms" is not used
ostypes.inc(204,14) Hint: Local type "pFDSet" is not used
ostypes.inc(210,15) Hint: Local type "TTimeZone" is not used
ostypes.inc(217,5) Hint: Local const "F_OK" is not used
ostypes.inc(218,5) Hint: Local const "R_OK" is not used
ostypes.inc(219,5) Hint: Local const "W_OK" is not used
ostypes.inc(220,5) Hint: Local const "X_OK" is not used
ostypes.inc(222,5) Hint: Local const "SEEK_SET" is not used
ostypes.inc(223,5) Hint: Local const "SEEK_CUR" is not used
ostypes.inc(224,5) Hint: Local const "SEEK_END" is not used
ostypes.inc(228,5) Hint: Local const "O_WRONLY" is not used
ostypes.inc(229,5) Hint: Local const "O_RDWR" is not used
ostypes.inc(244,5) Hint: Local const "O_CREAT" is not used
ostypes.inc(245,5) Hint: Local const "O_EXCL" is not used
ostypes.inc(246,5) Hint: Local const "O_NOCTTY" is not used
ostypes.inc(247,5) Hint: Local const "O_TRUNC" is not used
ostypes.inc(248,5) Hint: Local const "O_APPEND" is not used
ostypes.inc(250,5) Hint: Local const "O_NDELAY" is not used
ostypes.inc(251,5) Hint: Local const "O_SYNC" is not used
ostypes.inc(252,5) Hint: Local const "O_DIRECT" is not used
ostypes.inc(253,5) Hint: Local const "O_LARGEFILE" is not used
ostypes.inc(254,5) Hint: Local const "O_DIRECTORY" is not used
ostypes.inc(255,5) Hint: Local const "O_NOFOLLOW" is not used
ostypes.inc(270,5) Hint: Local const "WNOHANG" is not used
ostypes.inc(271,5) Hint: Local const "WUNTRACED" is not used
ostypes.inc(289,3) Hint: Local const "F_GetFd" is not used
ostypes.inc(290,3) Hint: Local const "F_SetFd" is not used
ostypes.inc(291,3) Hint: Local const "F_GetFl" is not used
ostypes.inc(292,3) Hint: Local const "F_SetFl" is not used
ostypes.inc(293,3) Hint: Local const "F_GetLk" is not used
ostypes.inc(294,3) Hint: Local const "F_SetLk" is not used
ostypes.inc(295,3) Hint: Local const "F_SetLkW" is not used
ostypes.inc(296,3) Hint: Local const "F_SetOwn" is not used
ostypes.inc(297,3) Hint: Local const "F_GetOwn" is not used
signal.inc(32,3) Hint: Local const "SA_NOCLDSTOP" is not used
signal.inc(33,3) Hint: Local const "SA_NOCLDWAIT" is not used
signal.inc(35,3) Hint: Local const "SA_SHIRQ" is not used
signal.inc(36,3) Hint: Local const "SA_STACK" is not used
signal.inc(37,3) Hint: Local const "SA_RESTART" is not used
signal.inc(38,3) Hint: Local const "SA_INTERRUPT" is not used
signal.inc(39,3) Hint: Local const "SA_NOMASK" is not used
signal.inc(40,3) Hint: Local const "SA_ONESHOT" is not used
signal.inc(42,3) Hint: Local const "SIG_BLOCK" is not used
signal.inc(44,3) Hint: Local const "SIG_SETMASK" is not used
signal.inc(47,3) Hint: Local const "SIG_DFL" is not used
signal.inc(48,3) Hint: Local const "SIG_IGN" is not used
signal.inc(49,3) Hint: Local const "SIG_ERR" is not used
signal.inc(87,3) Hint: Local const "SIGHUP" is not used
signal.inc(88,3) Hint: Local const "SIGINT" is not used
signal.inc(89,3) Hint: Local const "SIGQUIT" is not used
signal.inc(91,3) Hint: Local const "SIGTRAP" is not used
signal.inc(92,3) Hint: Local const "SIGABRT" is not used
signal.inc(93,3) Hint: Local const "SIGIOT" is not used
signal.inc(96,3) Hint: Local const "SIGKILL" is not used
signal.inc(97,3) Hint: Local const "SIGUSR1" is not used
signal.inc(99,3) Hint: Local const "SIGUSR2" is not used
signal.inc(100,3) Hint: Local const "SIGPIPE" is not used
signal.inc(101,3) Hint: Local const "SIGALRM" is not used
signal.in

Re: [fpc-pascal] Embedded ARM system unit

2005-08-23 Thread Marco van de Voort
> I am in the first stage of creating a system unit for 
> Embedded ARM. Things are working but I get a lot of 
> Warnings and Hints (See some of them below).
> Should I be worried about this?

I see no troubling ones. THe first few mean that generic might not be 64-bit
clean, but are probably false. (since generic.inc is used for the 64-bit ports 
too),
the others are simply unused Unix symbols. This is normal, because these 
includefiles
are also used in a few other places (like baseunix), where they _are_ used.

> In the "fpc_InitializeUnits" procedure I have excluded the call 
> to the "fpc_cpuinit" procedure, my system cannot start if it is 
> included in the start up code. I cannot figure out the meaning 
> of this procedure. Dos anyone know what it is meant to do.

> (*
> procedure fpc_cpuinit;
> begin
>   asm
> rfs r0
> and r0,r0,#0xffe0
> orr r0,r0,#0x0002
> wfs r0
>   end;
> end;

Probably modifications to the processor's exceptions registers. IOW, enable 
certain exceptions so
that they can be trapped to Delphi language exceptions.

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal


[fpc-pascal] building docs from svn

2005-08-23 Thread Bob Barry
I've copied current svn of fpc2_fixes and fpcdocs to a working directory:

   asterix:svn> ls -ld fpc fpcdocs
   drwxr-xr-x  14 root root 4096 Aug 23 16:09 fpc
   drwxr-xr-x  44 root root 4096 Aug 23 17:12 fpcdocs

Fpc compiles OK, but when I try to generate html docs I get:

   asterix:svn> cd fpcdocs
   asterix:fpcdocs> make html
   make -C ../fpc/compiler checkdir msg2inc
   make[1]: Entering directory `/home/bobb/freepascal/svn/fpc/compiler'
   make[1]: *** No rule to make target `checkdir'.  Stop.
   make[1]: Leaving directory `/home/bobb/freepascal/svn/fpc/compiler'
   make: *** [../fpc/compiler/msg2inc] Error 2

It looks like a cooperative entry in the fpc/compiler Makefile, and a msg2inc
file, are needed for this to work.

Is there a way of switching the included messages off?

Thanks,

Bob Barry


___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal


[fpc-pascal] Re: KeyPressed

2005-08-23 Thread Lowell C. Savage

Thanks for the replies Michael, Eduardo, and Martin!

It looks like I'll have to see what functions are being called to use the 
Video and Drivers units and see what I can do to work around them or 
something.  Ugh.  Oh well, better that than another dead end.


Thanks!

Lowell

Michael Van Canneyt <[EMAIL PROTECTED]> wrote, in part:

> I'm using: CRT, IO, DOS, Video, Printer, Graph, and Drivers.

This is the problem. You can't use the Drivers, CRT and Video unit together.
Each of them tries to catch keystrokes, and they will randomly receive them.
(depending on thread usage).

You should use only Video or only CRT or only Drivers
(though it can be that drivers and video work together)

> And I don't care about multi-platform, so the C library DLL looks kind 
of like

> the way to go.

It will still cause problems, because the C library also will interfere 
with the

Video and CRT units...

It's planned to base the CRT unit on the video unit (so they would work 
together),

but until now no-one had time.

From: [EMAIL PROTECTED] (Marco van de Voort)

crt.keypressed etc. However that doesn't change the picture that Michael 
paints,
since the units must still be USES'd, and thus the init code that hooks 
input/output

are run.


Lowell C. Savage
[EMAIL PROTECTED]
505-667-6964 (office/msg)
360-961-8965 (cell/msg)
505-667-4341 (shared fax) 




___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal