Summary: | nvu fails to patch vertion 0.6 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | ewan paton <ewan_paton> |
Component: | New packages | Assignee: | Chris White (RETIRED) <chriswhite> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | axel.privat, corporate_gadfly, crefff, derek.berube, geekypenguin, yvasilev |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://forums.gentoo.org/viewtopic.php?p=1876771#1876771 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Output While Attempting to Apply: nvu-0.50-nvu.patch
Output of emerge net-www/nvu Freetype patch |
Description
ewan paton
2004-12-13 21:06:45 UTC
I'm running into a similar problem running on a Dell Latitude C840 with a P4M processor. Just to be sure, see if you guys can get it to work with >= idl-0.8.0. If you can, it just needs to be added as a non-conditional dep for nvu (right now it's based upon the gtk2 USE flag). If it starts asking for more gtk2 style deps.. then gtk2 deps will just have to be enforced. I myself would prefer to do that.. but for people that wish to keep with gtk 1, least I can do. Created attachment 47497 [details]
Output While Attempting to Apply: nvu-0.50-nvu.patch
Created attachment 47498 [details]
Output of emerge net-www/nvu
If it is of any interest, I've attached a copy of the emerge output to this
bug. There were some errors that I encountered while compiling the
nsFreeType.cpp code (lines 285, 286, 287 to name a few).
Here is the output of emerge info run from my machine: wildstar ~ # emerge info Portage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r10 i686) ================================================================= System uname: 2.6.9-gentoo-r10 i686 Intel(R) Pentium(R) 4 Mobile CPU 2.00GHz Gentoo Base System version 1.6.8 Python: dev-lang/python-2.2.3-r5,dev-lang/python-2.3.4 [2.3.4 (#1, Sep 26 2004, 13:20:59)] dev-lang/python: 2.2.3-r5, 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.3 sys-devel/binutils: 2.15.92.0.2-r2 sys-devel/libtool: 1.5.10-r2 virtual/os-headers: 2.6.8.1-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=i686 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=i686 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig buildpkg candy ccache distlocks sandbox sfperms"GENTOO_MIRRORS="ftp://gentoo.mirrors.pair.com/ http://www.gtlib.cc.gatech.edu/pub/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://gentoo.mirrors.pair.com/" LDFLAGS="" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /usr/local/bmg-main /usr/local/bmg-gnome-current" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X acl alsa apm arts avi berkdb bitmap-fonts bonobo cdr crypt cups dvd encode esd fam foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 gtkhtml guile imagemagick imlib ipv6 java jpeg junit kerberos krb4 ldap libwww mad mikmod motif mozilla mpeg mysql ncurses nls oggvorbis opengl oss pam pcmcia pdflib perl png postgres python quicktime readline samba scanner sdl slang spell ssl svga tcpd tiff truetype xml xml2 xmms xv zlib" I'm not sure if this is what you mean, but I had dev-libs/libIDL-0.8.4 installed when I attempted the build. I'm something of a neophyte when it comes to compiling stuff under LINUX, so if you could let me know what else you would like me to try I'd be happy to do so. Maybe version bump to 0.70 help? Now I'm testing it. If I can quickly summarize here, please bear with me. Ewan reported an issue in comment 0 about: a) a configure error about libIDL-2.0 >= 0.8.0 b) failed application of a patch Then, in comment 1, Derek says he's having a similar problem, however, in comment 4, it looks like his problem is really not the same. (Derek's emerge output even has a line "checking for libIDL-2.0 >= 0.8.0... yes"). His issue seems to be: a) a make error while compiling nsFreeType.cpp b) failed application of a patch Now, I hope I didn't miss anything obvious, but, in my mind, these are two separate issues and should probably be filed as separate bugs. In any case, I am experiencing the same issue as Derek (the freetype wierdness/compile error). Just curious, shouldn't the failed patch be reported as soon as the patch fails, rather than waiting for a "error" to occur and then reporting it after the fact? I find it a little odd. Oh, well! Chris, is there anything I can do to help you out? Well.. basically, that patch fails if anything in the compilation process fails. As for freetype, I'm working on that right now and getting nowhere. I've contact upstream who, after about a couple of weeks, responded with a recommendation, which I tried and still failed. I sent a response back and I'm still waiting while people are eagerly spamming the mailing lists with information on runtime errors :| (love how that works..). Until I get time to sit down and work out the code, I don't expect much there... A simple look at the patch says it all it is trying to patch files that aren't present seeing they have been compiled or what not. Review the patch for all your problems you figure out the patch you figure out all errors. Chris I might have found the patch we need to make this bug report go away for good let me test it and I will repost what comes up in a bit. Well after much need work I have finally fixed the problems for all I do believe. Chris if you could get this added to ebuild and updated as soon as possible we could get this bug report closed. It is a patch I found online had to do some modifications manually but all works well with it. Patch will apply clean just add "epatch ${FILESDIR}/nvu-0.50-freetype-compile.patch" directly blow "epatch ${FILESDIR}/nvu-0.50-dir.patch" and emerge till your heart is content. Created attachment 50409 [details, diff]
Freetype patch
just add this to your FILES dir and read previous post for how to modify ebuild
and you should be good to go enjoy!!!
This ISN'T A BLOCKER this is a simple bug that should be fixed a blocker is some package that prevents ya from using your system!! This is simple a bug that should be fixed and just so all know nothing in portage depends on NVU so go read about filling a bug report please this is ridiculious Chris you chould change severity as soon as possible so these ppl get the clue. Fixed in the latest releases. |