Hi all!
Someone knows why, programs
compiled to ARM HF target have to be linked with libc to be displayed by
readelf -a as a ARM HF binary?
If the program isn't linked with libc, it's displayed as ARM soft float by
readelf. Someone have a explanation about this behavior? Should I report a
bug?
__
FPC 3.2 installed in FPCupdeluxe, with Lazarus trunk. NetBSD binary is
made but with such error in Laz window:
Compile Project, Mode: netbsd x64, OS: netbsd, Target:
builds/netbsd-x64-gtk2/cudatext: Success, Errors: 2
Error: /home/user/fpcupdeluxe/cross/bin/x86_64-netbsd/x86_64-netbsd-ld:
/ho
.
I seem to remember this was a bug in the Win64 SEH support that was
fixed later on, but I can't find the bug report.
It's still the case on current trunk at least on Win64.
Since it might be a bug, I'd like to search for all occurrences of such
combination in my projects.
How do I find it
Michael Van Canneyt schrieb am Mo., 24. Juni 2019,
09:30:
>
>
> On Sun, 23 Jun 2019, Sven Barth via fpc-pascal wrote:
>
> > - localhost:8080/metadata works
> > - localhost:8080/users returns "INVALID RESOURCE"
>
> Because it has rdoConnectionInURL set, and so you must do
>
On Sun, 23 Jun 2019, Sven Barth via fpc-pascal wrote:
- localhost:8080/metadata works
- localhost:8080/users returns "INVALID RESOURCE"
Because it has rdoConnectionInURL set, and so you must do
localhost:8080/expenses/users
Ahh! Hadn't seen that this option is active... Okay, then it
