Sign in Join

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

Mailing lists / fpc-devel / 2003-03

strange unit XLIB linking error

4 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

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

Mattias Gaertner

Hi,

I just updated my fpc 1.0.7 from cvs and then recompiled lazarus. I got the message

----------------------
Free Pascal Compiler version 1.0.7 [2003/03/07] for i386 Copyright (c) 1993-2003 by Florian Klaempfl
Target OS: Linux for i386
Compiling lazarus.pp
Assembling lazarus
lazarus.pp(302) Error: unit XLIB can't be smart or static linked Linking ./lazarus
make[1]: *** [lazarus] Error 1
make[1]: Leaving directory `/home/..../lazarus'
make: *** [ide] Error 2
----------------------

Adding the -XD switch I got the same but the line

lazarus.pp(302) Error: unit XLIB can't be shared or static linked

So, it seems that the current ppc386 can't link the unit XLIB in no way. Is there a mysterious, secret, fourth way of linking a unit? In any case it creates a working lazarus executable.

Mattias

Reply by email

Andrew Johnson
to Mattias Gaertner
Mattias Gaertner wrote 28 lines
Hi, I just updated my fpc 1.0.7 from cvs and then recompiled lazarus. I got the message ---------------------- Free Pascal Compiler version 1.0.7 [2003/03/07] for i386 Copyright (c) 1993-2003 by Florian Klaempfl Target OS: Linux for i386 Compiling lazarus.pp Assembling lazarus lazarus.pp(302) Error: unit XLIB can't be smart or static linked Linking ./lazarus make[1]: *** [lazarus] Error 1 make[1]: Leaving directory `/home/..../lazarus' make: *** [ide] Error 2 ---------------------- Adding the -XD switch I got the same but the line lazarus.pp(302) Error: unit XLIB can't be shared or static linked So, it seems that the current ppc386 can't link the unit XLIB in no way. Is there a mysterious, secret, fourth way of linking a unit? In any case it creates a working lazarus executable. Mattias

this has started happening for me too, including with other errors, I got this error while compiling a test program and got the same sort of error with gdkimlib, aka gdkimlib can't be smart or.. blah bah. I also get it with libgnome.

Andrew

Reply by email

Yakov Sudeikin
to Andrew Johnson

Hi fellow pascallers!

Can anyone introduce me into fpc source tree? How is the source organized where to look for what, any historical documents? I tried to find that info on the website no luck though. Guys, I am tired waiting for months for every small bug fixed and want to help you. This is more than a year as I am trying to compile my project with fpc11 finally it compiles but still crashes and with the speed you usually fix bugs that I submit, it will take another year or two :) YET! I am sure the bugs all are in about the same area (dynarrays, openarrays, overloading of stuff) and with some effort can be polished in a reasonable amount of time. If you do not want to guide me in compiling and building and hacking into sources I may create a set of tests but I think it will not help as much.

The readme or another file on the source directory says "read the fpc programer's manual before trying to work with the code and do any changes" but what is that mystical manual... where is that thing.

Thank you,
Yakov Sudeikin

Reply by email

Peter Vreman
to Yakov Sudeikin
you wrote 10 lines
Hi fellow pascallers! Can anyone introduce me into fpc source tree? How is the source organized where to look for what, any historical documents? I tried to find that info on the website no luck though. Guys, I am tired waiting for months for every small bug fixed and want to help you. This is more than a year as I am trying to compile my project with fpc11 finally it compiles but still crashes and with the speed you usually fix bugs that I submit, it will take another year or two :) YET! I am sure the bugs all are in about the same area (dynarrays, openarrays, overloading of stuff) and with some effort can

Starting with the dynarrays is the easiest, it's mostly RTL related. The openarrays is all compiler internal. And the overloading is one of the complex parts of the compiler and i do not recommend to start with that part.

be polished in a reasonable amount of time. If you do not want to guide me in compiling and building and hacking into sources I may create a set of tests but I think it will not help as much.

For regression tests see the fpc/tests/ subtree

The readme or another file on the source directory says "read the fpc programer's manual before trying to work with the code and do any changes" but what is that mystical manual... where is that thing.

The document fpc/docs/internal/comparch.tex describes the 1.0.x compiler. For the internals of the 1.1 compiler there is no document yet. But the generic ideas are still the same as in the 1.0.x compiler.

Peter

Reply by email