public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] bootstrap.sh and /var/lib/portage/world
Date: Thu, 07 Apr 2005 09:08:05 -0400	[thread overview]
Message-ID: <1112879285.7158.15.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <4254E282.8010606@free.fr>

[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]

On Thu, 2005-04-07 at 07:34 +0000, mathias wrote:
> Hi all,
> 
> I finished this night succefully compilation of bootstrap.sh with stage 
> 1 2005.0.
> The problem is my /var/lib/portage/world contain only 4 packages, glibc, 
> linux-headers, nano and gettext but no gcc ... I've read something for 
> several months about this problem on bugs.gentoo.org or on forums, I 
> don't remember exactly, but the question is why bootstrap.sh don't print 
> all installed packages in world file since the problem is know for 
> several months ?

The world file will only show packages that are implicitly called by
emerge.  It does not list dependencies.  It does this for a very good
reason, as dependencies can change over time and it keeps you from
having tons of orphaned packages.

> I've meet a second problem, attr package for compiling search crtn.o in 
> /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5/../../../ but only 
> /usr/lib/i686-pc-linux-gnu exist ... I made symbolic link this morning, 
> but why bootstrap (or anything else) don't make this link alone ?

Did you change CHOST in your make.conf?  If you did, it won't work.

> This is not my first installation of this fantastic system, but if it 
> was, these problems should have make me to become crazy :/
> 
> Perhaps there is lot of reasons to leave it in this state, but I don't 
> understand this reasons :)
> 
> Thanks a lot for your responses, have a nice day,

Well, this list is not a support list.  It is a development list.  You
would probably be better off asking these questions on gentoo-user, the
forums, or vai a bug on http://bugs.gentoo.org instead.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-04-07 13:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31 13:17 [gentoo-dev] PAM related: pam_console ? Diego "Flameeyes" Pettenò
2005-03-31 13:27 ` Mike Frysinger
2005-03-31 13:34   ` Diego "Flameeyes" Pettenò
2005-03-31 13:57     ` Mike Frysinger
2005-03-31 14:26       ` Diego "Flameeyes" Pettenò
2005-03-31 15:01         ` Mike Frysinger
2005-03-31 15:17           ` Diego "Flameeyes" Pettenò
2005-04-06 21:47         ` Martin Schlemmer
2005-04-07  7:34           ` [gentoo-dev] bootstrap.sh and /var/lib/portage/world mathias
2005-04-07 13:08             ` Chris Gianelloni [this message]
2005-04-06 21:41   ` [gentoo-dev] PAM related: pam_console ? Martin Schlemmer
2005-03-31 20:38 ` Robin H. Johnson
2005-03-31 21:09   ` Diego "Flameeyes" Pettenò
2005-03-31 21:35     ` Mike Frysinger
2005-03-31 22:19       ` Diego "Flameeyes" Pettenò
2005-04-06 21:52         ` Martin Schlemmer
2005-04-06 21:40 ` Martin Schlemmer

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=1112879285.7158.15.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@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