using STANDARD_BINDIR_PREFIX and overrdes

← All discussions

Project / Subsystem

gcc / gcc

Date

2026-05-28

Proposer

"James K. Lowden" <jklowden@schemamania.org>

Source type

public_inbox

Consensus

Proposed

Sentiment

—/10

View thread →

All attributes

project: gcc
subsystem: gcc
patch_id: —
discussion_id: 20260528185814.af0333e87a5f285ff4b91a25@schemamania.org
source_type: public_inbox
title: using STANDARD_BINDIR_PREFIX and overrdes
headline: Understanding STANDARD_BINDIR_PREFIX and -B overrides
tldr: A developer seeks to understand how the `-B` flag overrides `STANDARD_BINDIR_PREFIX` in GCC to correctly locate COBOL include files.
proposer: "James K. Lowden" <jklowden@schemamania.org>
consensus: Proposed
outcome: proposed
sentiment_score: —
technical_tradeoffs: []
series_id: —
series_role: standalone
series_parts: []
tags: []
url: https://inbox.sourceware.org/gcc/20260528185814.af0333e87a5f285ff4b91a25@schemamania.org
bugzilla_url: —
date: 2026-05-28T00:00:00.000Z

using STANDARD_BINDIR_PREFIX and overrdes

A developer is seeking clarification on how the -B flag interacts with STANDARD_BINDIR_PREFIX in GCC, specifically in the context of compiling COBOL. They want to understand how -B overrides the default search path for executables like cobol1 and how to propagate this information to the COBOL compiler to locate include files. This is important for ensuring that the COBOL compiler can find necessary include files similar to how C++ finds <algorithm>.