https://bugzilla.redhat.com/show_bug.cgi?id=1350884 --- Comment #49 from Brandon Nielsen <nielsenb@xxxxxxxxxxx> --- (In reply to Andy Mender from comment #48) > Apologies for the delay with this! > > I went through the various Packaging Guidelines and it doesn't seem like > there is anything against splitting the package into multiple SPEC files. > The only potential problem it introduces is that certain subpackages might > become uninstallable if the dependency is not available yet. On the plus > side, maybe when you split the SPEC, you'll notice a pattern that will let > you re-assemble everything into a single SPEC file again or you'll realize > it wouldn't work in a single SPEC. > At this point the only thing that I don't have working is the GDB check tests. I'll drill down on that next. If I can't get that working I'll look into splitting the package. Remember when I said I have enough disk space? Turns out I don't have that either... > > In the interim, it was suggested on the devel mailing list[0] that this could instead be built with the cross-gcc[1] and cross-binutils[2] packages. Doing this and having a useful (for embedded development) compiler at the end requires a matching newlib package, as is done for arm[3]. I've mocked all of this up, and while building it is super confusing, it does work. Would that be a better path forward? Do I run it up the flagpole on the devel mailing list? Somewhere else? > > I shortly revisited this bit. To my understanding, cross-gcc and > cross-binutils are meant for building OS kernels, not cross-compiling > regular userland software. However, following this example might be useful, > as suggested on the mailing list: > https://src.fedoraproject.org/rpms/arm-none-eabi-newlib/blob/master/f/arm- > none-eabi-newlib.spec > > However, that still requires the various -binutils, -gcc, etc. packages for > MSP430. That was my understanding as well, though it was noted it "shouldn't matter"[0]. Ultimately, even if I did get them working, it wouldn't match what TI ships and is discussed on the TI forums. [0] - https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/KRAG5KT3UTZTMLFT3O53STP2E3H33GXH/ -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
