From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] splitting build deps out from depends
Date: Fri, 1 Jul 2005 22:25:34 +0200 [thread overview]
Message-ID: <200507012225.34721.pauldv@gentoo.org> (raw)
In-Reply-To: <200507012053.18684@enterprise.flameeyes.is-a-geek.org>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
On Friday 01 July 2005 20:53, Diego 'Flameeyes' Pettenò wrote:
> On Friday 01 July 2005 20:42, Brian D. Harring wrote:
> > Err... missing the point, and proving my point. Current portage
> > _will_ fail because it's an unstated dependency. Why shouldn't
> > portage be provided the deps it needs so it can figure out what is
> > needed to get to what the user requested?
>
> BDEPEND is not going to resolve the case Mike shown.
>
> GCC bdepends over GCC to compile, you don't have GCC, you can't install
> GCC, you can't install anything (a part from binpkgs).
> But if you put GCC in profile, no need to depend on it, you'll always have
> one also if nothign depends on it and the problem is resolved.
>
> BTW, as I already stated on irc, GCC is a RDEPEND not a BDEPENED because of
> libgcc_s.so and libstdc++.so, so...
No, it's both. You need to have a cross gcc on the compiling machine, and a
runtime gcc (gcc-lib parts) on the running machine.
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-01 20:27 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 16:25 [gentoo-dev] splitting build deps out from depends Brian D. Harring
2005-07-01 17:49 ` Mike Frysinger
2005-07-01 18:03 ` Diego 'Flameeyes' Pettenò
2005-07-01 18:11 ` Brian D. Harring
2005-07-01 18:30 ` Mike Frysinger
2005-07-01 18:42 ` Brian D. Harring
2005-07-01 18:46 ` Brian D. Harring
2005-07-01 18:53 ` Diego 'Flameeyes' Pettenò
2005-07-01 19:10 ` Brian D. Harring
2005-07-01 20:25 ` Paul de Vrieze [this message]
2005-07-05 9:39 ` Martin Schlemmer
2005-07-07 11:56 ` John Myers
2005-07-07 19:44 ` Kito
2005-07-07 20:45 ` Diego 'Flameeyes' Pettenò
2005-07-09 9:28 ` Jason Stubbs
2005-07-01 18:37 ` Diego 'Flameeyes' Pettenò
2005-07-01 22:59 ` Drake Wyrm
2005-07-02 1:16 ` Kito
2005-07-04 0:18 ` Brian D. Harring
2005-07-09 9:28 ` Jason Stubbs
2005-07-05 10:48 ` Martin Schlemmer
2005-07-05 23:17 ` Brian Jackson
2005-07-06 1:46 ` Martin Schlemmer
2005-07-06 1:59 ` Brian Jackson
2005-07-06 2:39 ` Martin Schlemmer
2005-07-06 17:08 ` Brian D. Harring
2005-07-07 13:29 ` Martin Schlemmer
2005-07-09 9:28 ` Jason Stubbs
2005-07-09 9:45 ` Diego 'Flameeyes' Pettenò
2005-07-09 9:28 ` Jason Stubbs
2005-07-09 10:17 ` Martin Schlemmer
2005-07-09 9:28 ` Jason Stubbs
2005-07-09 9:47 ` Diego 'Flameeyes' Pettenò
2005-07-09 10:20 ` Martin Schlemmer
2005-07-09 11:45 ` Diego 'Flameeyes' Pettenò
2005-07-09 12:01 ` Martin Schlemmer
2005-07-09 12:08 ` Diego 'Flameeyes' Pettenò
2005-07-09 12:37 ` Stephen Bennett
2005-07-09 12:41 ` Martin Schlemmer
2005-07-09 12:46 ` Diego 'Flameeyes' Pettenò
2005-07-09 13:05 ` Martin Schlemmer
2005-07-09 13:11 ` Diego 'Flameeyes' Pettenò
2005-07-09 14:10 ` Martin Schlemmer
2005-07-09 19:19 ` Kito
2005-07-01 17:58 ` Diego 'Flameeyes' Pettenò
2005-07-01 18:35 ` Maurice van der Pot
2005-07-01 18:45 ` Brian D. Harring
2005-07-01 18:56 ` Maurice van der Pot
2005-07-01 19:12 ` Brian D. Harring
2005-07-01 19:19 ` Maurice van der Pot
2005-07-02 3:48 ` [gentoo-dev] " Duncan
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=200507012225.34721.pauldv@gentoo.org \
--to=pauldv@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