From: m h <sesquile@gmail.com>
To: gentoo-osx@lists.gentoo.org,
Michael Haubenwallner <michael.haubenwallner@salomon.at>
Subject: Re: [gentoo-osx] PREFIX the next generation...
Date: Tue, 20 Dec 2005 16:09:47 -0800 [thread overview]
Message-ID: <e36b84ee0512201609k787631d2o9b6072aa4dc426c1@mail.gmail.com> (raw)
In-Reply-To: <e36b84ee0512201520n7d12959anb1043e253e448335@mail.gmail.com>
still chugging. Upto 550Megs of memory for configure.... I guess I
need to see what is really going on here...
On 12/20/05, m h <sesquile@gmail.com> wrote:
> On 12/20/05, m h <sesquile@gmail.com> wrote:
> > Thanks, after setting that and a few more symlinks, I'm compiling away....
> >
>
> Hmm, let me re-phrase that. I'm configuring away. Been "configuring"
> for the past 20 minutes or so. (Actually I don't think it's
> configuring, I think it is stuck. Here's a screen dump, nothing is
> going)
>
> emerge -av system.
> ....
>
> Do you want me to merge these packages? [Yes/No] y
> >>> emerge (1 of 53) sys-devel/patch-2.5.9-r1 to /
> *** Adjusting cvs-src permissions for portage user...
> >>> md5 files ;-) patch-2.5.9-r1.ebuild
> >>> md5 files ;-) files/digest-patch-2.5.9
> >>> md5 files ;-) files/digest-patch-2.5.9-r1
> >>> md5 files ;-) files/patch-2.5.9-cr-stripping.patch
> >>> md5 src_uri ;-) patch-2.5.9.tar.gz
> >>> Unpacking source...
> >>> Unpacking patch-2.5.9.tar.gz to /data1/portage/dec20/prefix/toolsbox-4-patch
> espre.20051220/i686-pc-linux-gnu/var/tmp/portage/patch-2.5.9-r1/work
> [ ok ]ing patch-2.5.9-cr-stripping.patch ...
> >>> Source unpacked.
> >>> Compiling source in /data1/portage/dec20/prefix/toolsbox-4-patchespre.200512
> 20/i686-pc-linux-gnu/var/tmp/portage/patch-2.5.9-r1/work/patch-2.5.9 ...
> ./configure --prefix=/data1/portage/dec20/prefix/toolsbox-4-patchespre.20051220/
> i686-pc-linux-gnu//usr --host=i686-pc-linux-gnu --mandir=/data1/portage/dec20/pr
> efix/toolsbox-4-patchespre.20051220/i686-pc-linux-gnu//usr/share/man --infodir=/
> data1/portage/dec20/prefix/toolsbox-4-patchespre.20051220/i686-pc-linux-gnu//usr
> /share/info --datadir=/data1/portage/dec20/prefix/toolsbox-4-patchespre.20051220
> /i686-pc-linux-gnu//usr/share --sysconfdir=/data1/portage/dec20/prefix/toolsbox-
> 4-patchespre.20051220/i686-pc-linux-gnu//etc --localstatedir=/data1/portage/dec2
> 0/prefix/toolsbox-4-patchespre.20051220/i686-pc-linux-gnu//var/lib --build=i686-
> pc-linux-gnu
>
--
gentoo-osx@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-21 0:10 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 [this message]
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
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=e36b84ee0512201609k787631d2o9b6072aa4dc426c1@mail.gmail.com \
--to=sesquile@gmail.com \
--cc=gentoo-osx@lists.gentoo.org \
--cc=michael.haubenwallner@salomon.at \
/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