Skip to content

Enable rpath remapping in makefile #81218

Description

@zooba
BPO 37037
Nosy @Yhg1s, @ronaldoussoren, @ned-deily, @zooba

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 2019-05-24.16:48:42.360>
labels = ['type-feature', '3.8', '3.9', 'build']
title = 'Enable rpath remapping in makefile'
updated_at = <Date 2019-05-25.00:49:35.837>
user = 'https://github.com/zooba'

bugs.python.org fields:

activity = <Date 2019-05-25.00:49:35.837>
actor = 'ned.deily'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2019-05-24.16:48:42.360>
creator = 'steve.dower'
dependencies = []
files = []
hgrepos = []
issue_num = 37037
keywords = []
message_count = 2.0
messages = ['343411', '343447']
nosy_count = 4.0
nosy_names = ['twouters', 'ronaldoussoren', 'ned.deily', 'steve.dower']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue37037'
versions = ['Python 3.8', 'Python 3.9']

Linked PRs

Activity

  1. zooba commented on May 24, 2019

    @zooba
    MemberAuthor

    I'd like to be able to build libpython and have it already have the install path stripped out so I can use rpath instead. This libpython is going to be distributed with other applications.

    Right now, I'm running install_name_tool -id "@rpath/libpython3.7m.dylib" libpython3.7m.dylib as a post-build step, (and will then have to figure out what breaks next ;) )

    It's probably a simple makefile/autoconf update to add an option to run the necessary commands as part of build, but I can't figure it out myself. So I'm hoping someone can help or has already done it and wants to share.

  2. added
    buildThe build process and cross-build
    type-featureA feature request or enhancement
    on May 24, 2019
  3. ned-deily commented on May 25, 2019

    @ned-deily
    Member

    (Sorry, my original answer was great except it didn't actually work. Revisiting.)

  4. transferred this issue fromon Apr 10, 2022
  5. added 2 commits that reference this issue on Jan 28, 2026
  6. added a commit that references this issue on Feb 11, 2026
  7. added a commit that references this issue on May 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    3.8 (EOL)end of life3.9 (EOL)end of lifebuildThe build process and cross-buildtype-featureA feature request or enhancement

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions