I will look into that tomorrow, but that won't make it to the 1.9 release I think.

El Mi�rcoles, 5 de Noviembre de 2003 20:08, Marco van de Voort escribi�:

Fixed, I hope.

Now, compiling Lazarus is OK. Thanks.

Hello:

Linux+fpc-1.0.10
Compiling last CVS Lazarus, here you have a bug

Compiling filectrl.pp
filectrl.inc(461,8) Error: Identifier not found MODE_T filectrl.inc(461,14) Error: Error in type definition filectrl.inc(472,29) Error: Incompatible types: got "WORD" expected "<erroneous type>"
filectrl.inc(473,21) Error: Incompatible types: got "<erroneous type>" expected "LONGINT"
filectrl.inc(476,21) Error: Incompatible types: got "<erroneous type>" expected "LONGINT"
filectrl.inc(479,21) Error: Incompatible types: got "<erroneous type>" expected "LONGINT"
filectrl.inc(482,21) Error: Incompatible types: got "<erroneous type>" expected "LONGINT"
filectrl.inc(487,21) Error: Incompatible types: got "<erroneous type>" expected "LONGINT"
filectrl.inc(491,21) Error: Incompatible types: got "<erroneous type>" expected "LONGINT"
filectrl.inc(495,21) Error: Incompatible types: got "<erroneous type>" expected "LONGINT"
filectrl.inc(500,21) Error: Incompatible types: got "<erroneous type>" expected "LONGINT"
filectrl.inc(504,21) Error: Incompatible types: got "<erroneous type>" expected "LONGINT"
filectrl.inc(508,21) Error: Incompatible types: got "<erroneous type>" expected "LONGINT"
filectrl.inc(513,21) Error: Incompatible types: got "<erroneous type>" expected "LONGINT"
filectrl.inc(517,21) Error: Incompatible types: got "<erroneous type>" expected "LONGINT"
filectrl.inc(521,21) Error: Incompatible types: got "<erroneous type>" expected "LONGINT"
filectrl.pp(199) Fatal: There were 16 errors compiling module, stopping make[1]: *** [allunits.ppu] Error 1
make[1]: Leaving directory `/home/mapelo/Lazarus/lazarus/lazarus/lcl' make: *** [lcl] Error 2
bash-2.05b$

oops. sorry my bad. I meant filectrl.inc :)

Andrew

Just a question, why did you change it to longint, and not to word?

Regards,
Vincent.

Fixed, I hope.

After the latest batch of updates from everybody for 1.1/1.9 I am no longer capable of compiling current cvs lazarus with 1.0.10, I first get an error on mode_t not found in fileproc.inc, and after that I got a whole slew of other errors I didn't bother to write down.

I only had a problem with filectrl.inc not fileproc.inc.

I tcan be solved by changing line 461 of filectrl.inc to
  mode:{$IFDEF Ver1_0}word{$ELSE}mode_t{$ENDIF};

I am able to build it, but running it gives this error. Therefore I reported this bug on the fpc bug tracker, bug number 2761, with a small sample program showing the bug. A few days ago it crashed on the error, but now it is silently caught, but error still happens. So no compiling from the IDE is possible.

Vincent.

After the latest batch of updates from everybody for 1.1/1.9 I am no longer capable of compiling current cvs lazarus with 1.0.10, I first get an error on mode_t not found in fileproc.inc, and after that I got a whole slew of other errors I didn't bother to write down.

Since I had been wanting to try 1.1 again anyway I installed a cvs snapshot, and found that I was unable to link lazarus, upon linking of ./lazarus I was given lot of unresolved symbols "LEX" when I tried a make clean all. however using my gtk2 script, a gtk2 lazarus built fine. So I tried running make again, and this time it linked properly. make clean all always fails. odd.

Also I am unable to build lazarus from within lazarus with fpc1.9, it gives me a "unable to create pipe" error.

Andrew

It is a longint on FreeBSD :_)

But afaik this is the case on linux also nowadays. Linux also changed a bit after the creation of the original linux unit :-)

This kind of change illustrates some of the reasons behind the change of the linux port.

Adding proper typing aids portability, but also change through time.