Good point; in fact, it's probably not related to MSP430X ("relocation" just
signals that thought in my mind). Either way, it's on the queue (I've had a
Chronos sitting on my desk for the last three months that I haven't had a
chance to look at, so what you're doing could be very useful to me as well).
The warning in signal.h is from a previous maintainer, and I just need to
look again to confirm there's nothing wrong with what it's doing. Since
it's been working fine since January, I don't have much concern.
Peter
On Fri, Jun 4, 2010 at 12:32 PM, Paul F. Sehorne <[email protected]> wrote:
> Thank you, Peter.
>
> I notice you refer to the linking problem as MSP430X. Are the linking
> problem and the warning issued in signal.h related?
>
> Thanks,
> Paul
>
> On 6/3/2010 9:16 AM, Peter Bigot wrote:
> > I've been told before that the MSP430X patch set has never been
> integrated
> > into mspgcc4. That's on my list to get to, but it's probably between one
> > and four weeks out.
> >
> > Peter
> >
> > On Tue, Jun 1, 2010 at 10:36 PM,<[email protected]> wrote:
> >
> >
> >> I am using mspgcc4.
> >>
> >> The "warning: internal error: unsupported relocation error" are all
> >> related to pointer to functions (in my case), details below.
> >> I found mspgcc bug 5815 (fixed a few months ago). But it appears that
> >> this bug also exists in MSPGCC4_r4-20100210.
>
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit. See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Mspgcc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
