I am compiling monotone with gcc 4.1.1 and it fails to build. The error reported is: x86_64-pc-linux-gnu-g++ -DNDEBUG -DBOOST_DISABLE_THREADS -DBOOST_SP_DISABLE_THREADS -O3 -march=k8 -fno-stack-protector -fno-strict-aliasing -fno-omit-frame-pointer -fno-strict-aliasing -Wall -Wl,-O1 -Wl,--enable-new-dtags -o monotone monotone-app_state.o monotone-commands.o monotone-diff_patch.o monotone-lua.o monotone-transforms.o monotone-update.o monotone-work.o monotone-cert.o monotone-database.o monotone-key_store.o monotone-file_io.o monotone-keys.o monotone-manifest.o monotone-packet.o monotone-sanity.o monotone-vocab.o monotone-rcs_file.o monotone-xdelta.o monotone-ui.o monotone-schema_migration.o monotone-constants.o monotone-netsync.o monotone-netcmd.o monotone-merkle_tree.o monotone-basic_io.o monotone-mkstemp.o monotone-lcs.o monotone-rcs_import.o monotone-revision.o monotone-change_set.o monotone-mt_version.o monotone-automate.o monotone-database_check.o monotone-epoch.o monotone-inodeprint.o monotone-selectors.o monotone-annotate.o monotone-restrictions.o monotone-hmac.o monotone-globish.o monotone-string_queue.o monotone-paths.o monotone-package_revision.o monotone-package_full_revision.o monotone-monotone.o monotone-main.o lib3rdparty.a libplatform.a -lz -ldl -lboost_regex -lboost_date_time -lboost_filesystem monotone-database.o: In function `Musing<hexenc<id> const>::gasp(std::basic_string<char, std::char_traits<char>, std::allocator<char> >&) const': database.cc:(.text._ZNK6MusingIK6hexencI2idEE4gaspERSs[Musing<hexenc<id> const>::gasp(std::basic_string<char, std::char_traits<char>, std::allocator<char> >&) const]+0x2e): undefined reference to `void dump<id>(hexenc<id> const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> >&)' monotone-database.o: In function `Musing<hexenc<id> >::gasp(std::basic_string<char, std::char_traits<char>, std::allocator<char> >&) const': database.cc:(.text._ZNK6MusingI6hexencI2idEE4gaspERSs[Musing<hexenc<id> >::gasp(std::basic_string<char, std::char_traits<char>, std::allocator<char> >&) const]+0x2e): undefined reference to `void dump<id>(hexenc<id> const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> >&)' collect2: ld returned 1 exit status make[2]: *** [monotone] Error 1 make[2]: Leaving directory `/var/tmp/portage/monotone-0.25/work/monotone-0.25' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/monotone-0.25/work/monotone-0.25' make: *** [all] Error 2 !!! ERROR: dev-util/monotone-0.25 failed. Call stack: ebuild.sh, line 1543: Called dyn_compile ebuild.sh, line 938: Called src_compile monotone-0.25.ebuild, line 39: Called die !!! Compilation failed !!! If you need support, post the topmost build error, and the call stack if relevant. I have rebuild my whole system with gcc 4.1.1 and this is the only package not compiling. I have done 'emerge -e system' and 'emerge -e world' twice, and it still fails to build. 'revdep-rebuild -pv' doesn't point out anything broken. It builds fine with 3.4.6.
output of "emerge --info" is missing, please file. :)
dup of bug 117572? Use a later version of monotone.
>> output of "emerge --info" is missing, please file. :) hehe...:) the latest version (0.29) compiles fine on amd64. Please close this bug. One thing I did note though was that it creates userid, group and directory before even starting the compile. I think it should be done in postinst rather than setup to avoid touching user's "/" if the install fails. But you are a better judge on that one.
(In reply to comment #3) > the latest version (0.29) compiles fine on amd64. Please close this bug. Great. > One thing I did note though was that it creates userid, group and directory > before even starting the compile. I think it should be done in postinst rather > than setup to avoid touching user's "/" if the install fails. But you are a > better judge on that one. Ideally yes that would be good. The user&group are used in src_install to change permission so it can't occur post install. One of the GLEPs aims to improve the user/group management of portage but it hasn't been implemented yet. *** This bug has been marked as a duplicate of 117572 ***
