-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests fail on 32-bit with _FILE_BITS=64 #2786
Comments
JuergenReppSIT
added a commit
to JuergenReppSIT/tpm2-tss
that referenced
this issue
Mar 18, 2024
Tests file the unit tests are compiled with _FILE_BITS is set to 64. The tests work without problems if _FILE_BITS is not set. Addresses: tpm2-software#2786 Signed-off-by: Juergen Repp <[email protected]>
JuergenReppSIT
added a commit
to JuergenReppSIT/tpm2-tss
that referenced
this issue
Mar 20, 2024
Tests file the unit tests are compiled with _FILE_BITS is set to 64. The tests work without problems if _FILE_BITS is not set. Addresses: tpm2-software#2786 Signed-off-by: Juergen Repp <[email protected]>
JuergenReppSIT
added a commit
to JuergenReppSIT/tpm2-tss
that referenced
this issue
Mar 20, 2024
Tests file the unit tests are compiled with _FILE_BITS is set to 64. The tests work without problems if _FILE_BITS is not set. Addresses: tpm2-software#2786 Signed-off-by: Juergen Repp <[email protected]>
AndreasFuchsTPM
pushed a commit
that referenced
this issue
Mar 21, 2024
Tests file the unit tests are compiled with _FILE_BITS is set to 64. The tests work without problems if _FILE_BITS is not set. Addresses: #2786 Signed-off-by: Juergen Repp <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When _FILE_BITS is set to 64, symbols like open get redirected (by glibc headers) to symbols like open64 and that means the interception/wrapping of those symbols done in the tests fail and so you get failures like this:
(excerpted from https://launchpadlibrarian.net/717964109/buildlog_ubuntu-noble-armhf.tpm2-tss_4.0.1-7.1ubuntu2_BUILDING.txt.gz)
Fixing this properly is probably quite annoying (it requires something like all this nonsense https://lore.kernel.org/all/[email protected]/).
The text was updated successfully, but these errors were encountered: