Bug 23558 - abiword 1.99.2 ebuild with some modifications, notably plugins
|
Bug#:
23558
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: All
|
Status: VERIFIED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: foser@gentoo.org
|
Reported By: mg_gentoo@yahoo.com
|
|
Component: Ebuilds
|
|
|
URL:
http://www.abisource.com
|
|
Summary: abiword 1.99.2 ebuild with some modifications, notably plugins
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2003-06-26 19:03 0000
|
it is set to enable all, which means it will try to build everything for which
it finds all known prerequisites and which hasnt been explicitly blocked
upstream (for various good reasons). Right now that's fine because all known
build bustage has been fixed in the plugins that aren't blocked and this is
marked unstable anyway, even though it isn't _really_ unstable. So enjoy, have
fun, live a little. There are a bunch of very nifty plugins here.
Attached.
it uses ${PV} which means you misnamed the file, it should be 1.99.1.
I'm really sorry, my aplogies. Too hot climate and too bad days :(
Regards
No worries, lemme know if anything else doesn't work.
foser-
Two other things to think about are a noplugins local use, if anyone finds it useful enough to add that in (I don't so I just ignored it for speed and simplicity's sake), as well as a more comprehensive method of reporting which plugins are available to the builder than the suboptimal, inconsistent messages abi provides. Hopefully before 2.4 a better plugin build system will be in place (current one leaves a lot to be desired) but if anyone has the spare time until then...
Created an attachment (id=14078) [details]
Output of failed emerge
Emerge fails on compiling. In the attachment is the output (cut off all lines
not important).
Portage 2.0.48-r1 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1)
=================================================================
System uname: 2.4.20-gentoo-r5 i686 AMD Athlon(tm) XP 2000+
GENTOO_MIRRORS="http://212.219.56.152/sites/www.ibiblio.org/gentoo/
http://212.219.56.131/sites/www.ibiblio.org/gentoo/
ftp://ftp.tu-clausthal.de/pub/linux/gentoo/
ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config
/usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config
/usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY="/usr/local/portage"
USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg libg++ libwww mikmod mmx
mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib directfb
gtkhtml alsa gdbm berkdb slang readline arts bonobo svga tcltk java guile X sdl
gpm tcpd pam ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl
mozilla cdr acpi dga dvd evo fbcon gb gnomedb gtk2 mbox mozaccess mozcalendar
mozinterfaceinfo mozp3p mozsvg mozxmlterm pic threads tiff usb"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-O2 -march=athlon-xp -pipe -fomit-frame-pointer -O2 -m3dnow "
CXXFLAGS="-O2 -march=athlon-xp -pipe -fomit-frame-pointer -O2 -m3dnow "
ACCEPT_KEYWORDS="x86 ~x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"
REcompiling gcc 3,2 against latest glibc installed worked for me.
Created an attachment (id=14340) [details]
Updated abiword-1.99.2.ebuild
libole2 should not be a direct dep of abiword, and wv includes its own libole
(as nasty as that is), the last I saw we weren't specifying to use
system-libole2 for wv, and everything else uses libgsf.
Also, I just now noticed this dep when looking at the ebuild, but abiword
builds fine without libole2 merged, on my clean environment (no stuff from
outside of portage causing false results).
sorry, martin fscked up the plugin tarball again, I'll have to change the
ebuild accordingly
*** Bug 24222 has been marked as a duplicate of this bug. ***
finally added this, thnx for keeping up with it.
the libole2 dep was a remnant of worse times i think, thats a good example of why you really always should check updates to ebuilds.