Hi Harald, I know it's a big problem, and working on the solution. This issue is a bit strange, 'cause the compiler should accept gcc 6.2.1 too, not just 6.2.0. Titan only checks the first two version numbers (major and minor), but the third level (change) is not important. I'm investigating this. Thanks again for the bug report!
BR, Gergely 2017-10-27 15:17 GMT+02:00 Harald Welte <[email protected]>: > Please note this bug also exist in stable/stretch. I'm not a BTS > expert, but is it possible to somehow flag a bug as being relevant to > multiple debian releases? If so, please mark this bug as such. If not, > I'm happy to file a separate bug against stretch. > > Right now, the eclipse-titan package in the debian archive for stretch > was built using gcc-6.2.0, but stretch actually has gcc-6.2.1 by now. > > So starting with a fresh stretch installation, you will run into this > exact same problem. Without the gross hack of manually patching the > include file, the eclipse-titan compiler is not usable. > > I am not a Debian expert, but I guess you will need to find out how you can > automatically trigger a re-build of eclipse-titan, every time a package > with a new gcc version is pushed into the debian archive. > > Probably only part of the solution: The eclipse-titan package should > depend on the specific gcc-version. So basically 'control' would list > a "Depends: gcc (= 6.2.0)" line to express this specific dependency > which is currently only in /usr/include/titan/cversion.h, but not in the > package metadata, where (I think) it belongs. > > Regards, > Harald > > -- > - Harald Welte <[email protected]> > http://laforge.gnumonks.org/ > ============================================================ > ================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. > A6) >
