RE: [fpc-pascal] In EABI ARM rootdisk dynamic linker is not named ld-linux.so.2
> > Hi developer of freepascal (for arm) et all > > > > I have tried a freepascal program for arm EABI. I have created a > > ppcrossarm with SOFTFLOAT with binutils for EABI. > > Freepascal program compiled okey but When I run it in ARM board (with > > rootdisk EABI) I received a "FILE NOT FOUND" > > > > It was due that ld-linux.so is not ld-linux.so.2 but ld-linux.so.3 > (in > > order to allow libraries for OABI and EABI in the same rootdisk at > the > > same time). > > > > problem can be resolved with a symbolic link or patching in > > ./compiler/systems/t_linux.pas > > > > Simbolic link breaks possibility to allow libraries for OABI and EABI > > where place in same rootdisk running OABI program and EABI program at > > the same time. > > > > What is your opinion? (I'm very novice in EABI world so it's really > > possible I'm wrong) how does program detect to use dynamic linker > > ld-linux.so.2 or ld-linux.so.3? > > Should it be possible detect if fpc compiler has built with eabi > > toolschain or are using eabi toolchain to generate compiled programs? > > The dynamic loader the compiler depends on the libc you use. What libc > do you use? > libc-2.5 ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
RE: [fpc-pascal] In EABI ARM rootdisk dynamic linker is not named ld-linux.so.2
Op Fri, 6 Jul 2007, schreef josepascual: > > > Hi developer of freepascal (for arm) et all > > > > > > I have tried a freepascal program for arm EABI. I have created a > > > ppcrossarm with SOFTFLOAT with binutils for EABI. > > > Freepascal program compiled okey but When I run it in ARM board (with > > > rootdisk EABI) I received a "FILE NOT FOUND" > > > > > > It was due that ld-linux.so is not ld-linux.so.2 but ld-linux.so.3 > > (in > > > order to allow libraries for OABI and EABI in the same rootdisk at > > the > > > same time). > > > > > > problem can be resolved with a symbolic link or patching in > > > ./compiler/systems/t_linux.pas > > > > > > Simbolic link breaks possibility to allow libraries for OABI and EABI > > > where place in same rootdisk running OABI program and EABI program at > > > the same time. > > > > > > What is your opinion? (I'm very novice in EABI world so it's really > > > possible I'm wrong) how does program detect to use dynamic linker > > > ld-linux.so.2 or ld-linux.so.3? > > > Should it be possible detect if fpc compiler has built with eabi > > > toolschain or are using eabi toolchain to generate compiled programs? > > > > The dynamic loader the compiler depends on the libc you use. What libc > > do you use? > > > > libc-2.5 glibc-2.5 probably, but my SuSE 10.2 system contains glibc 2.5 and does use the normal ld-linux.so.2. We need to find out what is going here. Daniël___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Arm EABI vs OABI [was:DateToStr in arm does not work!]
En/na Marco van de Voort ha escrit: En/na Bernd Mueller ha escrit: I guess that fpc does not care about OABI/EABI. The compiler ether generates fpu opcodes or not (when floating point is used). This depends on the -CfSOFT option while building the compiler/rtl. Yes, but I think that fpc generates its own syscalls (not going through libc), and if I'm not mistaken, these are different in OABI vs EABI FPC can do both, but syscalls are default because these binaries are more portable across distributions (and versions) than glibc and thus easier to deploy. (and recently, libc has been broken after the introduction of the new syscalls. There is a release blocking bugentry for that in Mantis, so I expect that to be solved soon). But are they OABI or EABI under arm (or is there no difference?). Bye -- Luca ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
RE: [fpc-pascal] In EABI ARM rootdisk dynamic linker is not named ld-linux.so.2
> > > > Hi developer of freepascal (for arm) et all > > > > > > > > I have tried a freepascal program for arm EABI. I have created a > > > > ppcrossarm with SOFTFLOAT with binutils for EABI. > > > > Freepascal program compiled okey but When I run it in ARM board > > > > (with rootdisk EABI) I received a "FILE NOT FOUND" > > > > > > > > It was due that ld-linux.so is not ld-linux.so.2 but ld- > linux.so.3 > > > (in > > > > order to allow libraries for OABI and EABI in the same rootdisk > at > > > the > > > > same time). > > > > > > > > problem can be resolved with a symbolic link or patching in > > > > ./compiler/systems/t_linux.pas > > > > > > > > Simbolic link breaks possibility to allow libraries for OABI and > > > > EABI where place in same rootdisk running OABI program and EABI > > > > program at the same time. > > > > > > > > What is your opinion? (I'm very novice in EABI world so it's > > > > really possible I'm wrong) how does program detect to use dynamic > > > > linker > > > > ld-linux.so.2 or ld-linux.so.3? > > > > Should it be possible detect if fpc compiler has built with eabi > > > > toolschain or are using eabi toolchain to generate compiled > programs? > > > > > > The dynamic loader the compiler depends on the libc you use. What > > > libc do you use? > > > > > > > libc-2.5 > > glibc-2.5 probably, but my SuSE 10.2 system contains glibc 2.5 and does > use the normal ld-linux.so.2. We need to find out what is going here. yes, glibc-2.5, your SuSE is glibc-2.5 also but you are a i386 ARCH and I'm in an ARM ARCH with EABI. Jose Pascual. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
