Re: [gentoo-user] emerge world looking grim

2015-08-24 Thread Rich Freeman
On Sun, Aug 23, 2015 at 10:19 PM, Harry Putnam rea...@newsguy.com wrote:
 Can anyone advise me which iso to use?  And which profile to set for
 general use in a vbox, hopefully to allow a `no sweat' emerge to a
 full OS.

As others have pointed out you probably just need to update your gcc
and all will be well, or if you have it updated check gcc-config -l to
make sure you're using the latest version.

However, I did want to point out something else.  Gentoo isos don't
actually contain any packages.  They're nothing more than boot disks.
You can install Gentoo from an Ubuntu iso as easily as from a Gentoo
iso, and the Gentoo isos don't even boot on EFI.  The software is all
in the stage3.  However, I wouldn't really try to overwrite your
install with a stage3 at this point as it doesn't actually look like
you have any serious problems.  You  just need to do a bit of
housecleaning.

And a note to everybody else on the list:  take it easy on the poor
guy.  People used to other distros are used to doing things like
blowing away their installs every other year with a fresh install.
Release-based distros get people used to this kind of nonsense, and
the idea that FOSS comes on a shiny DVD.  Portage's error messages
don't always help in this regard.  Of course any Gentoo user has to be
willing to take the time to learn some of the nuts and bolts to keep
things running, but when it is obvious somebody doesn't understand
what they're doing we can educate rather than just point it out.

-- 
Rich



Re: [gentoo-user] emerge world looking grim

2015-08-24 Thread Alan Mackenzie
Hello, Harry,

Long time, no see!

On Sun, Aug 23, 2015 at 10:19:42PM -0400, Harry Putnam wrote:
 My gentoo OS is running on Openindiana (solaris) inside oracle's vbox.

 It's been left setting for at least 4-5 months maybe a couple more.

 After eix-sync, attempting an `emerge vuND world' comes up with so
 many blocks, use flag changes and a variety of other bad news in
 such proliferation... I'm thinking better to install from scratch with
 latest ISO.

I know the feeling.  When the same thing happened to me (my system got
into a mess because I was running XFCE which was too dependent on
gnome-2; when gnome-3 became stable, the demons of hades were let
loose, and I tried a couple of times, half-heartedly, to update), I told
myself to stop and think.

I could spend days fighting with use flags and conflicts, or I could
spend a few days reinstalling.  In the end I reinstalled (using the old
system (rather than an ISO image) to do the initial stages.  It took me
about a week, compared with about a month the first time I seriously
installed Gentoo.  Installation here means getting everything up and
running, including X with destop manager, printing, sound, email server
and client, 

 ,
 | NOTE: The full mess can be viewed here:
 | 
 | zeus.jtan.com/~reader/vutxt/images/emerge_MassiveFailure-150823.txt
 `

 I've been quite a long time gentoo user but last 2+ yrs only very
 lightly.

 I'm awful dumb for someone who has problably more than 15 yrs running
 gentoo.

I doubt that!  But if I were only using Gentoo lightly for an extended
period, I'd forget a _lot_.

 I wondered if there are some very new ISO's that would contain all
 major changes in last year or so once I got the core installed and key
 useflags/make.conf setup?

That's not the way Gentoo works - (what was that I was saying about
forgetting things?).  The Gentoo ISO is really just an installation
environment to boot up into, one with enough power for you to be able to
download and install a stage 3 into which you reboot, then really get
going with configuring the system, and installing further stuff, etc.
All the new stuff from the last few months is in portage (which you get
with $ emerge --sync, and so on).

 Can anyone advise me which iso to use?  And which profile to set for
 general use in a vbox, hopefully to allow a `no sweat' emerge to a
 full OS.

Painful though it might seem, I'd suggest you go back to the Gentoo
handbook and do a bit of revision.  It's been moved to the Gentoo wiki
at https://wiki.gentoo.org/wiki/Handbook:Main_Page.

I'd recommend you then just to reinstall.  Remembering my fights with
stupid error messages from emerge, and so on, I wish I'd just
reinstalled months earlier than I did.

Whatever you end up doing, all the best!

-- 
Alan Mackenzie (Nuremberg, Germany).



Re: [gentoo-user] emerge world looking grim

2015-08-24 Thread Alec Ten Harmsel
On Mon, Aug 24, 2015 at 08:41:48AM -0400, Rich Freeman wrote:
 And a note to everybody else on the list:  take it easy on the poor
 guy.  People used to other distros are used to doing things like
 blowing away their installs every other year with a fresh install.
 Release-based distros get people used to this kind of nonsense, and
 the idea that FOSS comes on a shiny DVD.  Portage's error messages
 don't always help in this regard.  Of course any Gentoo user has to be
 willing to take the time to learn some of the nuts and bolts to keep
 things running, but when it is obvious somebody doesn't understand
 what they're doing we can educate rather than just point it out.

That's fine, we could all be a bit nicer. That said, if someone wants a
distro that is fast and easy to install (which is perfectly valid to
want; I use plenty of them on a daily basis), it is important to point
out that Gentoo is neither fast nor extremely easy to install.

Alec



Re: [gentoo-user] emerge world looking grim

2015-08-24 Thread Alan McKinnon
On 24/08/2015 15:17, Alan Mackenzie wrote:
 Hello, Harry,
 
 Long time, no see!
 
 On Sun, Aug 23, 2015 at 10:19:42PM -0400, Harry Putnam wrote:
 My gentoo OS is running on Openindiana (solaris) inside oracle's vbox.
 
 It's been left setting for at least 4-5 months maybe a couple more.
 
 After eix-sync, attempting an `emerge vuND world' comes up with so
 many blocks, use flag changes and a variety of other bad news in
 such proliferation... I'm thinking better to install from scratch with
 latest ISO.
 
 I know the feeling.  When the same thing happened to me (my system got
 into a mess because I was running XFCE which was too dependent on
 gnome-2; when gnome-3 became stable, the demons of hades were let
 loose, and I tried a couple of times, half-heartedly, to update), I told
 myself to stop and think.
 
 I could spend days fighting with use flags and conflicts, or I could
 spend a few days reinstalling.  In the end I reinstalled (using the old
 system (rather than an ISO image) to do the initial stages.  It took me
 about a week, compared with about a month the first time I seriously
 installed Gentoo.  Installation here means getting everything up and
 running, including X with destop manager, printing, sound, email server
 and client, 


At first glance it does look like maybe a reinstall would be better. But
in this case, that's not true. Looking over the list of packages to be
updated, there are 3 general classes of things:

1. Regular updates
2. A whole whack of rebuilds
3. A perl upgrade from 5.20 to 5.22

#1 is routine. Press enter, and make does it's thing
#2 looks scary, but in the old days we'd have to do the updates then let
revdep-rebuild catch the inconsistencies, and rebuild those. Modern
portage has some magic code to fold everything into the main emerge
world step. So just press Enter and make does it's thing
#3 can be very confusing. With 5.22, upstream moved many Perl packages
into the core Perl codebase, so all such installed packages (and all of
us have many of them) need to uninstall perl-core/package and replace
it with virtual/perl-package. Portage normally deals with this
transparently, but the output can be a little too verbose sometimes, and
takes some decent brainpower to figure out what is really going on.

There's also some blockers in that list ([blocks b  ]), but they are all
soft (lower case b) so portage should take those in it's stride and just
fix it with no intervention.


Harry's real problem as many have noted is that his gcc config is not
valid. But, portage can't tell him that. It started the merge, and
handed control over to the next app, which portage can't make sense of
as it all happened outside portage's control. Result: a wall of text on
the screen, right after the wall of text of 195 things to be rebuilt and
a huge list of stuff causing other stuff to be needed to be rebuilt!

I suppose those ebuilds that are sensitive to gcc versions could have a
check built in to check the version before starting and then print a
sane error message that portage CAN control and make sense of.

Either way, gcc-config -l is what Harry needs to run first, and make
his default compiler 4.7 or later. With that out of the way, emerge
should proceed normally apart from taking a while to get through it. He
might have perl issues afterwards and need to run perl-cleaner.

The real problem is how do I know all this, and Harry did spot it? Well,
building a source distro comes in at a much lower level than a binary
one, and it does take a good large dose of experience, knowledge and
plain old luck to figure out what is really going on. These days portage
is very good at doing the right thing (it still sucks at a human level
in it's output...) and today Harry just got really unlucky.

So yeah, reinstall is probably not the better option here.


-- 
Alan McKinnon
alan.mckin...@gmail.com




Re: [gentoo-user] emerge world looking grim

2015-08-24 Thread Alec Ten Harmsel
On Sun, Aug 23, 2015 at 10:19:42PM -0400, Harry Putnam wrote:
 My gentoo OS is running on Openindiana (solaris) inside oracle's vbox.
 
 It's been left setting for at least 4-5 months maybe a couple more.
 
 After eix-sync, attempting an `emerge vuND world' comes up with so
 many blocks, use flag changes and a variety of other bad news in
 such proliferation... I'm thinking better to install from scratch with
 latest ISO.

 ,
 | NOTE: The full mess can be viewed here:
 | 
 | zeus.jtan.com/~reader/vutxt/images/emerge_MassiveFailure-150823.txt
 `

No, this really shouldn't be that bad. Look at the list of updates and
apply certain updates first. glibc and gcc should probably be updated
first, so just run:

emerge -uDN1 glibc

Since gcc-config could not find gcc 4.7, it is marked as stable, and
emerge was not trying to install it, you must have a version hard-coded
in `/var/lib/portage/world`. For now, to upgrade gcc you can just grab
the newest version:

emerge --oneshot gcc

From then on, it should go relatively smoothly, since emerge was
handling all of the blockers.

 Can anyone advise me which iso to use?  And which profile to set for
 general use in a vbox, hopefully to allow a `no sweat' emerge to a
 full OS.

As Jc Garcia mentioned, Gentoo is not a `no sweat' distro.

Alec



[gentoo-user] emerge world looking grim

2015-08-23 Thread Harry Putnam
My gentoo OS is running on Openindiana (solaris) inside oracle's vbox.

It's been left setting for at least 4-5 months maybe a couple more.

After eix-sync, attempting an `emerge vuND world' comes up with so
many blocks, use flag changes and a variety of other bad news in
such proliferation... I'm thinking better to install from scratch with
latest ISO.

,
| NOTE: The full mess can be viewed here:
| 
| zeus.jtan.com/~reader/vutxt/images/emerge_MassiveFailure-150823.txt
`

I've been quite a long time gentoo user but last 2+ yrs only very
lightly.

I'm awful dumb for someone who has problably more than 15 yrs running
gentoo.

I wondered if there are some very new ISO's that would contain all
major changes in last year or so once I got the core installed and key
useflags/make.conf setup?

Can anyone advise me which iso to use?  And which profile to set for
general use in a vbox, hopefully to allow a `no sweat' emerge to a
full OS.




Re: [gentoo-user] emerge world looking grim

2015-08-23 Thread Jc GarcĂ­a
2015-08-23 20:19 GMT-06:00 Harry Putnam rea...@newsguy.com:
 My gentoo OS is running on Openindiana (solaris) inside oracle's vbox.


Why so much overhead for compiling, and not doing it bare-metal?

 It's been left setting for at least 4-5 months maybe a couple more.

 After eix-sync, attempting an `emerge vuND world' comes up with so
 many blocks, use flag changes and a variety of other bad news in
 such proliferation... I'm thinking better to install from scratch with
 latest ISO.


Did you really took your time to read that error message, You are
seeing problems, except where they are.

 ,
 | NOTE: The full mess can be viewed here:
 |
 | zeus.jtan.com/~reader/vutxt/images/emerge_MassiveFailure-150823.txt
 `

 I've been quite a long time gentoo user but last 2+ yrs only very
 lightly.

 I'm awful dumb for someone who has problably more than 15 yrs running
 gentoo.

Considering gentoo doesn't even have 15 years, I guess you are talking
to us from the future.

 I wondered if there are some very new ISO's that would contain all
 major changes in last year or so once I got the core installed and key
 useflags/make.conf setup?

 Can anyone advise me which iso to use?  And which profile to set for
 general use in a vbox, hopefully to allow a `no sweat' emerge to a
 full OS.

You should really step first at the documentation and then ask about
it, gentoo doesn't have 'new isos to install', it has stage3 tarballs.
you are trying to see gentoo as a binary distro.

Did you even tried to read the message before asking?

Didn't this told you anything? (From your log):
---
* LLVM-3.6.2 requires C++11-capable C++ compiler. Your current compiler
 * does not seem to support -std=c++11 option. Please upgrade your compiler
 * to gcc-4.7 or an equivalent version supporting C++11.
 * ERROR: sys-devel/llvm-3.6.2::gentoo failed (pretend phase):
 *   Currently active compiler does not support -std=c++11
---
gcc-config: error: could not run/locate 'i686-pc-linux-gnu-cpp'
 * ERROR: x11-base/xorg-server-1.17.2-r1::gentoo failed (pretend phase):
 *   Sorry, but gcc earlier than 4.0 will not work for xorg-server.


Upgrade your compiler and try again. But I should say from reading
your email you don't seem to have the attitude to be a gentoo user and
enjoy it, if this made think about reinstalling without even giving a
good read to that error message, I've using gentoo for ~2 years, and
even then 4.7 or 4.6, I remember was already a stable compiler, are
you sure you haven't upgraded in a significant more time than you say?