On Mon, Oct 26, 2015 at 02:41:27PM -0400, Bart Oldeman wrote: > Just my 2 cents: > > This is really about a bootstrap procedure for what is presently > called the GNU/4.9.3-2.25 module (proposed to be just > GCC/4.9.3-binutils-2.25). I think one issue is now that this procedure > is user-exposed: > all the bits and pieces used in the bootstrap stay there by default, > and can be deleted once GNU/4.9.3-2.25 is done.
my 2 cents as a eb newbie: I would rather keep the build requirements pieces (in case some other tools needs them, later on, or if I want to rebuild GCC with some other compilers flags --optarch for instance) instead of deleting and re-doing them. But I would flag them as buildrequires/binutils/2.25 for instance. > > To have a binutils compiled with GCC 4.9.3 I think is elegant, and I > don't see a good reason NOT to do it. However it messes up the > dependency chain. > > In the end with: > > eb -r GCC-4.9.3-binutils-2.25.eb > > what I'd like to see is just one and only one user-visible module: > GCC/4.9.3-binutils-2.25 > (there may of course be extra files, such as for yacc IIRC). +1 Regards, Tru -- Dr Tru Huynh | http://www.pasteur.fr/research/bis mailto:[email protected] | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France
