barada-pam version 0.5-1ubuntu1 failed to build on i386

Bug #765927 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
barada-pam (Ubuntu)
Fix Released
High
Unassigned

Bug Description

barada-pam version 0.5-1ubuntu1 failed to build on i386
Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110413/+buildjob/2446148

Direct link to the build log: https://launchpad.net/ubuntu/+archive/test-rebuild-20110413/+buildjob/2446148/+files/buildlog_ubuntu-natty-i386.barada-pam_0.5-1ubuntu1_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 971 lines into the build log:

barada-add.o: In function `boost::enable_if<boost::filesystem::is_basic_path<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >, bool>::type boost::filesystem::is_directory<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >(boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> const&)':
/usr/include/boost/filesystem/operations.hpp:303: undefined reference to `boost::filesystem::detail::status_api(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, boost::system::error_code&)'
barada-add.o: In function `boost::enable_if<boost::filesystem::is_basic_path<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >, bool>::type boost::filesystem::create_directory<boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> >(boost::filesystem::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem::path_traits> const&)':
/usr/include/boost/filesystem/operations.hpp:423: undefined reference to `boost::filesystem::detail::create_directory_api(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
barada-add.o: In function `__static_initialization_and_destruction_0':
/usr/include/boost/system/error_code.hpp:208: undefined reference to `boost::system::get_system_category()'
/usr/include/boost/system/error_code.hpp:209: undefined reference to `boost::system::get_generic_category()'
/usr/include/boost/system/error_code.hpp:214: undefined reference to `boost::system::get_generic_category()'
/usr/include/boost/system/error_code.hpp:215: undefined reference to `boost::system::get_generic_category()'
/usr/include/boost/system/error_code.hpp:216: undefined reference to `boost::system::get_system_category()'
collect2: ld returned 1 exit status
make[1]: *** [barada-add] Error 1
make[1]: Leaving directory `/build/buildd/barada-pam-0.5'
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110419-0240
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/barada-pam-0.5

Tags: ftbfs oneiric

Related branches

Matthias Klose (doko)
Changed in barada-pam (Ubuntu):
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package barada-pam - 0.5-2ubuntu1

---------------
barada-pam (0.5-2ubuntu1) oneiric; urgency=low

  * debian/patches/fix_ftbfs_dso.patch: (LP: #765927)
    - really fix FTBFS with gold/--no-add-needed

barada-pam (0.5-2) unstable; urgency=low

  * Convert to 3.0 (quilt) source format
  * debian/control: bump Standards-Version (no changes)
  * Add patch from Andreas Moog to fix FTBFS with gold or ld --no-add-needed
    (closes: #615696)
 -- Andreas Moog <email address hidden> Sat, 28 May 2011 17:07:50 +0200

Changed in barada-pam (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.