Wrong bitmap bit count

[clhamilto]

I’ve built Lazarus 4.0 QT6 on FreeBSD on PowerPC64(big endian).  When running the application I continuously get “Wrong bitmap bit count:  xxx”, where xxx is always a different number.  It makes the application unusable.

From what I’ve read this may be an endianness issue.

Any help/advice would be greatly appreciated.

[clhamilto]

I found this: https://forum.lazarus.freepascal.org/index.php/topic,64749.15.html

Could this be related to my issue?

[Thaddy]

No. Not likely because that is cross-platform.

[wp]

@clhamilto: why are you opening a new thread on the same topic and event with the same title? This will be very confusing to those reading the posts, and to those who want to answer - and to you because nobody knows which thread is the correct one.

[Thaddy]

Also, what we have seen in the other thread it is codetools that causes it.
Maybe that can be disabled in a Lazarus build for your PowerPC?
Codetools has many more bugs. (mostly because it lags behind features, not usually on endianness)
I concluded you have a working FPC - because the lazarus build process uses it - and a broken Lazarus because of codetools failing to compile.

And, indeed, as wp wrote, stick to a single thread for the same subject.

[clhamilto]

@clhamilto: why are you opening a new thread on the same topic and event with the same title? This will be very confusing to those reading the posts, and to those who want to answer - and to you because nobody knows which thread is the correct one.

I apologize but I opened this thread first and after several days with no response, I open the one under freepascal/unix, hoping to get a response there.

Also, what we have seen in the other thread it is codetools that causes it.
Maybe that can be disabled in a Lazarus build for your PowerPC?
Codetools has many more bugs. (mostly because it lags behind features, not usually on endianness)
I concluded you have a working FPC - because the lazarus build process uses it - and a broken Lazarus because of codetools failing to compile.

And, indeed, as wp wrote, stick to a single thread for the same subject.

Again I apologize for the dualing threads. Hence, based on your comment, I will only reply in this thread.