Discussion:
Errors in compilation
Leon Pollak
2017-06-21 13:27:33 UTC
Permalink
Hello, all.

I already reported this error with one of the older versions of the
Kdevelop.AppImage and it did not exist in the last versions.
But now, with the very last release it returned...:-(

ERROR: ld.so: object '/tmp/.mount_ahSRNO/exec_wrapper.so' from LD_PRELOAD
cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.

Is there any way to eliminate this somehow?
Thanks.
--
Leon
Sven Brauch
2017-06-21 15:42:07 UTC
Permalink
Do you run a 32-bit system ...?
Post by Leon Pollak
Hello, all.
I already reported this error with one of the older versions of the
Kdevelop.AppImage and it did not exist in the last versions.
But now, with the very last release it returned...:-(
ERROR: ld.so: object '/tmp/.mount_ahSRNO/exec_wrapper.so' from LD_PRELOAD
cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
Is there any way to eliminate this somehow?
Thanks.
Leon Pollak
2017-06-22 06:56:29 UTC
Permalink
Post by Sven Brauch
Do you run a 32-bit system ...?
I cross compile in 64-bit FC25 to 32-bit ARM.
Post by Sven Brauch
Post by Leon Pollak
Hello, all.
I already reported this error with one of the older versions of the
Kdevelop.AppImage and it did not exist in the last versions.
But now, with the very last release it returned...:-(
ERROR: ld.so: object '/tmp/.mount_ahSRNO/exec_wrapper.so' from LD_PRELOAD
cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
Is there any way to eliminate this somehow?
Thanks.
--
Leon
Sven Brauch
2017-06-22 07:14:31 UTC
Permalink
Post by Leon Pollak
Post by Sven Brauch
Do you run a 32-bit system ...?
I cross compile in 64-bit FC25 to 32-bit ARM.
Ah ok, I think running a 32-bit executable from the AppImage explains
it. That error is not fatal though, or is it?

Greetings,
Sven
Leon Pollak
2017-06-22 07:22:54 UTC
Permalink
Post by Sven Brauch
Post by Leon Pollak
Post by Sven Brauch
Do you run a 32-bit system ...?
I cross compile in 64-bit FC25 to 32-bit ARM.
Ah ok, I think running a 32-bit executable from the AppImage explains
it. That error is not fatal though, or is it?
No, no! Everything works.
Its just filling the build frame with a lot of messages and forces me to
scroll through them to check that there were no errors, which are hardly
noticed because of this flood....

BR
--
Leon
René J.V. Bertin
2017-06-22 07:44:15 UTC
Permalink
This post might be inappropriate. Click to display it.
Sven Brauch
2017-06-22 19:55:38 UTC
Permalink
Hi,
No, no! Everything works. Its just filling the build frame with a lot
of messages and forces me to scroll through them to check that there
were no errors, which are hardly noticed because of this flood....
Ah, alright. I guess we should ship a 32-bit version of this library.
Not sure if that'll make it actually work and not display the message
... I'll put it on my todo list.
This touches on something that I've noticed too, the build output
view is actually one of the least usable (or should I say sleek?)
features in KDevelop, IMHO. At the very least it could do with a
feature found in other IDEs allowing to filter out either the
(compiler) warnings or the errors (or both).
Patches welcome, but this is completely unrelated to this thread.

Greetings,
Sven

Loading...