Hi, On 2023-06-28 01:41, Guillem Jover wrote: > On Fri, 2023-06-16 at 11:19:21 +0200, Emanuele Rocca wrote: > > are written in > > Pascal. It seems that fpc just emits the wrong flags. As an example, > > here is the readelf output for the armhf version of cqrlog. Note that > > Tag_ABI_VFP_args is not set either. > > Oh, hmm, could you file a report for this (perhaps preferably > upstream)? (Or perhaps you did already? :)
Done, see https://gitlab.com/freepascal.org/fpc/source/-/issues/40374 and https://bugs.debian.org/1038868. > > astap > > astap-cli > > c-evo-dh-gtk2 > > c-evo-dh-stdai > > cqrlog > > doublecmd-gtk > > doublecmd-plugins > > doublecmd-qt > > el-ixir > > fp-compiler-3.2.2 > > fp-ide-3.2.2 > > fp-units-castle-game-engine > > fp-units-rtl-3.2.2 > > fp-utils-3.2.2 > > gearhead > > gearhead-sdl > > goverlay > > lazpaint-gtk2 > > lazpaint-qt5 > > mricron > > nbc > > pasdoc > > tomboy-ng > […] > > view3dscene > > winff-gtk2 > > winff-qt > > Hmm I guess these are going to be problematic for dpkg-shlibdeps when > trying to analyze these objects against the shared libraries they link > against. Once fpc is fixed, we could maybe rebuild all of the above? > > clisp-module-fastcgi_2.49.20210628.gitde01f0f-3_armhf.deb > > ./usr/lib/clisp-2.49.93+/fastcgi/fastcgi.o 0x5000000: Version5 EABI > > TAG_ABI_VFP_ARGS > > This seems like something to fix. > > > What do we want to do about those? I can take care of filing bug reports > > asking to add the missing flags if we agree it's a good idea. > > I guess it would be interesting to know whether this is due to these > having been built with old toolchains (and never been rebuilt since), > or there's some toolchain or build machinery issue at play or similar. Nope, I've rebuilt clisp on armhf and the flags are still wrong. I'll look into this further. > Otherwise it would be nice to get consistency here We'll get there! :)
