* Re: common/environment/build-style/go.sh: allow setting CGO_ENABLED
2022-12-18 16:31 [PR PATCH] common/environment/build-style/go.sh: allow setting CGO_ENABLED sug0
@ 2023-01-13 17:24 ` Vaelatern
2023-01-13 18:32 ` sug0
` (8 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Vaelatern @ 2023-01-13 17:24 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 153 bytes --]
New comment by Vaelatern on void-packages repository
https://github.com/void-linux/void-packages/pull/41167#issuecomment-1382164868
Comment:
Why `:-`?
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: common/environment/build-style/go.sh: allow setting CGO_ENABLED
2022-12-18 16:31 [PR PATCH] common/environment/build-style/go.sh: allow setting CGO_ENABLED sug0
2023-01-13 17:24 ` Vaelatern
@ 2023-01-13 18:32 ` sug0
2023-01-13 18:34 ` sug0
` (7 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: sug0 @ 2023-01-13 18:32 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 251 bytes --]
New comment by sug0 on void-packages repository
https://github.com/void-linux/void-packages/pull/41167#issuecomment-1382231328
Comment:
I found it the most practical way to maintain the old value, if `CGO_ENABLED` was not set in the env @Vaelatern
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: common/environment/build-style/go.sh: allow setting CGO_ENABLED
2022-12-18 16:31 [PR PATCH] common/environment/build-style/go.sh: allow setting CGO_ENABLED sug0
2023-01-13 17:24 ` Vaelatern
2023-01-13 18:32 ` sug0
@ 2023-01-13 18:34 ` sug0
2023-01-13 18:49 ` Vaelatern
` (6 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: sug0 @ 2023-01-13 18:34 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 307 bytes --]
New comment by sug0 on void-packages repository
https://github.com/void-linux/void-packages/pull/41167#issuecomment-1382231328
Comment:
I found it the most practical way to maintain the old value, if `CGO_ENABLED` was not set in the env
@Vaelatern is there any issue with using `${VAR:-$DEFAULT_VALUE}`?
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: common/environment/build-style/go.sh: allow setting CGO_ENABLED
2022-12-18 16:31 [PR PATCH] common/environment/build-style/go.sh: allow setting CGO_ENABLED sug0
` (2 preceding siblings ...)
2023-01-13 18:34 ` sug0
@ 2023-01-13 18:49 ` Vaelatern
2023-01-13 19:24 ` classabbyamp
` (5 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Vaelatern @ 2023-01-13 18:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 196 bytes --]
New comment by Vaelatern on void-packages repository
https://github.com/void-linux/void-packages/pull/41167#issuecomment-1382246575
Comment:
makes it look like you mean negative instead of `:=`
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: common/environment/build-style/go.sh: allow setting CGO_ENABLED
2022-12-18 16:31 [PR PATCH] common/environment/build-style/go.sh: allow setting CGO_ENABLED sug0
` (3 preceding siblings ...)
2023-01-13 18:49 ` Vaelatern
@ 2023-01-13 19:24 ` classabbyamp
2023-01-13 19:24 ` classabbyamp
` (4 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: classabbyamp @ 2023-01-13 19:24 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 310 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/41167#issuecomment-1382288543
Comment:
`:-` and `:=` do different things, `:-` wil substitute the default if null or unset, `:=` will assign the default if null or unset. which is the desired behaviour?
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: common/environment/build-style/go.sh: allow setting CGO_ENABLED
2022-12-18 16:31 [PR PATCH] common/environment/build-style/go.sh: allow setting CGO_ENABLED sug0
` (4 preceding siblings ...)
2023-01-13 19:24 ` classabbyamp
@ 2023-01-13 19:24 ` classabbyamp
2023-01-13 22:35 ` sug0
` (3 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: classabbyamp @ 2023-01-13 19:24 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/41167#issuecomment-1382288543
Comment:
`:-` and `:=` do different things, `:-` wil substitute the default if null or unset, `:=` will assign the default if null or unset. which is the desired behaviour?
> In all cases shown with "substitute", the expression is replaced with the value shown. In all cases shown with "assign", parameter is assigned that value, which also replaces the expression.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: common/environment/build-style/go.sh: allow setting CGO_ENABLED
2022-12-18 16:31 [PR PATCH] common/environment/build-style/go.sh: allow setting CGO_ENABLED sug0
` (5 preceding siblings ...)
2023-01-13 19:24 ` classabbyamp
@ 2023-01-13 22:35 ` sug0
2023-01-13 23:16 ` Vaelatern
` (2 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: sug0 @ 2023-01-13 22:35 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
New comment by sug0 on void-packages repository
https://github.com/void-linux/void-packages/pull/41167#issuecomment-1382486430
Comment:
`:-` seems like the best option here. `:=` will do two assignments, since `CGO_ENABLED` is set again and exported on the left. either way, both would work here. can you tell me which of the two you prefer?
> `:-` and `:=` do different things, `:-` wil substitute the default if null or unset, `:=` will assign the default if null or unset. which is the desired behaviour?
>
> > In all cases shown with "substitute", the expression is replaced with the value shown. In all cases shown with "assign", parameter is assigned that value, which also replaces the expression.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: common/environment/build-style/go.sh: allow setting CGO_ENABLED
2022-12-18 16:31 [PR PATCH] common/environment/build-style/go.sh: allow setting CGO_ENABLED sug0
` (6 preceding siblings ...)
2023-01-13 22:35 ` sug0
@ 2023-01-13 23:16 ` Vaelatern
2023-01-13 23:57 ` [PR PATCH] [Merged]: " classabbyamp
2023-01-14 13:07 ` sug0
9 siblings, 0 replies; 11+ messages in thread
From: Vaelatern @ 2023-01-13 23:16 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 195 bytes --]
New comment by Vaelatern on void-packages repository
https://github.com/void-linux/void-packages/pull/41167#issuecomment-1382576538
Comment:
@classabbyamp I'm ok either way, you want to merge?
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PR PATCH] [Merged]: common/environment/build-style/go.sh: allow setting CGO_ENABLED
2022-12-18 16:31 [PR PATCH] common/environment/build-style/go.sh: allow setting CGO_ENABLED sug0
` (7 preceding siblings ...)
2023-01-13 23:16 ` Vaelatern
@ 2023-01-13 23:57 ` classabbyamp
2023-01-14 13:07 ` sug0
9 siblings, 0 replies; 11+ messages in thread
From: classabbyamp @ 2023-01-13 23:57 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
There's a merged pull request on the void-packages repository
common/environment/build-style/go.sh: allow setting CGO_ENABLED
https://github.com/void-linux/void-packages/pull/41167
Description:
Change hard-coded value of `CGO_ENABLED` to allow reading a user configured value from a template file. This is required to fix a segmentation fault in #40919, derived from some kind of linking error. The default behavior is kept, i.e. cgo is still enabled by default, which shouldn't break any packages.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: common/environment/build-style/go.sh: allow setting CGO_ENABLED
2022-12-18 16:31 [PR PATCH] common/environment/build-style/go.sh: allow setting CGO_ENABLED sug0
` (8 preceding siblings ...)
2023-01-13 23:57 ` [PR PATCH] [Merged]: " classabbyamp
@ 2023-01-14 13:07 ` sug0
9 siblings, 0 replies; 11+ messages in thread
From: sug0 @ 2023-01-14 13:07 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 145 bytes --]
New comment by sug0 on void-packages repository
https://github.com/void-linux/void-packages/pull/41167#issuecomment-1382733786
Comment:
cheers
^ permalink raw reply [flat|nested] 11+ messages in thread