lazarus on fedora 3 for x86_64

[cenzin]

I can't get lazarus compiled under fedora 3 for x86_64. it will give a lot of compilation errors regarding typecasting integers into pointer and enumerated types into pointer (which are 64 bit long in x86_64)

I downloaded the plataform independent version of the source code.  Is there any 64 bit compilation of fedora that works?

help!

[Vincent Snijders]

Recently, since 0.9.6 has been released, a lot of 64 bits fixes have been made to the lazarus code. You might want to try using cvs to download the latest source and compile that.

Since I don't know any lazarus developers with a 64 bits machine, I can't give you any guarantees.

[Anonymous]

Is there any problem with AMD64 + 32BitLinux OS ?

[cenzin]

I have been downloading the latest CVS of both FPC and Lazarus and it changes the error, but no building of the 64 bit version of lazarus under linux fedora 3 for x86_64.

Now it appears to be an internal error of the compiler:

"Internal error 200304302"

it appears while compiling the unit "eventcodetools.pas" in the component/codetools directory.

What can i do?

HELP

[Vincent Snijders]

Did you remove all existing .ppu and .o files (make clean) before?

[Anonymous]

Did you remove all existing .ppu and .o files (make clean) before?

Oh yes, i allways perform a "make clean all" sequence.  Still doesn't pass the eventcodetools.pas barrier!

[Vincent Snijders]

Could you try again and give an explicit path the compiler?

Code: [Select]

make PP=/path/to/your/ppcx64
Please gives the last couple of lines of the output.

[Anonymous]

OK, I tried what you suggest. it still explodes, here is the last output

Assembling extractproctool
eventcodetool.pas(223,6) Fatal: Internal error 200304302
make[2]: *** [allcodetoolunits.ppu] Error 1
make[2]: Leaving directory `/home/naranjo/freepascal/lazarus/components/codetools'
make[1]: *** [codetools_all] Error 2
make[1]: Leaving directory `/home/naranjo/freepascal/lazarus/components'
make: *** [components] Error 2


Hope that you can figure out what is going on.

[Vincent Snijders]

It is strange. This internal error occurred with fpc 1.9.8, but with yesterdays fpc 1.9.9 I successfully compiled lazarus.

what does ppx86_64 -id say?
what does which ppx86_64 say?
what is the top line of /path/to/fpc-source/logs/Changes.compiler?

[Marc]

Ehm... what sometimes work with internal errors is to make again, but without cleaning first (iow. continue the build)

[Anonymous]

I have been downloading the latest version of fpc from CVS. I assume that is the 1.9.9 in this case. I perform a make all and make install on the fpc tree but i haven't checked if the installed version is the latest one. i'll check and i'll let you guys know about it.

[Anonymous]

I finally manage to make the whole build. but when it comes to the make install it fail.  and if i run it appears for about 1/10 of a second and exits with  an error code related to some gtk+ invalid region thing.  I advance today but i'm still not there

[glober]

I finally manage to make the whole build. but when it comes to the make install it fail.  and if i run it appears for about 1/10 of a second and exits with  an error code related to some gtk+ invalid region thing.  I advance today but i'm still not there

I had problems running make install on the Daily Lazarus Snapshot (on Gentoo Linux). Make worked OK.  Figured out that Lazarus ran fine out of the unziped directory where I ran make, without make install.

[Anonymous]

No, i'm afraid not. iif i run it from there it still bomb after a fraction of a second. it gives you a message with a warning with a lack of environment variables, but it says that this will disable some features only.  after that.. pum.  During my quest for linking lazarus i installed some development libraries that might be inconsistent.  At some stage there was a library (i don't remember the name, something related to gnome) that was refusing to install via rpm because of a dependency problem and the only way i found to work was to put the switch --nodeps in the rpm command.  maybe it was there when i start screwing up things.

is there a list of libraries / versions i should check so i can be sure that everything on that side is not causing me trouble.  Still want to leave Windows but everytime i try to leave an irresistible force pull me back to bill's domain

HELP

[Marc]

1) usually forcing rpms to install when dependencies don't match is a source of problems (those dependencies aren't there for fun)

2) make sure you don't mix  32bit and 64bit libs when linking. You may want to edit your fpc.cfg so that the lib64 dirs are searched first

to get a list of libs used you  can try to run make OPT=-sh and look in the link.res file