Bug 900525 – dev-lang/ruby-3.3.6-r1 has implicit function declarations in configure logs (CLANG-17-SYSTEM)

• Product: Gentoo Linux
• Status: CONFIRMED ---

[Description Agostino Sarubbo 2023-03-09 12:40:29 UTC]

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: dev-lang/ruby-2.7.7 has implicit function declarations in configure logs (CLANG-17-SYSTEM).
Discovered on: amd64 (internal ref: hardened_tinderbox)

NOTE:
(CLANG-17-SYSTEM) in the summary means that the bug was found on a machine that runs clang-17 but this bug MAY or MAY NOT BE related to the new compiler
See also: https://bugs.gentoo.org/898488#c4.

[Comment 1 Agostino Sarubbo 2023-03-09 12:40:32 UTC]

Created attachment 856925 [details]
build.log

build log and emerge --info

[Comment 2 Agostino Sarubbo 2023-05-05 07:02:32 UTC]

ci has reproduced this issue with version 3.2.2-r2 - Updating summary.

[Comment 3 Sam James 2023-05-05 07:05:08 UTC]

 * QA Notice: Found the following implicit function declarations in configure logs:
 *   /var/tmp/portage/dev-lang/ruby-2.7.7/work/ruby-2.7.7/config.log:36487 - sigsetjmp
 * Check that no features were accidentally disabled.

I need to check this. It might be legit.

[Comment 4 Agostino Sarubbo 2023-06-17 11:45:46 UTC]

ci has reproduced this issue with version 3.2.2-r3 - Updating summary.

[Comment 5 Agostino Sarubbo 2023-07-09 09:02:04 UTC]

ci has reproduced this issue with version 3.2.2-r4 - Updating summary.

[Comment 6 Agostino Sarubbo 2023-12-20 08:29:37 UTC]

gcc14_tinderbox has reproduced this issue with version 3.2.2-r5 - Updating summary.

[Comment 7 Sam James 2023-12-20 08:31:19 UTC]

checking for __builtin_setjmp... yes with cast ((void **))
checking for _setjmpex as a macro or function... no
checking for _setjmp as a macro or function... yes
checking for sigsetjmp as a macro or function... no
checking for setjmp type... __builtin_setjmp\((void **)\)

I suspect it's fine but I still need to check.

[Comment 8 Agostino Sarubbo 2023-12-29 10:38:07 UTC]

gcc14_tinderbox has reproduced this issue with version 3.3.0 - Updating summary.

[Comment 9 Agostino Sarubbo 2024-01-20 11:49:42 UTC]

tinderbox_musl has reproduced this issue with version 3.3.0-r1 - Updating summary.

[Comment 10 Agostino Sarubbo 2024-02-10 14:26:47 UTC]

ci has reproduced this issue with version 3.3.0-r2 - Updating summary.

[Comment 11 Agostino Sarubbo 2024-04-24 06:38:49 UTC]

ci has reproduced this issue with version 3.3.1 - Updating summary.

[Comment 12 Agostino Sarubbo 2024-06-01 10:20:40 UTC]

ci has reproduced this issue with version 3.3.2 - Updating summary.

[Comment 13 Agostino Sarubbo 2024-06-21 11:04:52 UTC]

gcc14_tinderbox has reproduced this issue with version 3.3.3 - Updating summary.

[Comment 14 Agostino Sarubbo 2024-07-10 11:09:52 UTC]

ci has reproduced this issue with version 3.3.4 - Updating summary.

[Comment 15 Agostino Sarubbo 2024-07-29 07:13:54 UTC]

ci has reproduced this issue with version 3.3.4-r1 - Updating summary.

[Comment 16 Agostino Sarubbo 2024-09-11 17:20:41 UTC]

ci has reproduced this issue with version 3.3.5 - Updating summary.

[Comment 17 Andreas K. Hüttel 2024-11-02 20:03:59 UTC]

(In reply to Sam James from comment #7)
> checking for __builtin_setjmp... yes with cast ((void **))
> checking for _setjmpex as a macro or function... no
> checking for _setjmp as a macro or function... yes
> checking for sigsetjmp as a macro or function... no
> checking for setjmp type... __builtin_setjmp\((void **)\)
> 
> I suspect it's fine but I still need to check.

[Comment 18 Agostino Sarubbo 2024-11-05 07:57:49 UTC]

ci has reproduced this issue with version 3.3.6 - Updating summary.

[Comment 19 Agostino Sarubbo 2024-11-09 13:43:56 UTC]

ci has reproduced this issue with version 3.3.6-r1 - Updating summary.