Apache/2.4.7 (Ubuntu) Linux sman1baleendah 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 uid=33(www-data) gid=33(www-data) groups=33(www-data) safemode : OFF MySQL: ON | Perl: ON | cURL: OFF | WGet: ON > / usr / share / doc / gcc-4.9-base / | server ip : 172.67.156.115 your ip : 172.70.126.132 H O M E |
Filename | /usr/share/doc/gcc-4.9-base/TODO.Debian |
Size | 1.68 kb |
Permission | rw-r--r-- |
Owner | root : root |
Create time | 27-Apr-2025 09:50 |
Last modified | 08-Apr-2014 06:13 |
Last accessed | 07-Jul-2025 00:06 |
Actions | edit | rename | delete | download (gzip) |
View | text | code | image |
(It is recommended to edit this file with emacs' todoo mode)
Last updated: 2008-05-02
* General
- Clean up the sprawl of debian/rules. I'm sure there are neater
ways to do some of it; perhaps split it up into some more files?
Partly done.
- Make debian/rules control build the control file without unpacking
the sources or applying patches. Currently, it unpacks the sources,
patches them, creates the control file, and a subsequent
dpkg-buildpackage deletes the sources, re-unpacks them, and
re-patches them.
- Reorganise debian/rules.defs to decide which packages to build in a
more straightforward and less error-prone fashion: (1) start with
all languages; override the list of languages depending on the name
of the source package (gcc-4.3, gnat-4.3, gdc-4.3, gcj-4.3). (2)
filter the list of languages depending on the target platform; (3)
depending on the languages to build, decide on which libraries to
build.
o [Ludovic Brenta] Ada
- Done: Link the gnat tools with libgnat.so, instead of statically.
- Done: Build libgnatvsn containing parts of the compiler (version
string, etc.) under GNAT-Modified GPL. Link the gnat tools with it.
- Done: Build libgnatprj containing parts of the compiler (the project
manager) under pure GPL. Link the gnat tools with it.
- Done: Build both the zero-cost and setjump/longjump exceptions
versions of libgnat. In particular, gnat-glade (distributed systems)
works best with SJLJ.
- Done: Re-enable running the test suite.
- Add support for building cross-compilers.
- Add support for multilib (not yet supported upstream).
* Fortran
- gfortran man page generation
* Java
- build java-gcj-compat from the gcc source?
Last updated: 2008-05-02
* General
- Clean up the sprawl of debian/rules. I'm sure there are neater
ways to do some of it; perhaps split it up into some more files?
Partly done.
- Make debian/rules control build the control file without unpacking
the sources or applying patches. Currently, it unpacks the sources,
patches them, creates the control file, and a subsequent
dpkg-buildpackage deletes the sources, re-unpacks them, and
re-patches them.
- Reorganise debian/rules.defs to decide which packages to build in a
more straightforward and less error-prone fashion: (1) start with
all languages; override the list of languages depending on the name
of the source package (gcc-4.3, gnat-4.3, gdc-4.3, gcj-4.3). (2)
filter the list of languages depending on the target platform; (3)
depending on the languages to build, decide on which libraries to
build.
o [Ludovic Brenta] Ada
- Done: Link the gnat tools with libgnat.so, instead of statically.
- Done: Build libgnatvsn containing parts of the compiler (version
string, etc.) under GNAT-Modified GPL. Link the gnat tools with it.
- Done: Build libgnatprj containing parts of the compiler (the project
manager) under pure GPL. Link the gnat tools with it.
- Done: Build both the zero-cost and setjump/longjump exceptions
versions of libgnat. In particular, gnat-glade (distributed systems)
works best with SJLJ.
- Done: Re-enable running the test suite.
- Add support for building cross-compilers.
- Add support for multilib (not yet supported upstream).
* Fortran
- gfortran man page generation
* Java
- build java-gcj-compat from the gcc source?