U++ forum: Welcome to the forum

Re: Strange build error only after changing [message #13818 is a reply to message #13812]

Tue, 29 January 2008 09:50

mr_ped
Messages: 826
Registered: November 2005
Location: Czech Republic - Praha

Experienced Contributor

Try to switch off blitz and/or "Build / Clean UPPOUT".
Depends which one you value more, the already built objects or usage of BLITZ. (I suggest to do both)

How did you do "clean", trough Upp build menu? Maybe some blitz files remain anyway so Clean UPPOUT is safer option (that deletes absolutely everything from build directory).

To me it looks like some .cpp file is compiled both individually and inside the big "blitz" file, so all of it's instantiated variables do get multiple definitions during linking.
It may be also problem with instantiating variables inside .h/.hpp files.

And finally I would check date/time of all source files, and current time on the machine, if they are bogus (future?) dates, it may cause havoc both to compiler itself and to blitz heuristic (at least so I think).

edit: And on multi-core CPU the multi threaded compilation may hit the problem with future dates too, there was some fix already between 2007.1 and current dev I think? Try to limit compilation to single thread (Setup/Environment/IDE/HYDRA 1 threads), if this helps, check the "changes" forum if you are using older UPP to see when there was some minor fix introduced.
(But I don't think this is the cause, as this one always did work when the compilation was invoked second time after first failure.)

[Updated on: Tue, 29 January 2008 09:54]

Report message to a moderator