From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] kdeaddons-2.2.1-r1.ebuild
Date: Mon, 19 Nov 2001 16:16:16 +0200 [thread overview]
Message-ID: <0GN100F3QXHNMF@mxout2.netvision.net.il> (raw)
In-Reply-To: <20011119020826.44724EEDD@chiba.3jane.net>
On Sunday 18 November 2001 20:06, you wrote:
> The ebuild for kdeaddons-2.2.1-r1 is broken. At least on my machine, I've
> been working on a new install of gentoo, and started compiling the machine
> yesterday. The first problem is the fact that the ebuild isn't looking in
> /usr/include/noatun, I fixed this by adding a
> --with-extra-includes=/usr/include/noatun to the kde.eclass.
OK I've aded this to the ebuild (it doesn't belong in the eclass, it's
kdeaddons-specific).
> The second
> problem with the ebuild is that /usr/lib/kdelibs-2.2.1/lib/libnoatun.so
> link is broken, this needs to be linked against /usr/lib/libnoatun.so all
> need to moved into /usr/lib/kdelibs-2.2.1/lib. I think danamark was working
> on some kinda changes lately, so maybe that the problem too, if so what
> packages do I need to remerge or change? I just thought I should mention
> the fixes that I did to make it work.
I don't understand what you said. How did you make it work?
libkfile.la isn't the only thing it can't find, it can't find every other
standard library that now installs in /usr/lib/kdeklibs-*/lib. Strange. I'm
working on it. Meanwhile the ebuild can be considered officially broken :-(.
To know what you need to remerge, read my orig. announcement on
gentoo-announce (cc'd to gentoo-dev).
--
Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel
next prev parent reply other threads:[~2001-11-19 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 18:06 [gentoo-dev] kdeaddons-2.2.1-r1.ebuild Michael M Nazaroff
2001-11-19 14:16 ` Dan Armak [this message]
2001-11-19 8:55 ` Michael M Nazaroff
2001-11-24 13:36 ` Dan Armak
2001-11-19 15:08 ` Dan Armak
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=0GN100F3QXHNMF@mxout2.netvision.net.il \
--to=danarmak@gentoo.org \
--cc=gentoo-dev@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