| View previous topic :: View next topic |
| Author |
Message |
Shadow_Fury
Apprentice
Joined: 20 Apr 2021
Posts: 196
Location: 11.435765792823453, 143.05926743686274
|
 Posted: Thu Oct 17, 2024 2:10 am Post subject: make fails emerge due to severe warnings [solved] |
 |
|
Fresh install of a system, trying to update world, and make fails to emerge:
emerge --info '=dev-build/make-4.4.1-r1::gentoo'
emerge -pqv '=dev-build/make-4.4.1-r1::gentoo':
| Code: |
[ebuild R ] dev-build/make-4.4.1-r1 USE="nls verify-sig* -doc -guile -static -test"
|
/var/tmp/portage/dev-build/make-4.4.1-r1/temp/build.log
this happens both when emerging the new (~4.4.1-r100) version, and rebuilding the stable 4.4.1-r1 version (seen in above logs).
in both cases, the package fails to install due to severe errors:
| Code: |
* src/main.c:872:11: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/main.c:874:16: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/main.c:876:16: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/main.c:878:16: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/main.c:1540:13: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/read.c:1902:30: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/read.c:1918:32: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/read.c:1925:25: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/read.c:1992:7: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/variable.c:411:47: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/variable.c:1142:33: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/variable.c:1146:29: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/variable.c:1153:33: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/variable.c:1166:37: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/variable.c:1194:34: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/variable.c:1251:7: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/variable.c:1254:12: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/variable.c:1421:21: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
* src/posixos.c:876:7: warning: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) [-Wstring-compare]
|
i could override these warnings but it seems wrong to do so, and that they shouldn't be occuring in a well maintained package like make
any help is appreciated
-S
Last edited by Shadow_Fury on Thu Oct 17, 2024 10:59 am; edited 1 time in total |
|
| Back to top |
|
 |
sam_
Developer
Joined: 14 Aug 2020
Posts: 2231
|
| Posted: Thu Oct 17, 2024 4:53 am Post subject: |
|
|
I suggest not using FEATURES=stricter. I don't think any developers use it and it would need to be reworked for suitability to actually abort before emerging a package just because of warnings. The list that we maintain for said warnings is for QA notices rather than intended to abort, it's some legacy leftover functionality we've not really tended to.
That said, if you want, feel free to report the issues upstream. |
|
| Back to top |
|
|
Shadow_Fury
Apprentice
Joined: 20 Apr 2021
Posts: 196
Location: 11.435765792823453, 143.05926743686274
|
| Posted: Thu Oct 17, 2024 10:59 am Post subject: |
|
|
| sam_ wrote: | I suggest not using FEATURES=stricter. I don't think any developers use it and it would need to be reworked for suitability to actually abort before emerging a package just because of warnings. The list that we maintain for said warnings is for QA notices rather than intended to abort, it's some legacy leftover functionality we've not really tended to.
That said, if you want, feel free to report the issues upstream. |
Thanks for letting me know. i initially enabled it because i wanted to build a hardened system, and the manpage says
| manpage wrote: | | Have portage react strongly to conditions that may conflict with system security provisions |
,
but if it's not actually tested all too much, then i'll turn it off.
it may be worth getting the manpage changed to reflect that the "stricter" option is primarily for developer use. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
