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

autoconfreconfigure timestamp -> restarting build #70

Closed
rhubert opened this issue Mar 13, 2025 · 1 comment · Fixed by #71
Closed

autoconfreconfigure timestamp -> restarting build #70

rhubert opened this issue Mar 13, 2025 · 1 comment · Fixed by #71

Comments

@rhubert
Copy link
Contributor

rhubert commented Mar 13, 2025

[End    387] NOTE: CHECKOUT  core::dbus-tgt - dev/src/core/dbus/1/workspace (initial checkout) 
[***** ****] WARN: Restart build due to wrongly predicted sources.

This is caused by autoreconf timestamping some files, e.g.: aminclude_static.am

# aminclude_static.am generated automatically by Autoconf                                                                                              
# from AX_AM_MACROS_STATIC on Wed Mar 12 18:12:03 UTC 2025

Where date is called in https://gitlab.freedesktop.org/dbus/dbus/-/blob/dbus-1.15.8/m4/ax_am_macros_static.m4?ref_type=tags#L36

I'm unsure how to handle this. For dbus it might be easy as from dbus-1.16 they dropped autotools, but there might be more like this?

Maybe a more generic solution would be to use libfaketime for autoreconf & friends?

Somehow working prototype: rhubert/basement@ab59ba5

@jkloetzke
Copy link
Member

Thanks for tracking this down.

I'm afraid the only safe option is to fix such error one-by-one. Using an absolute timestamp in libfaketime is even officially discouraged. It will probably break scripts and tools in interesting ways. I find the risk higher than tracking down such nuisances individually.

Having said that, I've prepared BobBuildTool/bob#623 to really halt the build on such error.

rhubert added a commit to rhubert/basement-gnu-linux that referenced this issue Mar 17, 2025
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 a pull request may close this issue.

2 participants