[Bug 824478] New: Review Request: msp430mcu - Headers and linker scripts for MSP430 micro-controllers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=824478

            Bug ID: 824478
        QA Contact: extras-qa@xxxxxxxxxxxxxxxxx
          Severity: medium
           Version: rawhide
          Priority: medium
                CC: notting@xxxxxxxxxx,
                    package-review@xxxxxxxxxxxxxxxxxxxxxxx
          Assignee: nobody@xxxxxxxxxxxxxxxxx
           Summary: Review Request: msp430mcu - Headers and linker scripts
                    for MSP430 micro-controllers
        Regression: ---
      Story Points: ---
    Classification: Fedora
                OS: Linux
          Reporter: rspanton@xxxxxxxxxx
              Type: ---
     Documentation: ---
          Hardware: All
        Mount Type: ---
            Status: NEW
         Component: Package Review
           Product: Fedora

Spec URL: http://users.ecs.soton.ac.uk/rds/rpm/mspgcc-uniarch/msp430mcu.spec
SRPM URL:
http://users.ecs.soton.ac.uk/rds/rpm/mspgcc-uniarch/msp430mcu-20120406-2.fc16.src.rpm
Description: Headers and linker scripts for the Texas Instruments MSP430 range
of
micro-controllers.  These headers provide the location of all the
special function registers of the micro-controllers.  The linker
scripts provide the mapping of those registers into memory as well as
information on where code should be loaded.

I'm in the process of updating the msp430 toolchain from the old gcc 3.x
situation that we were shipping to the considerably newer and more functional
gcc 4.x "uniarch" variant.  This upgrade involves a change in the way that the
headers and linker scripts for the msp430 are delivered.  Instead of them being
part of msp430-libc, they are now brought-in as a separate package called
"msp430mcu".  The new msp430-libc will depend on this package.

I considered whether this package needs to be a -devel package, and consulted
the fedora devel mailing list:
http://thread.gmane.org/gmane.linux.redhat.fedora.devel/164102  The general
conclusion is that it does not need to be since compiler toolchains are exempt
from the -devel package requirement.

rpmlint outputs 0 errors and warnings when run on the specfile.  When run on
the built package, it spits out a lot of warnings about headers not being in a
'-devel' package.  These should be ignored (see above).

A review would be very much appreciated.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review



[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]