Michael Hope <michael.h...@linaro.org> wrote on 09/21/2010 11:44:14 PM:
> > As a related question, the generated files in a standard GDB 7.2 release > > seem to have been built on a relatively old system (RHEL 4 ?), which is > > visible through the versions of tools like bison, flex, texinfo, and > > gettext used to build those files. When building our Linaro GDB release > > tarballs, should we: > > - just use the tools as installed on a recent build system (say, Ubuntu > > Lucid), or > > - attempt to rebuild the release with the exact same set of tools used for > > the GDB 7.2 release? > > We should use the tools that come with Lucid. This does cause a > bigger diff but is easier to reproduce and less of a maintenance > problem. OK, sounds good. We'll need to make sure to test the final released tarball, to verify that there's no problem with those versions of generated files ... > I'm not happy with generated files being checked in, but we have to do > that to be drop-in replacement for the upstream GDB. > > If it's straight forward then I'd like to avoid checking in the > generated files if the change is only due to tool changes. We will > regenerate everything as part of the release process but it would be > nice to keep the branch clean. They'll not be checked into the branch; they'll be generated on the fly and simply become part of the tarballs. Mit freundlichen Gruessen / Best Regards Ulrich Weigand -- Dr. Ulrich Weigand | Phone: +49-7031/16-3727 STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E. IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht Stuttgart, HRB 243294 _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
