From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kompozer: undefined reference to `SEC_ASN1Encode_Util'
Date: Thu, 28 Apr 2011 14:28:14 -0500 [thread overview]
Message-ID: <BANLkTinGifWrHemWtEt-4NCxTDjFga_9xw@mail.gmail.com> (raw)
In-Reply-To: <201104271808.42427.peter@humphrey.ukfsn.org>
On Wed, Apr 27, 2011 at 12:08 PM, Peter Humphrey
<peter@humphrey.ukfsn.org> wrote:
> Hello list,
>
> I've been trying to install kompozer (very useful for developing web style
> sheets), but it fails with a whole lot of errors such as the one in the subject.
>
> Googling only shows a conversation from two-and-a-half years ago, with no real
> solution after much discussion of nss and nspr, both of which I've remerged
> (nspr has the utils USE flag set).
>
> Does anyone here know how to evade this problem? Alternatively, is there another
> visual web-page development tool?
Hi,
I don't see kompozer in portage at all. Is it in an overlay?
I think the function in the subject is from libnss, so I wonder if
trying a different version of libnss might produce different results.
Kompozer is probably closely related to some version of Firefox or
Seamonkey. If you know which version it is similar to, you might be
able to look at the dependencies for that and compare them.
I also wonder if you might need to remove -Wl,--as-needed from your LDFLAGS.
next prev parent reply other threads:[~2011-04-28 19:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 17:08 [gentoo-user] Kompozer: undefined reference to `SEC_ASN1Encode_Util' Peter Humphrey
2011-04-28 19:28 ` Paul Hartman [this message]
2011-04-29 9:03 ` Peter Humphrey
2011-05-01 16:29 ` Peter Humphrey
2011-05-02 16:54 ` Paul Hartman
2011-05-02 19:12 ` Peter Humphrey
2011-05-02 20:18 ` Mick
2011-05-03 8:00 ` Peter Humphrey
2011-05-03 8:12 ` Peter Humphrey
2011-05-03 18:18 ` Mick
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=BANLkTinGifWrHemWtEt-4NCxTDjFga_9xw@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