Summary: | dev-libs/cgicc-3.2.5 fails to build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Evil Compile Person <bugs> |
Component: | New packages | Assignee: | C++ Team [disbanded] <cpp+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | death, evan.teran, feniksa, flameeyes, mlspamcb, stas |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Patch for cgicc-3.2.5.ebuild that calls eautoreconf
Oops use this patch for cgicc-3.2.5, previous was wrong one does autoreconf and fixes example links (manually) patch for HTMLElement.cpp fixes disable debug by remove USE debug cgicc-3.2.5-r1 ebuild Manifest for cgicc-3.2.5-r1 ebuild and files New ebuild with debug warning fixed New manifest New ebuild with debug warning fixed (debug remove from IUSE) Manifest for cgicc-3.2.5-r1 ebuild and files |
Description
Evil Compile Person
2008-06-16 17:43:03 UTC
Created attachment 164869 [details, diff]
Patch for cgicc-3.2.5.ebuild that calls eautoreconf
Running eautoreconf should fix up the links that were pointing to libtool-1.5 locations for helper files
Created attachment 164871 [details, diff]
Oops use this patch for cgicc-3.2.5, previous was wrong one
Your path helps to correct symlinks "work/cgicc-3.2.5/support/*" from "/usr/share/libtool/*" to "/usr/share/libtool/config/*". But it doesn't correct the same symlinks in "work/cgicc-3.2.5/example". Fix it, please. Created attachment 176659 [details, diff]
does autoreconf and fixes example links (manually)
The same patch as Wormo's one, additionnally :
* fixes symbolic links for example directory
(rm & ln -s in ebuild)
* applies patch on HTMLElement.cpp adding an #include <cstring>
(I went into trouble compiling with gcc-4.3.2, patch posted later on)
* fixes a warning during configure stage
(debug-logging no longer understood by configure)
Created attachment 176662 [details, diff]
patch for HTMLElement.cpp
cf last post
Please add HTMLElement-cstring.patch from Ikujam to both 3.2.3 and 3.2.5 ebuilds. cgicc is not compilable now w/o this patch. Created attachment 213230 [details, diff]
fixes disable debug by remove USE debug
ebuild.patch by Henrik I got a error. /var/tmp/portage/dev-libs/cgicc-3.2.5/temp/environment: line 2739: --disable-debug: command not found everything works 100% behind The HTMLElement-cstring.patch is need for cgicc 3.2.5 and 3.2.3. HTMLElement-cstring.patch works 100% (In reply to comment #8) > ebuild.patch by Henrik > > I got a error. > /var/tmp/portage/dev-libs/cgicc-3.2.5/temp/environment: line 2739: > --disable-debug: command not found > everything works 100% behind > > The HTMLElement-cstring.patch is need for cgicc 3.2.5 and 3.2.3. > HTMLElement-cstring.patch works 100% > everything works 100% by remove USE debug from ebuild.patch by Ikujam And have upload the ebuild.patch with no debug This patches not in stable portage. What patches to use, in what order? sorry, i don't understand Created attachment 223703 [details]
cgicc-3.2.5-r1 ebuild
cgicc-3.2.5-r1 ebuild (you can use it without any patches)
Created attachment 223705 [details]
Manifest for cgicc-3.2.5-r1 ebuild and files
Please add cgicc-3.2.5-r1.ebuild and HTMLElement-cstring.patch to main tree. Tested successfully on ~amd64. (In reply to comment #11) > Created an attachment (id=223703) [details] > cgicc-3.2.5-r1 ebuild > > cgicc-3.2.5-r1 ebuild (you can use it without any patches) > Can you compile it with -debug? (In reply to comment #14) > (In reply to comment #11) > > Created an attachment (id=223703) [details] [details] > > cgicc-3.2.5-r1 ebuild > > > > cgicc-3.2.5-r1 ebuild (you can use it without any patches) > > > > Can you compile it with -debug? > Yep, with and without. * configure: WARNING: unrecognized options: --enable-debug-logging This just a warning. Created attachment 223739 [details]
New ebuild with debug warning fixed
Created attachment 223741 [details]
New manifest
Created attachment 223743 [details]
New ebuild with debug warning fixed (debug remove from IUSE)
Created attachment 223745 [details]
Manifest for cgicc-3.2.5-r1 ebuild and files
Sorry for attachment flood. Can this ebuild be testing, so it can get to portage. (In reply to comment #21) > Can this ebuild be testing, so it can get to portage. > There is only one thing I'm not sure. The HTMLElement-cstring.patch is this in the portage or how? I test the patch as I have thrown up, with HTMLElement-cstring.patch. I can see there is no great difference whether you use the patch and HTMLElement-cstring.patch or ebuild and manifest from Mishael Sibiryakov. I have test patch on x86 and amd64. Fixed by 3.2.9 in Portage. |