head	1.1;
access;
symbols
	pkgsrc-2026Q1:1.1.0.4
	pkgsrc-2026Q1-base:1.1
	pkgsrc-2025Q4:1.1.0.2
	pkgsrc-2025Q4-base:1.1;
locks; strict;
comment	@# @;


1.1
date	2025.12.15.03.37.01;	author maya;	state Exp;
branches;
next	;
commitid	wMH43XSXpfxYgsmG;


desc
@@


1.1
log
@bazel: hacky method of patching a file to fix build

We would prefer the distfile to include the patches, but since ryoon@@
is having trouble regenerating the distfile, introduce a workaround that
fixes the build issue for now.

Make sure the patch is also available in patches/, but it's not used.

PR pkg/59590
@
text
@--- bazel/build_defs.bzl.orig	2023-12-14 07:54:10.464989126 +0000
+++ bazel/build_defs.bzl
@@@@ -36,6 +36,8 @@@@ _DEFAULT_CPPOPTS.extend([
     # "-Wshorten-64-to-32",  # not in GCC (and my Kokoro images doesn't have Clang)
     "-Werror",
     "-Wno-long-long",
+    "-Wno-deprecated-copy",
+    "-Wno-deprecated-builtins",
 ])
 _DEFAULT_COPTS.extend([
     "-std=c99",
@@@@ -43,6 +45,7 @@@@ _DEFAULT_COPTS.extend([
     "-Werror=pedantic",
     "-Wall",
     "-Wstrict-prototypes",
+    "-Wno-gnu-offsetof-extensions", "-Wno-c23-extensions",
     # GCC (at least) emits spurious warnings for this that cannot be fixed
     # without introducing redundant initialization (with runtime cost):
     #   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80635
@