> From: Christopher Gregory <[email protected]> > To: [email protected] > Date: Wed, 06 Aug 2014 23:23:59 +1200 > Subject: [blfs-dev] When naming versions of gcc > > Hello, > > Would it be possible to please use a wild card for gcc versions? > > On the lame page it has: > > First, if you are using i686 and gcc-4.9.0, fix a compile problem: > > This signals that it is only for that version of gcc, which is not the > case as it also applies to 4.9.1. > > So if gcc-4.9.x was used this would be clear to people that it is for > the subsequent minor versions as well. >
But what if the issue is for just 4.9.0 and not 4.9.1, or for 4.9.0 & 4.9.1 and not 4.9.2 ? BLFS is usually tied to the gcc version in lfs: so you're really just basing such work - e.g. the lame compile - on a single version of gcc anyhow. Would you be auto-using an xml entity value for gcc-ver anyway? And anyway how would you know in advance that e.g. '4.9.x' would be true for all such x ? > It would also mean less overall work as the version would not need to be > changed in the descriptions section until the problem no longer occurs > due to the effected package being fixed upstream. > But as said, aren't you auto-using a variable-value for gcc-ver anyhow? > Regards, > > Christopher. > > -- -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
