Skip to content

Conversation

@PankhudiJ17
Copy link

@PankhudiJ17 PankhudiJ17 commented May 8, 2025

This pull request addresses build issues encountered on Power architecture with GCC-11, specifically related to the following components: pg_bitutils.c (PostgreSQL), m4, and BoringSSL. The fixes ensure better compatibility and successful compilation on Power systems using GCC-11.

Summary of Changes
1. Power Architecture Support – PostgreSQL Patch

A patch has been added to resolve a build error in pg_bitutils.c encountered specifically on Power architecture.
Patch location: //ml_metadata/third_party:postgresql.patch

2. GCC-11 Compatibility Fix – m4 Patch
Resolved the following compilation error in c-stack.c when building m4 with GCC-11:
error:
missing binary operator before token "(" #elif HAVE_LIBSIGSEGV && SIGSTKSZ < 16384

Upstream patch taken from Debian sources:
https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/m4/1.4.18-5ubuntu1/m4_1.4.18-5ubuntu1.debian.tar.xz
Patch location: ml_metadata/third_party:zetasql.patch

3. Boringssl Update for GCC-11
A build error was encountered with the previous version of BoringSSL on Power architecture using GCC-11.
The issue was resolved by upgrading the boringssl version.
Update location: WORKSPACE file

Purpose of this PR:
These changes are necessary to ensure successful builds of ml_metadata on Power architecture with GCC-11. They improve cross-platform compatibility and ensure smoother CI/CD integration for platforms using newer compilers.

@PankhudiJ17
Copy link
Author

@XinranTang Could you please review and merge this PR.

@PankhudiJ17 PankhudiJ17 changed the title [ppc64le] Fixed pg_bitutils.c build error for Power architecture. [ppc64le] Added GCC-11 and Power support May 19, 2025
@PankhudiJ17
Copy link
Author

@vkarampudi @XinranTang
Could you please review as I have added GCC-11 build support as well in this PR?

@alhad-deshpande
Copy link

@vkarampudi
Fixed pre-commit/post-commit CI issues. Can you please trigger a CI build?

@XinranTang
Can you please review/merge this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants