Ticket #150 (new defect)

Opened 2 years ago

Last modified 2 years ago

Need arch-specific .sconf data

Reported by: dirk Assigned to: allenb
Priority: major Milestone: 2.0 Beta
Component: Build Version: 2.0
Keywords: variant Cc:
Completion:

Description

If there are differences in the installations for different architectures the .sconf_temp files/directories create problems (see FC5 buildbot), as the test is only done once and the cache data is shared. I'm also not sure if the options test code respects the necessary arch-specific compiler flags (e.g. -m32 for ia32 on x64).

My recommendation would be to remove the arch variants. It sounds like a nice idea, but IMHO is not worth the large amount of trouble it causes. Being able to do debug and non-debug in one call would be nice, but will probably run into the same problems at some point.

Change History

(in reply to: ↑ description ) 01/07/07 16:55:44 changed by allenb

Replying to dirk:

If there are differences in the installations for different architectures the .sconf_temp files/directories create problems (see FC5 buildbot), as the test is only done once and the cache data is shared. I'm also not sure if the options test code respects the necessary arch-specific compiler flags (e.g. -m32 for ia32 on x64).

Can you describe these problems further. I have not seen then before and I am not sure what you mean.

-A

01/09/07 12:47:00 changed by dirk

The .sconf_temp (or .sconf_temp_linux) dir is arch-independent, so any differences between archs cannot be reflected there (e.g. only having some libs installed for one arch).