From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Tips/Tricks for Gentoo on low-spec computer?
Date: Tue, 20 Jan 2009 21:28:51 -0600 [thread overview]
Message-ID: <58965d8a0901201928i2cc96699r757d0dbb0841d31@mail.gmail.com> (raw)
In-Reply-To: <gl60ko$c5q$1@ger.gmane.org>
On Tue, Jan 20, 2009 at 8:18 PM, Grant Edwards <grante@visi.com> wrote:
> On 2009-01-21, Dale <rdalek1967@gmail.com> wrote:
>
>> It's funny, I have read a lot of people complain that the binary is the
>> same way but compiling from source works. Interesting. The reason I
>> was told I should compile my own is because it was more stable than the
>> binary.
>
> The first time I tried installing OOo, I did the binary
> install. It wouldn't run, so since then I've always built it.
>
>> How do you figure that OOo from source is not supported?
>
> I've been wondering that as well. I checked the package
> database and the OOo ebuild is marked as stable for x86. In my
> book, that's "supported". Of course that's not be the same
> thing as "practical" for some machines (I believe my OOo emerge
> just passed hour 31). It would be interesting to know how much
> further it's go to go, but as long as it's done in a week or so
> that'll be good enough. I remember building binutils, gcc,
> X11, emacs, and so on from sources on a 25MHz 68000 with 4MB of
> RAM -- that took some patience as well.
Latest OOo 3.0 source compile for me took 1hr 34 minutes on my
dual-core E6600 overclocked to 3ghz with 8 gigs of RAM :P
i don't know what that translates to in your machine speed. I have
6000 bogomips for each core according to /proc/cpuinfo (I know it's
not a benchmark)
Paul
next prev parent reply other threads:[~2009-01-21 3:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 17:05 [gentoo-user] Tips/Tricks for Gentoo on low-spec computer? Volker Armin Hemmann
2009-01-20 17:14 ` Paul Hartman
2009-01-20 17:15 ` Alejandro
2009-01-20 17:22 ` Nick Cunningham
2009-01-20 17:32 ` Paul Hartman
2009-01-20 18:42 ` Neil Bothwick
2009-01-20 18:53 ` Dirk Heinrichs
2009-01-20 19:37 ` [gentoo-user] " Grant Edwards
2009-01-21 19:01 ` Daniel Troeder
2009-01-20 19:20 ` Grant Edwards
2009-01-21 15:57 ` Grant Edwards
2009-01-24 14:43 ` [gentoo-user] " Steven Lembark
2009-01-20 17:27 ` Volker Armin Hemmann
2009-01-20 17:37 ` Paul Hartman
2009-01-20 17:56 ` Volker Armin Hemmann
2009-01-20 18:00 ` s3b4sm4gr1
2009-01-20 19:23 ` [gentoo-user] " Grant Edwards
2009-01-21 1:00 ` [gentoo-user] " Dale
2009-01-24 14:53 ` Steven Lembark
2009-01-24 15:47 ` [gentoo-user] " Grant Edwards
2009-01-24 15:55 ` [gentoo-user] " Dale
2009-01-20 17:37 ` [gentoo-user] " Grant Edwards
2009-01-21 0:54 ` [gentoo-user] " Dale
2009-01-21 2:18 ` [gentoo-user] " Grant Edwards
2009-01-21 3:28 ` Paul Hartman [this message]
2009-01-21 3:49 ` Grant Edwards
2009-01-21 4:02 ` Paul Hartman
2009-01-21 3:39 ` Shawn Haggett
-- strict thread matches above, loose matches on Subject: below --
2009-01-20 16:46 [gentoo-user] " Grant Edwards
2009-01-20 17:05 ` Paul Hartman
2009-01-20 17:36 ` [gentoo-user] " Grant Edwards
2009-01-20 18:01 ` [gentoo-user] " Dirk Heinrichs
2009-01-20 19:30 ` [gentoo-user] " Grant Edwards
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=58965d8a0901201928i2cc96699r757d0dbb0841d31@mail.gmail.com \
--to=paul.hartman+gentoo@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