Misc/python-config.sh.in: ensure sed invocations only match beginning of strings

[peko]

BPO	22907
Files	0001-Misc-python-config.sh.in-ensure-sed-invocations-only.patch: patch fixing issue

^{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 2014-11-20.13:00:52.944>
labels = ['build']
title = 'Misc/python-config.sh.in: ensure sed invocations only match beginning of strings'
updated_at = <Date 2014-11-20.13:00:52.944>
user = 'https://bugs.python.org/peko'

bugs.python.org fields:

activity = <Date 2014-11-20.13:00:52.944>
actor = 'peko'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Cross-Build']
creation = <Date 2014-11-20.13:00:52.944>
creator = 'peko'
dependencies = []
files = ['37234']
hgrepos = []
issue_num = 22907
keywords = ['patch']
message_count = 1.0
messages = ['231427']
nosy_count = 1.0
nosy_names = ['peko']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue22907'
versions = ['Python 3.4']

[peko]

The build/real prefix handling using sed breaks if build != real and the
standard include / lib directories are used ($prefix/include and $prefix/lib).

E.G.

prefix_build="/usr", libdir="$prefix/lib", includedir="$prefix/include".

If this gets installed with make DESTDIR="/foo" install, then we end up with prefix_real = prefix = "/foo/usr" as expected, but
includedir="/foo/foo/usr/include" and libdir="/foo/foo/usr/lib" because of the double sed invocation (prefix is already expanded). Work around it by ensuring we only match the beginning of the string.

[vfazio]

Is this already resolved via 14086cf?