Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2003-11

A bug for fpc 1.9.0

4 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Unknown author

Hello, everyone,

I downloaded the newest fpc-1.9.0-i386.rpm and installed it on RedHat linux 9.0. But I found that if a program uses the unit "linux", it will output many errors when compiling it:

unitbar.pp(130,17) Error: Identifier not found "PGlob"
unitbar.pp(130,22) Error: Error in type definition
unitbar.pp(131,17) Error: Identifier not found "stat"
unitbar.pp(131,21) Error: Error in type definition
unitbar.pp(134,36) Error: Identifier not found "PGlob"
unitbar.pp(134,41) Error: Error in type definition
unitbar.pp(141,5) Error: Identifier not found "LinuxError"
unitbar.pp(149,8) Error: Identifier not found "LinuxError"
unitbar.pp(151,11) Error: Identifier not found "Glob"
unitbar.pp(154,17) Error: Incompatible types: got "<erroneous type>"
expected "Pointer"
unitbar.pp(155,23) Error: Illegal qualifier
unitbar.pp(157,20) Error: Identifier not found "fstat"
unitbar.pp(159,22) Error: Illegal qualifier
unitbar.pp(162,22) Error: Illegal qualifier
unitbar.pp(162,31) Error: Identifier not found "STAT_IFREG"
unitbar.pp(166,42) Error: Illegal qualifier
unitbar.pp(167,31) Error: Illegal qualifier
unitbar.pp(167,40) Error: Identifier not found "STAT_IFDIR"
unitbar.pp(177,19) Error: Identifier not found "Glob"
unitbar.pp(184,18) Error: Illegal qualifier
unitbar.pp(186,14) Error: Incompatible types: got "<erroneous type>"
expected "Pointer"
unitbar.pp(187,11) Error: Identifier not found "Globfree"
unitbar.pp(187,23) Error: Illegal expression
unitbar.pp(191,18) Error: Illegal qualifier
unitbar.pp(243,11) Error: Identifier not found "stat"
unitbar.pp(243,15) Error: Error in type definition
unitbar.pp(253,12) Error: Identifier not found "FExpand"
unitbar.pp(254,12) Error: Identifier not found "DirName"
unitbar.pp(267,12) Error: Identifier not found "fstat"
unitbar.pp(268,40) Error: Identifier not found "linuxerror"
unitbar.pp(268,51) Error: Illegal expression
unitbar.pp(273,14) Error: Illegal qualifier
unitbar.pp(273,23) Error: Identifier not found "STAT_IFREG"
unitbar.pp(277,23) Error: Illegal qualifier
unitbar.pp(277,32) Error: Identifier not found "STAT_IFDIR"
unitbar.pp(279,13) Error: Identifier not found "FExpand"
unitbar.pp(343,16) Error: Identifier not found "DirName"
unitbar.pp(347,34) Error: Identifier not found "BaseName"
unitbar.pp(348,20) Error: Identifier not found "DirName"
unitbar.pp(354,34) Error: Identifier not found "BaseName"
unitbar.pp(355,20) Error: Identifier not found "DirName"
    It must be a bug of fpc 1.9.0 because it's okay for fpc 1.0.10.
    yours,
    kenny
Marco van de Voort
to Unknown author
I downloaded the newest fpc-1.9.0-i386.rpm and installed it on RedHat linux 9.0. But I found that if a program uses the unit "linux", it will output many errors when compiling it:

[big snip]

It must be a bug of fpc 1.9.0 because it's okay for fpc 1.0.10.

Unit linux is considered legacy, since it has many fundamental issues.

However the old unportable 1.0.x unit will be provided as legacy unit for linux/i386 as unit "oldlinux".

The 1.9 unix units are still a bit in flux, so oldlinux might behave a bid unpredicatable. I hope to correct that in the next version.

paradice
to Marco van de Voort

I get the above error code when compiling a specific unit with the new 1.9.0 beta under Win32.

It doesn't occur under either 1.0.10 or 1.0.6, which are the other two versions I keep around to test things. It only occurs when *compiling* the unit. When *building* the unit, it compiles perfectly, but if I immediately try to compile after this, I get the same error again.

I would post the unit on my website & make a link here, except it's tied in to quite a few others...

any ideas?

Peter Vreman
to paradice
Show quoted text 15 lines
I get the above error code when compiling a specific unit with the new 1.9.0 beta under Win32. It doesn't occur under either 1.0.10 or 1.0.6, which are the other two versions I keep around to test things. It only occurs when *compiling* the unit. When *building* the unit, it compiles perfectly, but if I immediately try to compile after this, I get the same error again. I would post the unit on my website & make a link here, except it's tied in to quite a few others... any ideas?

Without sources we can't do anything