From: Francisco Ares <frares@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] emerge -e errors right after install
Date: Sat, 17 Aug 2013 13:13:33 -0300 [thread overview]
Message-ID: <CAHH9eM6g+RJz_R9tZMVh9d8M2_VVxu9jTSdt_Q9Gpv92NNaMng@mail.gmail.com> (raw)
In-Reply-To: <A56FABB9-A909-4232-A45B-08D3865C1A57@stellar.eclipse.co.uk>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
2013/8/17 Stroller <stroller@stellar.eclipse.co.uk>
>
> On 16 August 2013, at 14:22, Francisco Ares wrote:
>
> ...
> But (here comes the "but"), right on the point I was able to build the
> kernel ... I tried an "emerge -e world", and there were so many errors that
> very few packages were able to be completely built.
>
>
> Is this during the installation process?
>
> IMO you should exit the chroot and get the system booting before you try
> re-emerging everything.
>
> Stroller.
>
>
Yes, after a bunch of "/etc/" settings, including network, locale, keyboard
layout, ..., but before building the kernel.
I think this time the kernel had no effect, since the "stage-3" was working
perfectly, and then, during "emerge -e", some applications started to
malfunction, and returned to work after a "march" change.
Thanks to your contribution
Francisco
[-- Attachment #2: Type: text/html, Size: 1714 bytes --]
prev parent reply other threads:[~2013-08-17 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 13:22 [gentoo-user] emerge -e errors right after install Francisco Ares
2013-08-16 13:59 ` [gentoo-user] " Michael Palimaka
2013-08-16 14:58 ` Francisco Ares
2013-08-16 18:18 ` Francisco Ares
2013-08-16 22:38 ` Walter Dnes
2013-08-17 13:51 ` Michael Palimaka
2013-08-17 16:15 ` Francisco Ares
2013-08-17 16:09 ` Francisco Ares
2013-08-17 7:52 ` [gentoo-user] " Stroller
2013-08-17 16:13 ` Francisco Ares [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHH9eM6g+RJz_R9tZMVh9d8M2_VVxu9jTSdt_Q9Gpv92NNaMng@mail.gmail.com \
--to=frares@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox