enable-new-dtags only for GNU ELF linker

Open
#61,564 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the linked 0004-ORIGIN-enable-new-dtags-only-for-GNU-ELF-linker.patch and the CPython build configuration associated with the Build component. Confirm where the enable-new-dtags option is selected and verify that it is restricted to the GNU ELF linker without affecting other linkers.

Written by the indexing model from the issue text.

Description

build
BPO 17362
Files
  • 0004-ORIGIN-enable-new-dtags-only-for-GNU-ELF-linker.patch
    		•

    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 2013-03-05.22:22:42.851>
labels = ['build']
title = 'enable-new-dtags only for GNU ELF linker'
updated_at = <Date 2019-04-26.19:58:40.339>
user = 'https://bugs.python.org/rpetrov'

    bugs.python.org fields:

    activity = <Date 2019-04-26.19:58:40.339>
actor = 'BreamoreBoy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2013-03-05.22:22:42.851>
creator = 'rpetrov'
dependencies = []
files = ['29317']
hgrepos = []
issue_num = 17362
keywords = ['patch']
message_count = 2.0
messages = ['183557', '223392']
nosy_count = 1.0
nosy_names = ['rpetrov']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'compile error'
url = 'https://bugs.python.org/issue17362'
versions = ['Python 3.4']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    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.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.