From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] another openoffice build failure
Date: Sat, 2 Sep 2006 19:16:05 -0700 [thread overview]
Message-ID: <7573e9640609021916p20797b24tcde8c2e20ee3bbc8@mail.gmail.com> (raw)
In-Reply-To: <yu9ejutn33w.fsf@nyu.edu>
On 9/2/06, Allan Gottlieb <gottlieb@nyu.edu> wrote:
> I am not sure what to try next. I suppose I could try to revert back
> to gcc3.4.6
> ajglap hdc10 # gcc-config --list-profiles
> [1] i686-pc-linux-gnu-3.4.6
> [2] i686-pc-linux-gnu-3.4.6-hardened
> [3] i686-pc-linux-gnu-3.4.6-hardenednopie
> [4] i686-pc-linux-gnu-3.4.6-hardenednopiessp
> [5] i686-pc-linux-gnu-3.4.6-hardenednossp
> [6] i686-pc-linux-gnu-4.1.1 *
> ajglap hdc10 #
>
> Any ideas would be welcome
Well googling wasn't terribly helpful for me, and I couldn't find any
bug report on bugs.gentoo.org.
The program that is failing ("ar") comes from binutils. Maybe you can
try the 2.17 version of binutils...it's what I built OOo with.
echo "~sys-devel/binutils-2.17 ~x86 >> /etc/portage/package.keywords
emerge --oneshot binutils
binutils-config -l # make sure it shows 2.17 as selected
emerge --oneshot openoffice
If this doesn't work, reverting gcc versions, or maybe even just merge
openoffice-bin.
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-03 2:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 18:07 [gentoo-user] another openoffice build failure Allan Gottlieb
2006-09-02 18:22 ` Rafael Fernández López
2006-09-02 20:19 ` Allan Gottlieb
2006-09-02 21:10 ` Richard Fish
2006-09-02 21:23 ` Lord Sauron
2006-09-02 23:26 ` Richard Fish
2006-09-02 23:14 ` Allan Gottlieb
2006-09-03 1:36 ` Allan Gottlieb
2006-09-03 2:16 ` Richard Fish [this message]
2006-09-04 21:59 ` Allan Gottlieb
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=7573e9640609021916p20797b24tcde8c2e20ee3bbc8@mail.gmail.com \
--to=bigfish@asmallpond.org \
--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