Make file wrongly attempts to set optimisation using lowercase o

[looopTools]

Problem/Opportunity

The Make line 100 wrongly use -o0 instead of -O0 to set optimisation level 0 when building to TARGET=linux.

This result in all file compiled with CC being named 0

Steps to reproduce

No response

Expected Behavior

Files compile with optimisation level 0

Actual Behavior

Files are named 0

Notes (Optional)

No response

[looopTools]

For some reason I cannot create a branch on this repository, so I have generate a patch for solving the issue.

From 35f0b9fbc5cea9e308f45bfb7eb81cf8a9979b88 Mon Sep 17 00:00:00 2001
From: Lars Kakavandi-Nielsen <lars@embras.dk>
Date: Wed, 22 Jul 2026 16:16:07 +0200
Subject: [PATCH] 256: Fixing using lower case o when setting optimisation
 level

  -o0 was replaced with -O0 to correctly set optimisation level.
  This issue only happens with build target LINUX
---
 Makefile | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Makefile b/Makefile
index 7d2a256..91bb4d1 100755
--- a/Makefile
+++ b/Makefile
@@ -96,8 +96,8 @@ COMPILER := $(if $(filter CPP,$(VARIANT)),$(CXX),$(CC))
 INC_DIRS += $(UT_CORE_DIR)/sysroot/usr/include
 UT_CONTROL_COMPILER := $(CC)
 else
-COMPILER := $(if $(filter CPP,$(VARIANT)),g++ -ggdb -o0 -Wall, gcc -ggdb -o0 -Wall)
-UT_CONTROL_COMPILER := gcc -ggdb -o0 -Wall
+COMPILER := $(if $(filter CPP,$(VARIANT)),g++ -ggdb -O0 -Wall, gcc -ggdb -O0 -Wall)
+UT_CONTROL_COMPILER := gcc -ggdb -O0 -Wall
 endif
 
 # Common object file setup
-- 
2.53.0

[Ulrond]

Thanks @looopTools — confirmed and raised as #258, applying your patch verbatim via git am so your authorship is preserved.

One clarification for the record: ut-core’s own compile and link rules all append their own -o $@ after $(COMPILER), and GCC lets the last -o win, so ut-core itself was not mis-naming objects — what it was silently losing is the intended -O0. The file literally named 0 comes from UT_CONTROL_COMPILER being handed to the ut-control sub-make as CC="gcc -ggdb -o0 -Wall", where commands without their own -o pick it up. Your fix is the right one either way; the ut-control side is rdkcentral/ut-control#131.