public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] koffice-2.1.1_beta3-r1.ebuild errors
Date: Sun Aug  5 23:18:04 2001	[thread overview]
Message-ID: <01080607490200.00616@localhost> (raw)
In-Reply-To: <20010806021744.B25475@prosalg.no>

koffice 1.1-rc1 has been released a week ago. What you call 2.1.1-beta* is 
1.1-beta* in reality. I don't know why we have a custom versioning scheme 
here, I've emailed achim (who wrote the ebuilds) but got no response as yet. 
In fact that's what keeping me from introducing a 1.1-rc1 koffice ebuild.



On Monday 06 August 2001 03:17, you wrote:
> It doesn't build. It complains about missing (undefined) symbols when
> linking libkivio. I've not tried coming up with suggestion for a fix.
> Perhaps anyone with time and interest should start by trying to compile
> the kivio-part manually.
>
> Hint for rxvt and xterm users: -sl 1000 ;)
>
> Regards,
>
> Karl T
>
> On Sat, Aug 04, 2001 at 07:55:20PM +0000, Collins Richey wrote:
> > Has anyone successfully built this one?
> >
> > emerge koffice-2.1.1_beta3-r1.ebuild processes all the dependancies
> > successfully then ends with a lot of eerors like the following.  I can't
> > tell if there was an earlier error that was more informative.
> > make[5]: *** [libkivioconnectortool.la.closure] Error 1
> > make[5]: Leaving directory
> > `/tmp/portage/koffice-2.1.1_beta3-r1/work/koffice-1.1-beta3/kivio/plugins
> >/kivioconnectortool' make[4]: *** [all-recursive] Error 1
> > make[4]: Leaving directory
> > `/tmp/portage/koffice-2.1.1_beta3-r1/work/koffice-1.1-beta3/kivio/plugins
> >/kivioconnectortool' make[3]: *** [all-recursive] Error 1
> > make[3]: Leaving directory
> > `/tmp/portage/koffice-2.1.1_beta3-r1/work/koffice-1.1-beta3/kivio/plugins
> >' make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory
> > `/tmp/portage/koffice-2.1.1_beta3-r1/work/koffice-1.1-beta3/kivio'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory
> > `/tmp/portage/koffice-2.1.1_beta3-r1/work/koffice-1.1-beta3'
> > make: *** [all-recursive-am] Error 2
> >
> > !!! ERROR: the make command did not complete successfully.
> > !!! ("make")
> > !!! Since this is a critical task, ebuild will be stopped.
> >
> > !!! emerge aborting on
> > /usr/portage/kde-apps/koffice/koffice-2.1.1_beta3-r1.ebuild .
> >
> >
> > --
> > Collins Richey
> > Denver Area
> > Gentoo_rc5 XFCE
> >
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@cvs.gentoo.org
> > http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev

-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel



      reply	other threads:[~2001-08-06  5:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-04 19:45 [gentoo-dev] koffice-2.1.1_beta3-r1.ebuild errors Collins Richey
2001-08-05 18:19 ` Karl Trygve Kalleberg
2001-08-05 23:18   ` Dan Armak [this message]

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=01080607490200.00616@localhost \
    --to=danarmak@gentoo.org \
    --cc=gentoo-dev@cvs.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