Code::Blocks live svn ebuild [Check last page for news]

Yankee · Posted: Sun Jun 25, 2006 5:02 pm Post subject:

I am experciencing the same problem, but on the first emerge, so unmerging an older version is of no use.

ssvb · Tux's lil' helper Joined: 06 Nov 2003 Posts: 91

Adding "monolithic sdk static" USE flags helped. Did not check which USE flag exactly from this set is needed.

Bluespear · Posted: Sun Jun 25, 2006 8:16 pm Post subject:

I've also added "sdk" to compile this version, should be this.
Other flag I use are "contrib" and "unicode"

Bluespear · Posted: Tue Jul 04, 2006 10:37 am Post subject:

Some patchs seems to fail to apply.

Tiger683 · Posted: Wed Jul 05, 2006 7:31 am Post subject:

Pretty much fixed now i guess. rev.16, I missed uploading rev.15 somehow

_________________
Retired gentoo user

ClericLeech · n00b Joined: 06 Jul 2006 Posts: 3

Hi, I get the following error while building Code::Blocks,

any suggestions?

leech

Tiger683 · Posted: Fri Jul 07, 2006 12:42 pm Post subject:

younker · Apprentice Joined: 18 Feb 2004 Posts: 261 Location: China

>>> Emerging (1 of 1) dev-util/codeblocks-9999-r16 to /
>>> checking ebuild checksums ;-)

>>> checking auxfile checksums ;-)

>>> checking miscfile checksums ;-)

* Using /usr/lib/wx/config/gtk2-unicode-release-2.6
>>> Unpacking source...
* subversion update start -->
* repository: svn://svn.berlios.de/codeblocks/trunk
ÓÚÐÞ¶©°æ 2713¡£
* working copy: /usr/portage/distfiles/svn-src/codeblocks-9999/trunk

* Applying various patches (bugfixes/updates) ...
* 12_all_call-saveallfiles-on-custom-makefile-mode.patch ... [ ok ]
* 13_all_add-ability-to-physically-delete-file.patch ... [ ok ]
* 18_all_display-readonly-files-properly.patch ... [ ok ]
* 20_all_add-config_file-properties_file-lexer.patch ... [ ok ]
* Done with patching
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/codeblocks-9999-r16/work/codeblocks-9999 ...
* Running eautoreconf in '/var/tmp/portage/codeblocks-9999-r16/work/codeblocks-9999' ...
* Running aclocal ... [ ok ]
* Running libtoolize --copy --force --automake ... [ ok ]
* Running aclocal ... [ ok ]
* Running autoconf ... [ ok ]
* Running autoheader ... [ ok ]
* Running automake --add-missing --copy --foreign ... [ ok ]
* Running elibtoolize in: codeblocks-9999
* Applying max_cmd_len-1.5.0.patch ...
* Applying sed-1.5.6.patch ...
* Changing properties ...
Autoconf 2.50 or above is required. Aborting build...

!!! ERROR: dev-util/codeblocks-9999-r16 failed.
Call stack:
ebuild.sh, line 1545: Called dyn_compile
ebuild.sh, line 940: Called src_compile
codeblocks-9999-r16.ebuild, line 67: Called die

!!! Died in action: shipped bootstrap ...
!!! If you need support, post the topmost build error, and the call stack if relevant.

Bluespear · Posted: Sat Jul 08, 2006 9:19 am Post subject:

polygon7 · n00b Joined: 17 Dec 2005 Posts: 38

Tekel · Posted: Sat Jul 08, 2006 11:59 am Post subject:

I am having a hard time with x86_64 and GCC 4.1.0. I have actually managed to compile c::b but Now it is throwing erros while linking

simoaz · n00b Joined: 03 Dec 2004 Posts: 4

I installed the ebuild, no problem there.

However when i try to start the app, i get an error message like this:

~ $ codeblocks
Fatal Error: Mismatch between the program and library build versions detected.
The library used 2.6 (no debug,Unicode,compiler with C++ ABI 102,wx containers,compatible with 2.4),
and your program used 2.6 (no debug,Unicode,compiler with C++ ABI 1002,wx containers,compatible with 2.4).
Aborted

i see the difference in "compiler with c++ ABI 102,". I dont know what that means.

I reallize that i have probably used some wrong use flags, but i dont know what to change.

[ebuild R ] dev-util/codeblocks-9999-r16 USE="-contrib -debug -monolithic -static -unicode -vanilla -xrc" 0 kB [1]

no use flags on, anyone have any idees what to do?

I am pretty sure the installation went as it should; from the logs:
1152441526: ::: completed emerge (1 of 1) dev-util/codeblocks-9999-r16 to /
1152441526: *** Finished. Cleaning up...
1152441544: *** exiting successfully.
1152441545: *** terminating.

all ideas are welcome

update:

maybe its a good ide to show you my gcc useflags, something might be missing there as the error might suggest.

Calculating dependencies... done!
[ebuild R ] sys-devel/gcc-3.4.6-r1 USE="fortran nls -bootstrap -boundschecking -build -doc -gcj -gtk -hardened -ip28 -ip32r10k -multislot -nocxx -nopie -nossp -objc -vanilla"

Sincerly Simon

OnDraash · n00b Joined: 01 Feb 2006 Posts: 10

on my amd64 i get the following error with the latest r16:

Tekel · Posted: Thu Jul 13, 2006 2:25 pm Post subject:

This Ebuild needs to be marked somehow with not compatiable with GCC 4.1.x. There are known issues with GCC 4.1 not working. I don't know if portage has a method for that, but For the time being itshould be put in.

If you are having Errors and use GCC 4.1 you need to install a older version of GCC 4.0.x or 3.x.x

Also @OnDrash

Post your /var/tmp/portage/codeblocks-9999-r16/temp/aclocal-8471.out

OnDraash · n00b Joined: 01 Feb 2006 Posts: 10

i have the following:

first_slider · Posted: Thu Jul 13, 2006 5:36 pm Post subject:

Tekel · Posted: Thu Jul 13, 2006 9:26 pm Post subject:

Reemerge the auto tools. Other then that ????

OnDraash · n00b Joined: 01 Feb 2006 Posts: 10

does not help.

it seems to me that the file `revision.m4' is supposed to be part of the svn checkout, am i wrong?

WhiteDwarf · n00b Joined: 26 Oct 2003 Posts: 32 Location: Edmonton

Run ./bootstrap:

OnDraash · n00b Joined: 01 Feb 2006 Posts: 10

great, that helped. i just do not have enough experience with the svn checkout and emerge process, when should bootstrap be run a therefore where should i file a bugreport?

neuron · Advocate Joined: 28 May 2002 Posts: 2371

for those having problems with autoconf 2.6, just modify /usr/portage/distfiles/svn-source/codeblocks*/bootstrap to not do that check.

it's a simple bash file failing.

neuron · Advocate Joined: 28 May 2002 Posts: 2371

has anyone managed to build this on amd64+gcc4.1?

When I make it past the autoconf 2.6 problem I get this far:

Tekel · Posted: Sat Jul 15, 2006 3:16 am Post subject:

That error you are reporting is a known error. It also has a workaround on the C::B forums, you can look there for it, however I will tell you it compiles, links, and executes, but is entirly unuseable. Alot of features are borked. Untill they fix the inlineing issue it will not build on GCC 4.1 without revisions.

jshanab · Guru Joined: 22 Dec 2003 Posts: 359

I had the same issue here on AMD 64 as ondraash and solved it by moving the ./bootstrap line up before the ereconf in src_compile and re-digesting the ebuild. Nice wxWigets 2.6 !!!

Tekel · Posted: Sun Jul 16, 2006 1:29 am Post subject:

After switcing to gcc 3.4.6 building was no problem. Simple add FEATURES="keepwork" into make.conf then after first failed build run the bootstrap and It should build on a x86_64 gcc 4.1 based system