[Lazarus] Do FPC generates old EABI code?

2009-12-14 Thread Kjow
Hi all again, I think that I'm almost at the end of my path to make Lazarus able to build for arm-linux "graphical projects". It compiles and it seems to link right, I found all target libs I need (I grabbed most of these from sdk), but almost at the end I have this error: ... /home/kjow/lazarus

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-14 Thread Dariusz Mazur
Kjow pisze: Hi all again, I think that I'm almost at the end of my path to make Lazarus able to build for arm-linux "graphical projects". It compiles and it seems to link right, I found all target libs I need (I grabbed most of these from sdk), but almost at the end I have this error: ... /hom

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-14 Thread Kjow
2009/12/14 Dariusz Mazur : > did you compile FPC and libcross with the same binutils? > how you made crossppcarm ? > to read EABI version you may use > readelf -a ./linX11.so. I started from latest sources and compiled binutils, fpc and lazarus myselft in a fresh ubuntu installation, but target li

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-14 Thread Kjow
2009/12/14 Kjow : > I'm going to try! I don't understand... Now I forced to use as -meabi=5 , but there are still errors. I compiled Lazarus lcl, from the IDE. FPC uses the same binutils that Lazarus. Hint: Start of reading config file /home/kjow/.fpc.cfg Hint: Start of reading config file /etc/f

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-14 Thread Kjow
2009/12/14 Kjow : > I don't understand... Now I forced to use as -meabi=5 , but there are > still errors. I compiled Lazarus lcl, from the IDE. FPC uses the same > binutils that Lazarus. Ok... it seems that lazarus doesn't use my own binutils path. So I "tricked" original arm-linux-as to force -me

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-14 Thread darekm
> 2009/12/14 Kjow : >> I don't understand... Now I forced to use as -meabi=5 , but there are >> still errors. I compiled Lazarus lcl, from the IDE. FPC uses the same >> binutils that Lazarus. > > Ok... it seems that lazarus doesn't use my own binutils path. So I > "tricked" original arm-linux-as to

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-15 Thread Kjow
2009/12/15 : > Should be >   Target OS: Linux for ARMEL > > You have to recompile crosscompiller > Its not EABI (see my descuss with Jonas on fpc-devel) > > make crosssinstal OPT="-dFPC_ARMEL" ... This is the command that I used to make crosscompiler: sudo make crossinstall CPU_TARGET=arm OS

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-15 Thread Dariusz Mazur
Kjow pisze: 2009/12/15 : Should be Target OS: Linux for ARMEL You have to recompile crosscompiller Its not EABI (see my descuss with Jonas on fpc-devel) make crosssinstal OPT="-dFPC_ARMEL" ... This is the command that I used to make crosscompiler: sudo make crossinstall CPU_T

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-15 Thread Florian Klaempfl
Dariusz Mazur schrieb: > Kjow pisze: >> 2009/12/15 : >> >>> Should be >>> Target OS: Linux for ARMEL >>> >>> You have to recompile crosscompiller >>> Its not EABI (see my descuss with Jonas on fpc-devel) >>> >>> make crosssinstal OPT="-dFPC_ARMEL" ... >>> >> >> This is the command tha

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-15 Thread Kjow
2009/12/15 Florian Klaempfl : > Please, don't spread the nonsense of -CfSOFT -CaEABI, it's neither > needed nor desired. -dFPC_ARMEL is enough. Neither is -dFPC_ARMEL needed >  in CROSSOPT. It is only needed when the first arm compiler is built and > in this case OPT=-dFPC_ARMEL is enough. Hi! So

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-15 Thread Kjow
2009/12/15 Kjow : > sudo make crossinstall CPU_TARGET=arm OS_TARGET=linux > CROSSBINDIR=/home/kjow/lazarus/fpc/binutils/ OPT=-dFPC_ARMEL > INSTALL_PREFIX=/usr I rewrote "my guide" how to cross compile starting from sources, this is the result: http://forum.lazarus.freepascal.org/index.php/topic,8

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-15 Thread Dariusz Mazur
Florian Klaempfl pisze: Dariusz Mazur schrieb: Kjow pisze: 2009/12/15 : Should be Target OS: Linux for ARMEL You have to recompile crosscompiller Its not EABI (see my descuss with Jonas on fpc-devel) make crosssinstal OPT="-dFPC_ARMEL" ... This is the c

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-15 Thread Florian Klaempfl
Dariusz Mazur schrieb: > > I know too few to say to omit some options > Jonas say about: CROSSOPT="-dFPC_ARMEL This is not needed. > last time when I ask about reduction options everyone blame me > > > but how compiler know, that FPU is present or absent (-CfSOFT)? armel has by default no fp

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-15 Thread darekm
>> but how compiler know, that FPU is present or absent (-CfSOFT)? > > armel has by default no fpu or whatever. Thx > >> >> >>> needed nor desired. -dFPC_ARMEL is enough. Neither is -dFPC_ARMEL >>> needed >>> in CROSSOPT. It is only needed when the first arm compiler is built >>> and >>> in this

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-15 Thread Florian Klaempfl
dar...@emadar.com schrieb: > Can I ask: > What is difference between CPU_TARGET=arm (with -CaEABI) and armel > seems, that first not produce proper EABI code though it say it is > (readelf status) > its normal or bug or unexpected behaviour ? Undefined behaviour. readelf just checks the header of

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-15 Thread Kjow
2009/12/15 Florian Klaempfl : > Please, don't spread the nonsense of -CfSOFT -CaEABI, it's neither > needed nor desired. -dFPC_ARMEL is enough. Neither is -dFPC_ARMEL needed >  in CROSSOPT. It is only needed when the first arm compiler is built and > in this case OPT=-dFPC_ARMEL is enough. Thank y

Re: [Lazarus] Do FPC generates old EABI code?

2009-12-15 Thread Kjow
2009/12/15 : > Should be >   Target OS: Linux for ARMEL > > You have to recompile crosscompiller > Its not EABI (see my descuss with Jonas on fpc-devel) > > make crosssinstal OPT="-dFPC_ARMEL" ... Yes, now with the suggestions about OPT: sudo make crossinstall CPU_TARGET=arm OS_TARGET=linux