savannah-hackers
[Top][All Lists]
Advanced

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

[Savannah-hackers] Re: submission of GNU Development Chain for M16C - sa


From: Mathieu Roy
Subject: [Savannah-hackers] Re: submission of GNU Development Chain for M16C - savannah.gnu.org
Date: 15 Nov 2002 11:50:59 +0100
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

"Dr. Manuel Kessler" <address@hidden> a tapoté :

> On 15 Nov 2002, Mathieu Roy wrote:
> 
> > address@hidden said:
> >
> > > A package was submitted to savannah.gnu.org
> > > This mail was sent to address@hidden, address@hidden
> > >
> > > Manuel Kessler <address@hidden> described the package as follows:
> > > License: gpl
> > > Other License:
> > > Package: GNU Development Chain for M16C
> > > System name: m16c
> > > Type: GNU
> > >
> > > Description:
> > > M16C is a port of the GNU cross development tools to the Mitsubishi M16C 
> > > microcontrollers. Tools needed first are binutils and then gcc. gdb and 
> > > possibly sid are considered as well.
> > > A few first steps have been taken, but mostly infrastructure in binutils 
> > > so far. Some other people have already shown interest to participate.
> > >
> > > Other Software Required:
> > > As a port of GNU binutils and GCC of course these two packages are 
> > > required. I am inclined to use CGEN for the binutils port, but that is 
> > > not yet fixed in stone.
> > > Besides general configuration stuff as autoconf etc. that\'s it.
> >
> > Have you talked about it to GNU bintutils and GCC project members?
> >
> > It would be surely better if the support of this tools for M16C was
> > directly in GNU binutils and GCC.
> >
> >
> > Can you state about it?
> 
> I have asked at the mailing lists whether there is such a port already
> projected or even done, but got no response. Therefore I stated that I
> would start it, and got no response as well.
> 
> I agree that direct inclusion would be better, and that is definitely the
> final goal, but I think that it is more appropriate at this very early
> stage to keep it slightly more separate. IMO the port is difficult enough
> not to be bothered additionaly with the problems of hitting a moving
> target (ongoing binutils/gcc development).
> 
> Consequently I favour fixing binutils and gcc at the current releases and
> doing the port, and integrate into the then current mainline sources if it
> is working (at least somewhat).
> 
> This seems to be somewhat similar to the 68HC11/12 port, which started as
> a separate project and is now integrated into current binutils/gcc.
> 
> > You can resubmit your project with ease by copying
> > the big re-registration URL provided in the mail
> > you received  at submission
> 
> If you agree, can you just approve it as is, or do I have to resubmit
> anyway?

I agree but you'll have to resubmit anyway. We do not store
informations on the database of unsuccesfull registration.

Regards,

-- 
Mathieu Roy
 
 << Profile  << http://savannah.gnu.org/users/yeupou <<
 >> Homepage >> http://yeupou.coleumes.org           >>
 << GPG Key  << http://stock.coleumes.org/gpg        <<




reply via email to

[Prev in Thread] Current Thread [Next in Thread]