$ chrpath --list /usr/lib64/libboost_*.1.58.0
/usr/lib64/libboost_atomic.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_chrono.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_container.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_context.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_coroutine.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_date_time.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_filesystem.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_graph.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_iostreams.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_locale.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_log_setup.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_log.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_math_c99f.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_math_c99l.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_math_c99.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_math_tr1f.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_math_tr1l.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_math_tr1.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_prg_exec_monitor.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_program_options.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_python.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_random.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_regex.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_serialization.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_signals.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_system.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_thread.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_timer.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_unit_test_framework.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_wave.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config
/usr/lib64/libboost_wserialization.so.1.58.0: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config

Problem still exists?

$ chrpath -l /usr/lib64/libboost_python.so
/usr/lib64/libboost_python.so: RPATH=/usr/lib:/usr/lib/python2.7/config:/usr/lib/python3.4/config

$ rpm -qa | grep boost-python3
boost-python3-devel-1.58.0-11.fc23.x86_64
boost-python3-1.58.0-11.fc23.x86_64

(In reply to Antonio Trande from comment #2)
> Problem still exists?

Yes that's why this bug report is still open, obviously.

This seems to have been caused by the fix for Bug 1102667

I'll have to delve into the horrible boost build system to figure out why linking to Python adds useless RPATHs, but the linkage to Python is definitely desirable.

If this can't be fixed in the build system, then it can be in the spec:

https://fedoraproject.org/wiki/Packaging:Guidelines#Removing_Rpath

Ah yes, that would work, although I have a fix for the boost build system.

Created attachment 1162537 [details]
Drop rpath (#1318383)

I wouldn't say this was directly caused by the fix for bug 1102667, but 
it did trigger Jam's previously dormant use of rpaths.  With this patch, 
only the MPI shared objects contain rpath entries, and those are generated 
not by this but by the mpich wrappers themselves.

Looks good, thanks!

I've pushed the fix to rawhide now.