Bug#330125: comaintenance offer
Hakan Ardo wrote: On 11/8/05, Daniel Widenfalk <[EMAIL PROTECTED]> wrote: I have some questions to Hakan (mostly): *) During the build phase, the file template.tgz is created from binutils-TARGET and gdb-TARGET. I cannot see when the gcc-TARGET directory is used, or how to build the template-gcc.tgz archive. How, and where is this done? The gcc-TARGET dir is no longer used. template-gcc.tgz is instead built from a slightly modified version of the gcc source package. This has to be done manually before building the toolchain-source package as Build-Depends on source packages are nto possible. Check out the attached update_gcc.sh script. It is used to create template-gcc.tgz before the build. There is probably some pre 4.0 version of it in the source package. Note that a 4.0 template created this way don't work out of the box, some debugging and tweking is needed :) Nothing in life worth anything is easy :-) *) I've found multiple gcc-TARGET directories (./gcc-TARGET, and ./t/gcc-TARGET); which one is the right one? I think ./t/gcc-TARGET is an old checkout of gcc-3.4.3? In that case, why is it included in the source checkout? t is a temporary backup, it should be removed. gcc-TARGET is no longer used so it should probably be removed aswell. Sorry for the mess... Ok. I'll prune it when I get the rest going. *) I managed to grab gcc-4.0 after a bit of tweaking in /etc/apt/sources.list. I figure I should also get the relevant binutils, gdb and newlib sources? Well, the toolchain-source contains all those source codes, and they should be upgraded when newer versions is availible. There is a update.sh script that once did this. It might still work for binutils and gdb if you comment out the gcc stuff. But you don't have to update them att at once. Its probably better to take them one at the time until you get the hang of things. Maybe a good idea to start with upgrade the binutils or gdb sources, that should be quite straight forward, then move on to upgrading gcc, requires some tweeking and a lot of testting of for different targets. Check out test.sh it generates a set of corsscompilers, installs them and tries to compile some simple programs. newlib-support is not as important, but a nice feature once you get the rest working. Downloading the sources went well. However, all new source packages use the *.orig.tar.gz and *.diff.gz format. Shouldn't the update scripts take the diff archives into consideration as well? Doesn't the .orig tarball only contain the original upstream source and not the debian patches? /Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#330125: comaintenance offer
On 11/8/05, Daniel Widenfalk <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm sorry for the lengthy delay! I've been reading up on the Debian > Policy and the Developers Guide while trying to get a grip on the > toolchain-source package. A task not to be taken lightly! :-) > > I have some questions to Hakan (mostly): > > *) During the build phase, the file template.tgz is created from > binutils-TARGET and gdb-TARGET. I cannot see when the gcc-TARGET > directory is used, or how to build the template-gcc.tgz archive. > How, and where is this done? The gcc-TARGET dir is no longer used. template-gcc.tgz is instead built from a slightly modified version of the gcc source package. This has to be done manually before building the toolchain-source package as Build-Depends on source packages are nto possible. Check out the attached update_gcc.sh script. It is used to create template-gcc.tgz before the build. There is probably some pre 4.0 version of it in the source package. Note that a 4.0 template created this way don't work out of the box, some debugging and tweking is needed :) > > *) I've found multiple gcc-TARGET directories (./gcc-TARGET, and > ./t/gcc-TARGET); which one is the right one? I think > ./t/gcc-TARGET is an old checkout of gcc-3.4.3? In that case, > why is it included in the source checkout? t is a temporary backup, it should be removed. gcc-TARGET is no longer used so it should probably be removed aswell. Sorry for the mess... > > *) I managed to grab gcc-4.0 after a bit of tweaking in > /etc/apt/sources.list. I figure I should also get the relevant > binutils, gdb and newlib sources? Well, the toolchain-source contains all those source codes, and they should be upgraded when newer versions is availible. There is a update.sh script that once did this. It might still work for binutils and gdb if you comment out the gcc stuff. But you don't have to update them att at once. Its probably better to take them one at the time until you get the hang of things. Maybe a good idea to start with upgrade the binutils or gdb sources, that should be quite straight forward, then move on to upgrading gcc, requires some tweeking and a lot of testting of for different targets. Check out test.sh it generates a set of corsscompilers, installs them and tries to compile some simple programs. newlib-support is not as important, but a nice feature once you get the rest working. > > I appreciate your help and understanding in that I might stumble in > the beginning... By all means! > > Regards > /Daniel > > Hakan Ardo wrote: > > On 10/29/05, Aníbal Monsalve Salazar <[EMAIL PROTECTED]> wrote: > > > >>On Sat, Oct 29, 2005 at 10:20:03AM +0300, Martin-Éric Racine wrote: > >> > >>>Daniel: my experience of GCC development is non-existant but I am > >>>rather good at Debian packaging and I happen to need an updated set of > >>>cross-compilers. If you like, I could co-maintain this with you. > >>> > >>>Hakan: as you are experienced with this package, would you still want > >>>to remain onboard as a 3rd maintainer and as a sponsor for the uploads > >>>until Daniel and I have completed NM? > >> > >>Alternatively, I can sponsor the uploads. > > > > > > Great! My intention is to step down as maintainer of this package, and > > if the three of you are willing to comaintain it, thats just great! > > I'll be happy to help you get started by answering any questions > > though. > > > > > > > >>>-- > >>>Martin-Éric Racine > >>>http://q-funk.iki.fi > >> > >>Aníbal Monsalve Salazar > >>-- > >> .''`. Debian GNU/Linux > >>: :' : Free Operating System > >>`. `' http://debian.org/ > >> `- http://v7w.com/anibal > >> > >> > >>-BEGIN PGP SIGNATURE- > >>Version: GnuPG v1.4.2 (GNU/Linux) > >> > >>iD8DBQFDYyivgY5NIXPNpFURAjBaAJ9pHxsi8SmaRZdnH9TJ4tpco7LxvQCgkfKh > >>QJSP01/TEKw3bXTzUNNQUTQ= > >>=C08f > >>-END PGP SIGNATURE- > >> > >> > >> > > > > > > update_gcc.sh Description: Bourne shell script
Bug#330125: comaintenance offer
Hi all, I'm sorry for the lengthy delay! I've been reading up on the Debian Policy and the Developers Guide while trying to get a grip on the toolchain-source package. A task not to be taken lightly! :-) I have some questions to Hakan (mostly): *) During the build phase, the file template.tgz is created from binutils-TARGET and gdb-TARGET. I cannot see when the gcc-TARGET directory is used, or how to build the template-gcc.tgz archive. How, and where is this done? *) I've found multiple gcc-TARGET directories (./gcc-TARGET, and ./t/gcc-TARGET); which one is the right one? I think ./t/gcc-TARGET is an old checkout of gcc-3.4.3? In that case, why is it included in the source checkout? *) I managed to grab gcc-4.0 after a bit of tweaking in /etc/apt/sources.list. I figure I should also get the relevant binutils, gdb and newlib sources? I appreciate your help and understanding in that I might stumble in the beginning... Regards /Daniel Hakan Ardo wrote: On 10/29/05, Aníbal Monsalve Salazar <[EMAIL PROTECTED]> wrote: On Sat, Oct 29, 2005 at 10:20:03AM +0300, Martin-Éric Racine wrote: Daniel: my experience of GCC development is non-existant but I am rather good at Debian packaging and I happen to need an updated set of cross-compilers. If you like, I could co-maintain this with you. Hakan: as you are experienced with this package, would you still want to remain onboard as a 3rd maintainer and as a sponsor for the uploads until Daniel and I have completed NM? Alternatively, I can sponsor the uploads. Great! My intention is to step down as maintainer of this package, and if the three of you are willing to comaintain it, thats just great! I'll be happy to help you get started by answering any questions though. -- Martin-Éric Racine http://q-funk.iki.fi Aníbal Monsalve Salazar -- .''`. Debian GNU/Linux : :' : Free Operating System `. `' http://debian.org/ `- http://v7w.com/anibal -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDYyivgY5NIXPNpFURAjBaAJ9pHxsi8SmaRZdnH9TJ4tpco7LxvQCgkfKh QJSP01/TEKw3bXTzUNNQUTQ= =C08f -END PGP SIGNATURE-
Bug#330125: comaintenance offer
On 10/29/05, Aníbal Monsalve Salazar <[EMAIL PROTECTED]> wrote: > On Sat, Oct 29, 2005 at 10:20:03AM +0300, Martin-Éric Racine wrote: > >Daniel: my experience of GCC development is non-existant but I am > >rather good at Debian packaging and I happen to need an updated set of > >cross-compilers. If you like, I could co-maintain this with you. > > > >Hakan: as you are experienced with this package, would you still want > >to remain onboard as a 3rd maintainer and as a sponsor for the uploads > >until Daniel and I have completed NM? > > Alternatively, I can sponsor the uploads. Great! My intention is to step down as maintainer of this package, and if the three of you are willing to comaintain it, thats just great! I'll be happy to help you get started by answering any questions though. > > >-- > >Martin-Éric Racine > >http://q-funk.iki.fi > > Aníbal Monsalve Salazar > -- > .''`. Debian GNU/Linux > : :' : Free Operating System > `. `' http://debian.org/ > `- http://v7w.com/anibal > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.2 (GNU/Linux) > > iD8DBQFDYyivgY5NIXPNpFURAjBaAJ9pHxsi8SmaRZdnH9TJ4tpco7LxvQCgkfKh > QJSP01/TEKw3bXTzUNNQUTQ= > =C08f > -END PGP SIGNATURE- > > >
Bug#330125: comaintenance offer
Daniel: my experience of GCC development is non-existant but I am rather good at Debian packaging and I happen to need an updated set of cross-compilers. If you like, I could co-maintain this with you. Hakan: as you are experienced with this package, would you still want to remain onboard as a 3rd maintainer and as a sponsor for the uploads until Daniel and I have completed NM? -- Martin-Éric Racine http://q-funk.iki.fi signature.asc Description: This is a digitally signed message part
