From: Michael Haubenwallner <michael.haubenwallner@salomon.at>
To: m h <sesquile@gmail.com>
Cc: gentoo-osx@lists.gentoo.org
Subject: Re: [gentoo-osx] PREFIX the next generation...
Date: Wed, 21 Dec 2005 10:39:09 +0100 [thread overview]
Message-ID: <1135157949.6263.35.camel@sapc154> (raw)
In-Reply-To: <e36b84ee0512191449qee7d18tff4f88f99e6e4823@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
On Mon, 2005-12-19 at 14:49 -0800, m h wrote:
> I'm basically at the same state with Haubi's toolsbox and your method.
> After chatting with Kito I'm also thinking about sticking with
> toolsbox. (Since it is pretty generic and should run on most any
> unix). Kito also helped explain the next steps with seem to be coming
> up with virtuals/package.provided for (taken from emerge info):
> dev-lang/python: [Not Present]
> sys-apps/sandbox: [Not Present]
> sys-devel/autoconf: [Not Present]
> sys-devel/automake: [Not Present]
> sys-devel/binutils: [Not Present]
> sys-devel/libtool: [Not Present]
> sys-devel/odcctools: [Not Present]
> virtual/os-headers: [Not Present]
>
> Haubi- How did you deal with this in your 2.1 tree?
Hmm, don't know what you did, but i've installed these things using
portage. IIRC portage reads those versions from its database, not
querying the package's executables found in PATH or the like.
My 'emerge --info' output is attached.
~haubi
[-- Attachment #2: emerge-info --]
[-- Type: text/plain, Size: 1678 bytes --]
Portage 2.1_pre (!/portage/profiles/default-secondary/linux/x86, gcc-3.4.4, unavailable, 2.4.9-e.3smp i686)
=================================================================
System uname: 2.4.9-e.3smp i686 Intel(R) Xeon(TM) CPU 2.40GHz
Unknown Host Operating System
Python: dev-lang/python-2.4.1-r1 [2.4.1 (#1, Sep 14 2005, 15:16:31)]
distcc: No such file or directory [disabled]
dev-lang/python: 2.4.1-r1
sys-apps/sandbox: 1.2.9
sys-devel/autoconf: 2.59-r7, 2.13
sys-devel/automake: 1.5, 1.8.5-r3, 1.6.3, 1.7.9-r1, 1.4_p6, 1.9.5
sys-devel/binutils: 2.16-r1
sys-devel/libtool: 1.5.18
virtual/os-headers: [Not Present]
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -mcpu=i686 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/junk/haubi/w1/etc /junk/haubi/w1/kde/2/share/config /junk/haubi/w1/kde/3/share/config /junk/haubi/w1/share/config /junk/haubi/w1/var/qmail/control"
CONFIG_PROTECT_MASK="/junk/haubi/w1/etc/gconf /junk/haubi/w1/etc/terminfo /junk/haubi/w1/etc/env.d"
CXXFLAGS="-O2 -mcpu=i686 -pipe"
DISTDIR="/junk/haubi/w1/portage/distfiles"
FEATURES="autoaddcvs autoconfig buildpkg ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://sapc154.salomon.at/pub/toolsbox http://pc312005.salomon.at/gentoo"
MAKEOPTS="-j2"
PKGDIR="/junk/haubi/w1/portage/packages"
PORTAGE_TMPDIR="/junk/haubi/w1/var/tmp"
PORTDIR="/junk/haubi/w1/portage"
PORTDIR_OVERLAY="/junk/haubi/w1/wamas-portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 secondary userland_GNU kernel_linux elibc_glibc"
Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Config files: /junk/haubi/w1/etc/make.conf
prev parent reply other threads:[~2005-12-21 9:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 21:07 [gentoo-osx] PREFIX the next generation m h
2005-12-19 21:21 ` [gentoo-osx] " m h
2005-12-19 21:26 ` m h
2005-12-19 21:30 ` Grobian
2005-12-19 21:25 ` [gentoo-osx] " Grobian
2005-12-19 22:49 ` m h
2005-12-19 23:20 ` Kito
2005-12-20 1:33 ` m h
2005-12-20 6:32 ` Grobian
2005-12-20 9:23 ` Grobian
2005-12-20 20:11 ` m h
2005-12-20 20:53 ` Grobian
2005-12-20 23:00 ` m h
2005-12-20 23:20 ` m h
2005-12-21 0:09 ` m h
2005-12-21 12:50 ` Grobian
2005-12-22 6:57 ` Brian Harring
2005-12-22 7:02 ` Brian Harring
2005-12-22 10:35 ` Grobian
2005-12-21 13:26 ` Grobian
2005-12-20 22:18 ` Kito
2005-12-20 22:22 ` Kito
2005-12-21 9:39 ` Michael Haubenwallner [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=1135157949.6263.35.camel@sapc154 \
--to=michael.haubenwallner@salomon.at \
--cc=gentoo-osx@lists.gentoo.org \
--cc=sesquile@gmail.com \
/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