This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: RDOS support for libstdc++-v3
- From: Bernardo Innocenti <bernie at develer dot com>
- To: Leif Ekblad <leif at rdos dot net>
- Cc: Andrew Pinski <pinskia at physics dot uc dot edu>, gcc-patches at gcc dot gnu dot org
- Date: Tue, 10 Jan 2006 12:00:48 +0100
- Subject: Re: PATCH: RDOS support for libstdc++-v3
- References: <200512300401.13275.bjoern.m.haase@web.de> <03c801c60d4e$09d85320$410aa8c0@codab.home> <03ef01c60d4f$f76385f0$410aa8c0@codab.home> <d912337b23d95d7903e7499e32a28d4a@physics.uc.edu> <00a901c60d6f$b9074470$0201a8c0@LEIFACER>
Leif Ekblad wrote:
>> Remove the initial / in the changelog.
>> configure is generated from configure.ac and other files.
>
> Why then is configure part of the source code?
It's a leftover from when specific (and, in some cases,
customized) versions of the auto tools were required to
build GCC. The requirements are now more relaxed.
I'd favour removing these from SVN and adding the usual
autogen.sh script like any other autoconf based project
does.
>> This part comes from libtool.
>
> Do you mean this file is identical in libstdc++-v3 and libtool and
> is maintained by libtool?
Before you can add rdos support to GCC, you may need to send patches
for the new platform to the maintainers of the "config" and "libtool"
projects. Both are hosted at Savannah:
http://savannah.gnu.org/projects/config/
http://savannah.gnu.org/projects/libtool/
When the patches are in, anyone may import a later version of the
upstream files in GCC's SVN repository.
>> Since you are using diff manually, you can add -N to the options
>> passed to it to get the diff to include the new files.
I believe posting new files as plaintext to help reviewers
was a common practice in GCC development.
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/