Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config.environ: always strip slash from SYSROOT (bug 654600) #317

Merged
merged 1 commit into from
May 3, 2018

Conversation

zmedico
Copy link
Member

@zmedico zmedico commented May 3, 2018

Since SYSROOT=/ interacts badly with autotools.eclass (bug 654600),
and no EAPI expects SYSROOT to have a trailing slash, always strip
the trailing slash from SYSROOT.

Bug: https://bugs.gentoo.org/654600
Fixes: a41dacf ("Export SYSROOT and ESYSROOT in ebuild env in EAPI 7")

@chewi

@zmedico zmedico force-pushed the bug_654600_empty_sysroot branch 2 times, most recently from 1685b13 to d2ac79d Compare May 3, 2018 01:02
@chewi
Copy link
Member

chewi commented May 3, 2018

Fair enough. @mgorny might want to add his 2¢ here as he added the stripping.

@mgorny
Copy link
Member

mgorny commented May 3, 2018

Well, I just wanted to have the conditions consistent. Given that there are no EAPIs that define SYSROOT and have trailing slash, it is not strictly necessary to do it conditionally.

Since SYSROOT=/ interacts badly with autotools.eclass (bug 654600),
and no EAPI expects SYSROOT to have a trailing slash, always strip
the trailing slash from SYSROOT.

Bug: https://bugs.gentoo.org/654600
Fixes: a41dacf ("Export SYSROOT and ESYSROOT in ebuild env in EAPI 7")
Reviewed-by: James Le Cuirot <chewi@gentoo.org>
Reviewed-by: Michał Górny <mgorny@gentoo.org>
Reviewed-by: Brian Dolbec <dolsen@gentoo.org>
@gentoo-bot gentoo-bot merged commit 1b51105 into gentoo:master May 3, 2018
@zmedico zmedico deleted the bug_654600_empty_sysroot branch May 3, 2018 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants