[RFC] Dos and don'ts while removing multilib

← All discussions

Project / Subsystem

gcc / gcc

Date

2026-05-01

Proposer

Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>

Source type

public_inbox

Consensus

Under Review

Sentiment

—/10

Technical tradeoffs

  • • Removing multilib support simplifies the build process but requires careful configuration to ensure libraries are installed in the correct directories.
  • • Maintaining the /usr/lib64 convention may require custom configuration beyond simply removing multilib macros.

All attributes

project
gcc
subsystem
gcc
patch_id
—
discussion_id
afR3U-92dz6eYpOm@li-819a89cc-2401-11b2-a85c-cca1ce6aa768.ibm.com
source_type
public_inbox
title
[RFC] Dos and don'ts while removing multilib
headline
Dos and don'ts while removing multilib
tldr
An RFC discusses how to properly remove multilib support for s390 after dropping 31-bit support, while maintaining library directory conventions.
proposer
Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>
consensus
Under Review
outcome
proposed
sentiment_score
—
technical_tradeoffs
  • • Removing multilib support simplifies the build process but requires careful configuration to ensure libraries are installed in the correct directories.
  • • Maintaining the /usr/lib64 convention may require custom configuration beyond simply removing multilib macros.
series_id
—
series_role
standalone
series_parts
[]
tags
  • • gcc
  • • s390
  • • multilib
  • • library paths
bugzilla_url
—
date
2026-05-01T00:00:00.000Z

[RFC] Dos and don'ts while removing multilib

Stefan Schulze Frielinghaus is preparing a patch to remove -m31 support for s390, which would make multilib obsolete. The author seeks guidance on how to remove multilib while preserving the convention of installing 64-bit libraries under /usr/lib64 instead of /usr/lib. Andreas Schwab notes that alpha-linux and ia64-linux place their libraries in /lib, even without multilib.