From: "Lorenzo Milesi" <lorenzo.milesi@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] OpenOffice.org natively available for AMD64
Date: Mon, 16 Oct 2006 15:03:56 +0200 [thread overview]
Message-ID: <29c147bd0610160603g34a34cd7q3a7a9e0731eb9130@mail.gmail.com> (raw)
In-Reply-To: <45336D3E.4080009@gentoo.org>
> It finally happened: openoffice is expected to compile and work natively
> on amd64. In fact, I have just removed the package.mask entry.
> Versions starting from 2.0.4 should work and are therefore marked
> testing on amd64 (i.e. there still might be problems - please file bugs
> if you find any). That also means that you no longer need to run a
> multilib profile just because you need openoffice.
I had seen it this morning, and I though "What?!" :)
Which are the real advantages in compiling OOo instead of using -bin?
Except the multilib thing?
I've heard of aging compilation times... :)
thanks
maxxer
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-16 13:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 11:30 [gentoo-amd64] OpenOffice.org natively available for AMD64 Simon Stelling
2006-10-16 12:12 ` Sebastian Redl
2006-10-16 13:03 ` Lorenzo Milesi [this message]
2006-10-16 13:23 ` Boyd Stephen Smith Jr.
2006-10-16 13:29 ` Michael Weyershäuser
2006-10-16 13:30 ` Christoph Mende
2006-10-18 16:28 ` Felipe Ribeiro
2006-10-18 18:14 ` Jean-Marc Hengen
2006-10-19 3:08 ` Vladimir G. Ivanovic
2006-10-19 3:23 ` Gary E. Miller
2006-10-19 3:31 ` Vladimir G. Ivanovic
2006-10-19 3:29 ` Vladimir G. Ivanovic
2006-10-19 4:38 ` Neil Cathey
2006-10-19 4:42 ` Neil Cathey
2006-10-19 16:08 ` Vladimir G. Ivanovic
2006-10-19 18:10 ` Neil Cathey
2006-10-16 13:19 ` Boyd Stephen Smith Jr.
2006-10-18 15:41 ` Juergen Schinker
2006-10-23 15:41 ` Peter Humphrey
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=29c147bd0610160603g34a34cd7q3a7a9e0731eb9130@mail.gmail.com \
--to=lorenzo.milesi@gmail.com \
--cc=gentoo-amd64@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