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.

Sign up for GitHub

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

Jump to bottom

gcc-config: Don't call portageq if the variable is already set #3

Closed
wants to merge 1 commit into from
Closed

gcc-config: Don't call portageq if the variable is already set #3

wants to merge 1 commit into from

Conversation

ulm
Copy link
Member

@ulm ulm commented May 14, 2023

@ulm
gcc-config: Don't call portageq if the variable is already set
2e77c38 
Bug: https://bugs.gentoo.org/906329
Acked-by: James Le Cuirot <chewi@gentoo.org>
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
@thesamesam
Copy link
Member

Could you check binutils-config as well while at it?

@ulm
Copy link
Member Author

ulm commented May 14, 2023

Could you check binutils-config as well while at it?

binutils-config should be fine:

	: ${HOST:=${CHOST:-$(portageq envvar CHOST)}}

@thesamesam
Copy link
Member

Thank you!

@ulm ulm deleted the portageq branch May 14, 2023 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@ulm @thesamesam