Bug 619869

gnash build also encountered that issue: http://koji.fedoraproject.org/koji/getfile?taskID=2357337&name=build.log

(In reply to comment #1)
> gnash build also encountered that issue:
> http://koji.fedoraproject.org/koji/getfile?taskID=2357337&name=build.log    
Which is part of the gnash build task: http://koji.fedoraproject.org/koji/taskinfo?taskID=2357337

New package version (1.44.0-0.4) for Rawhide builds cleanly: http://koji.fedoraproject.org/koji/taskinfo?taskID=2369563
And for F14: http://koji.fedoraproject.org/koji/buildinfo?buildID=2370110

It should solve the issue (once the new version makes its way to the repository).

boost-1.44.0-0.4.fc14 has been submitted as an update for Fedora 14.
http://admin.fedoraproject.org/updates/boost-1.44.0-0.4.fc14

boost-1.44.0-0.4.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update boost'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/boost-1.44.0-0.4.fc14

Hi Orion,

The fixed boost is tagged into the buildroot on F-14. Could you give it another kick?

Thanks.

This looks to be fixed now:
http://koji.fedoraproject.org/koji/buildinfo?buildID=187644

I checked the build logs: boost 1.44 is found

I'm seeing this, or something like this currently on wesnoth:

hecking boost/iostreams/device/file_descriptor.hpp usability... yes
checking boost/iostreams/device/file_descriptor.hpp presence... yes
checking for boost/iostreams/device/file_descriptor.hpp... yes
checking for the Boost iostreams library... configure: error: Cannot compile a test that uses Boost iostreams
error: Bad exit status from /var/tmp/rpm-tmp.979rIy (%build)
    Bad exit status from /var/tmp/rpm-tmp.979rIy (%build)
RPM build errors:
Child returncode was: 1
EXCEPTION: Command failed. See logs for output.
 # ['bash', '--login', '-c', 'rpmbuild -bb --target i686 --nodeps builddir/build/SPECS/wesnoth.spec']
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/mock/trace_decorator.py", line 70, in trace
    result = func(*args, **kw)
  File "/usr/lib/python2.6/site-packages/mock/util.py", line 333, in do
    raise mock.exception.Error, ("Command failed. See logs for output.\n # %s" % (command,), child.returncode)
Error: Command failed. See logs for output.
 # ['bash', '--login', '-c', 'rpmbuild -bb --target i686 --nodeps builddir/build/SPECS/wesnoth.spec']
LEAVE do --> EXCEPTION RAISED

(In reply to comment #8)
> I'm seeing this, or something like this currently on wesnoth:
> [...]

Could open another bug request, as it seems you have a different issue here?

Thanks in advance

(In reply to comment #9)
> Could open another bug request => Could you open another bug request

BTW, the failed build can be seen on Koji: http://koji.fedoraproject.org/koji/taskinfo?taskID=2376730

From what I see in the wesnoth build log (http://koji.fedoraproject.org/koji/getfile?taskID=2376730&name=build.log), it appears to come from an Autotools-related issue (the configure script is not able to retrieve Boost.IOStreams). Upstream (wesnoth) suggests to use/try scons and/or CMake, instead of the Autotools. It can be a good opportunity to give it a try.

Otherwise, I suggest that you compare wesnoth's configure scripts (configure.ac and ??boost??.m4 M4 macro files) with those of working packages (paraview, glob2, rmol, etc.)

boost-1.44.0-0.4.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.