[Bug 485416] Review Request: msp430-gcc - Cross compiling GNU GCC for the MSP430

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


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





--- Comment #8 from Robert Spanton <rspanton at zepler.net>  2009-02-28 14:44:10 EDT ---
Hi Ralf, 

Thanks.  The CFLAGS issue that you spotted fixes building against rawhide on
ppc64.  However, it doesn't fix building against F10:

http://koji.fedoraproject.org/koji/taskinfo?taskID=1208914

So, I can either lean towards rawhide here or F10.  Disabling the ppc64 build
will make both work, but there'll be no ppc64 in rawhide.  Once it's in CVS, I
can enable the ppc64 build for rawhide.  Does that sound like a sensible
strategy?

> b) Remove all the hack entirely and live with the warnings brp-strip issues
> However, you seem to be lucky, this seems possible in this case, because
> brp-strip etc. (at least on Fedora 10) are broken enough not to try corrupting
> your target's files.

Unfortunately this doesn't work.  The brp-strip stuff does touch the libgcc.a
file, resulting in an unusable compiler.

I had a look at hacking the brp-strip scripts up more, but I can't see the
problem with them.  The output of: 

rpm -ql msp430-gcc | while read f; do file $f | grep ELF | grep -v stripped;
done

All the host binaries are stripped successfully when the brp-strip hacking is
in place.

I've added your suggestions for the setup macro (I can't believe that one has
to read the RPM source to find out what those %setup parameters mean. 
Terrible!) and moved the man pages.

> Finally, I guess you know that gcc-3.2.3 is dead and discontinued for ca.
> 5 years - Not actually something I would want to maintain ;-)

Unfortunately, this is the situation with mspgcc.  Most of the mspgcc
development is focussed on 3.2.3.

Yes, this is a pain.  However, hopefully packaging it up and making it
available in a major distribution will help to breathe life into the project. 
Once people start using it, I think they'll begin to appreciate why using those
non-free compilers is an inferior option.

As I'm sure you're aware, it's mighty difficult to get started on GCC hacking. 
I don't really see how we can get out of this situation until that changes :-/

New files:
Spec file: http://users.ecs.soton.ac.uk/rds/rpm/mspgcc/msp430-gcc.spec
SRPM:
http://users.ecs.soton.ac.uk/rds/rpm/mspgcc/msp430-gcc-3.2.3-2.20090210cvs.fc10.src.rpm

Rob

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.