Re: Unexpected messge with configure
Mats Wichmann <[email protected]>
| Newsgroups | gmane.comp.programming.tools.scons.user |
|---|---|
| Message-ID | <[email protected]> |
On 09/07/2018 12:15 PM, Jason Kenny wrote: > After a little more testing I see that it works correctly as is. GIven the values are cached it works basically as I suggested above. The message was unclear to me that if it was cached it would be ok. > Jason okay, I tried this out (sorry for following up to a message in the middle of a thread, rather than at the end). with a run in place so everything should be cached, I still can't dry-run: $ scons --dry-run scons: Reading SConscript files ... Processing using SCons version 3.0.1 Python 2.7.15 (default, May 15 2018, 15:37:31) [GCC 7.3.1 20180303 (Red Hat 7.3.1-5)] on linux2 scons: *** Cannot update configure test ".sconf_temp/conftest_0.c" within a dry-run. File "/home/mats/iotivity.work/build_common/iotivityconfig/compiler/factory.py", line 50, in check_for_gcc_c Should I assume that's a bug in our (homegrown) check, where the exception was thrown, that it's doing things that even cached results don't help? the file in question (that it can't update) is there and is a bog-standard "test for compiler type" stub of C code. _______________________________________________ Scons-users mailing list [email protected] https://pairlist4.pair.net/mailman/listinfo/scons-users