python / python/cpython

pkg-config file misses flags for static linking

Open
#77,619 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.7 (EOL) 3.8 (EOL) build type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 33438
Nosy @warsaw, @doko42, @pitrou

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2018-05-07.10:55:52.293>
labels = ['3.8', 'type-bug', '3.7', 'build']
title = 'pkg-config file misses flags for static linking'
updated_at = <Date 2018-05-07.12:14:11.893>
user = 'https://github.com/pitrou'

bugs.python.org fields:

activity = <Date 2018-05-07.12:14:11.893>
actor = 'pitrou'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2018-05-07.10:55:52.293>
creator = 'pitrou'
dependencies = []
files = []
hgrepos = []
issue_num = 33438
keywords = []
message_count = 4.0
messages = ['316258', '316259', '316260', '316263']
nosy_count = 3.0
nosy_names = ['barry', 'doko', 'pitrou']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue33438'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8']

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by locating the repository's pkg-config file and the build configuration that generates it, then inspect the static-linking output and related build flags. Done means the generated pkg-config data includes the flags required for static linking and the relevant build checks pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.