On 2019-10-29 13:09:46 +0100, rene.engelh...@mailbox.org wrote: > Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre <vinc...@vinc17.net>: > >In case makefile magic triggers some rebuild, you can also run the > >generated executable directly (with the right environment variables, > >in case this matters). If the programs honors the system ABI, this > >is allowed, and you'll effectively test the new libstdc++6. > > No, if the rebuild rebuilds cppunittester or one of the > exceptionprotectors or the smoketest so or similar we are at the > same situation as with the autopkgtest (that's what it builds) and > are not sure whether it's g++-9 or libstdc++6. Neither LO nor the > test are an executable it's a executable with gazillions of .sos.
I meant running the generated program (smoketest) without rebuilding it: 1. Build smoketest with the old g++-9 / libstdc++6. 2. Upgrade g++-9 / libstdc++6. 3. Run smoketest directly. (I assume that the smoketest executable does not invoke g++-9 to rebuild things on the fly.) -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
