Ken Moffat wrote:
On Tue, Apr 28, 2015 at 06:48:30AM -0300, Fernando de Oliveira wrote:
So, I'll be using gcc-5 on new builds, and continuing to use 4.9.2
to update packages on 7.7.
Thanks, ĸen,
I'd updated gcc to 5, because thought it would not be acceptable to
update packages tagged gcc5 with gcc 4.9, and after your post, it seems
I was wrong.
Therefore, I'm going to downgrade gcc and will not be able to contribute
with the tags any more. :-(
What I wrote was perhaps ambiguous -
If I update a package version, e.g. for biber-2.0, I will build it
both on a 7.7 system, using gcc-4.9.2, and also on a newer system
built with gcc-5. And tag it for both.
The first priority for everybody should be to keep a working system.
Anybody who updates to gcc-5 in-place is likely to have problems,
particularly in C++.
As you say, my approach does reduce our ability to commit upgrades.
Perhaps there is a better way of doing this ?
Just use the gcc tag and delete the 7.7 tag. Until we do a complete rebuild of
BLFS using gcc5, the -dev book will be in an inconsistent state, but that's the
nature of -dev.
Personally, I am going to start a new build starting with the current lfs-svn
and continue to BLFS. I want to explore kf5/plasma, but even with Armin's help,
I've been unable to get it to work yet. I keep getting segfaults so I think a
fresh start is needed for me.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
