Hi,

I have a funny problem with cvs -r FIXES_1_0_0: It does not link my project but do when compiling the compiler. I don't know, why, but there still is a bug:

In t_linux.pas (241): FileExists('/lib/ld-2.0.*');

This function allways return FALSE because of the wildcard. So even if a user just have installed glibc 2.0 fpc will think he has 2.1.

Back to the main problem: When I'm linking my project, the linker tells me, U_SYSTEM_* are not resolved while linking (from cprt21). I realy do not know, why. If I have just a test program like

uses
  sysutils;
begin
  writeln(fileexists('/lib/ld-2.1.*');
end.

everything works fine.

Next funny thing, when using FPC 1.1, everything is working fine as well.

Any hints?

Hinrich

Hinrich Donner wrote

Any hints?

As addition the verbose output of the linker attached.

Hinrich

The fileexists needs to be fixed, it'll take a look at it

You can't use the 1.1 RTL for the 1.0.x compiler as the system unit is renamed. The 1.1 RTL works with 1.0.x only to bootstrap a new compiler.

Peter

Hi Peter,

Peter Vreman wrote

>In t_linux.pas (241): FileExists('/lib/ld-2.0.*'); The fileexists needs to be fixed, it'll take a look at it

So you do mean that FileExists with wildcards has to work proper?

You can't use the 1.1 RTL for the 1.0.x compiler as the system unit is renamed. The 1.1 RTL works with 1.0.x only to bootstrap a new compiler.

I know, Peter. I removed the 1.1 completly because Jonas wrote me about the problem that integer constants are 64 bit in 1.1.

I have only compiled the 1.0.3 (cvs tree FIXES_1_0_0) with that units and with nothing is related to any other version.

The problem is still there.

Regards, Hinrich