From your log I can see that it uses wxGTK-2.4 to compile. But this won't work as Code::Blocks needs at least wxGTK-2.6. Although the ebuild states wxGTK-2.6.2 as dependency it looks like it uses 'wx-config' when calling ./configure. But (at least on gentoo) wx-config is for wxGTK-2.4! Thus configure should use 'wx-config-2.6'. Thus the call to econf should look like this:
econf --with-wx-config=wx-config-2.6 ${myconf} || die "econf failed"
Anyone able to submit this change as new ebuild?
The wxGTK version problem has been solved in my gentoo overlay since quite some time now,
and the autorevision problem can be solved with a simple one-line sed command ;)
Look here: http://forums.gentoo.org/viewtopic-t-440412.html
But just to make you know, i'm testing new revision of the overlay right now before i update that topic,
since the build fails now on patching the wxFlatNotebook since it got commited into svn recently.
But all in all it works if you simply remove the patch from files/patches subdirectory and redigest,
and after all it will get updated in about an hour including 2.7.0-svn version of angelscript for amd64 scripting
support.... ;)
Thanks,
T
EDIT:
Just for convenience:
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
inherit autotools wxwidgets subversion
ESVN_CO_DIR="${PORTAGE_ACTUAL_DISTDIR-${DISTDIR}}"/svn-src/${P/-svn}/"${ESVN_REPO_URI##*/}"
ESVN_REPO_URI="svn://svn.berlios.de/codeblocks/trunk"
ESVN_PROJECT="${P}"
WX_GTK_VER="2.6"
DESCRIPTION="free cross-platform C/C++ IDE"
HOMEPAGE="http://www.codeblocks.org/"
LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86 ~amd64"
IUSE="contrib unicode xrc monolithic debug"
RDEPEND="=x11-libs/wxGTK-2.6*
x11-libs/gtk+
!dev-util/codeblocks
!dev-util/codeblocks-cvs"
DEPEND="${RDEPEND}
>=sys-devel/autoconf-2.5.0
>=sys-devel/automake-1.7
>=sys-devel/libtool-1.4
app-arch/zip"
pkg_setup() {
if use unicode; then
need-wxwidgets "unicode"
else
need-wxwidgets "gtk2"
fi
}
src_unpack() {
subversion_src_unpack
EPATCH_SOURCE="${FILESDIR}/patches" \
EPATCH_SUFFIX="patch" \
EPATCH_ARCH="all" \
epatch
sed -i -e "s:\$(top_srcdir):${ESVN_CO_DIR}:" src/tools/autorevision/Makefile.am
}
src_compile() {
cd ${S}
eautoreconf || die "Died in action: eautoreconf..."
einfo "Changing properties ..." && \
edos2unix ${S}/{bootstrap,src/update} && \
chmod a+rx ${S}/{bootstrap,src/update} && \
edos2unix ${S}/src/setup/mime/codeblocks.{desktop,applications} || \
die "Died in action: properties ..."
./bootstrap || die "Died in action: shipped bootstrap ..."
econf --with-wx-config=wx-config-2.6 --enable-dependency-tracking \
$(use_enable contrib) $(use_enable unicode) $(use_enable xrc) \
$(use_enable monolithic) $(use_enable debug) \
|| die "Died in action: econf ..."
make clean-zipfiles || die "\"make clean-zipfiles\" failed..."
make || die "Died in action: make ..."
}
src_install() {
make DESTDIR="${D}" install || die "Died in action: make install ... "
}
including 2.7.0-svn version of angelscript for amd64 scripting support....
Huh?
There is no 2.7.0-svn. The svn version is what 2.6.+ will become, AFAIK.
Besides, where did you see the 64bit support? AS supports 64bits in AS_MAX_PORTABILITY mode only...
Well, then the code in there is a little confusing:
--- codeblocks-9999-orig/src/sdk/as/include/angelscript.h 2006-05-10 19:27:47.000000000 +0200
+++ codeblocks-9999/src/sdk/as/include/angelscript.h 2006-05-10 19:32:09.372021000 +0200
@@ -53,11 +53,11 @@ BEGIN_AS_NAMESPACE
// AngelScript version
-#define ANGELSCRIPT_VERSION 20601
+#define ANGELSCRIPT_VERSION 20700
#define ANGELSCRIPT_VERSION_MAJOR 2
-#define ANGELSCRIPT_VERSION_MINOR 6
-#define ANGELSCRIPT_VERSION_BUILD 1
-#define ANGELSCRIPT_VERSION_STRING "2.6.1 WIP"
+#define ANGELSCRIPT_VERSION_MINOR 7
+#define ANGELSCRIPT_VERSION_BUILD 0
+#define ANGELSCRIPT_VERSION_STRING "2.7.0 WIP"
// Data types
@@ -187,10 +187,10 @@ extern "C"
Just a snipp of an update patch from 20060505 svn to today's. (EDIT: attached the full patch against c::b-svn)
About the 64bit support I didn't really know, although the comments of preliminary 64bit support are
on the HP, I probably missed the details..... I'm not a 64bit user, so i couldn't verify anyway....
Thanks,
T
[attachment deleted by admin]