On Sat, Apr 21, 2012 at 3:30 AM, Matthias Ringwald <matth...@ringwald.ch> wrote: > Hi all > > sorry for the trouble. I've somehow (maybe it was too late..) imagined that > the patches are against some special already patched versions of the original > binutils, gcc, etc.. which is not the case.
Correct: mspgcc releases are always patches against the original upstream releases. In contrast, LTS bug-fix patches are generated from sources to which both the base mspgcc patches and any previous LTS patches were applied. Those are technically optional, might have to be combined with distribution-specific patches, and on the whole serve primarily as examples for downstream maintainers to use when applying fixes for upstream problems to distribution-specific packages. Most build systems I know of can simply add them (or reworked versions of them) to the full package build without significant pain. > I'm fine now and will update the fink package in the next days. Great; thanks. Peter > > Best > Matthias > > On 20.04.2012, at 23:06, Peter Bigot wrote: > >> On Fri, Apr 20, 2012 at 2:47 PM, Matthias Ringwald <matth...@ringwald.ch> >> wrote: >>> Hello Peter >>> >>> could you please provide a tar.gz of .. >>> >>>> >>>> The tag workspace/release/20120406 in >>>> git://mspgcc.git.sourceforge.net/gitroot/mspgcc/mspgcc checks out a >>>> workspace configured for this release. >>>> >>>> Downstream packagers: please use this version in subsequent distributions. >>> >>> on the mspgcc/files section where also the patches are located? >>> >>> Package managers that build from source (eg. fink) don't like/allow svn/git >>> checkouts, even if it's a tagged revision. >> >> I can't really do that: the workspace referred to is a skeleton >> directory structure that uses git submodules to fill out the >> contents---including all the upstream sources, with patches already >> applied. It'd be really huge if they were recursively exported. It's >> meant as a convenience for non-existent other developers who might >> want to do variant builds with debug flags or whatever. > .... > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
