# Boost recipe in pybombs

**URL:** <https://www.ruby-forum.com/t/boost-recipe-in-pybombs/245933>\
**Category:** GNU Radio\
**Created:** [August 1, 2013, 8:17pm UTC](https://www.ruby-forum.com/t/boost-recipe-in-pybombs/245933 "2013-08-01T20:17:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rafa\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/958977/32.png) [@Rafa\_F](https://www.ruby-forum.com/u/Rafa_F)\
**Post date:** [August 1, 2013, 8:17pm UTC](https://www.ruby-forum.com/t/boost-recipe-in-pybombs/245933/1 "2013-08-01T20:17:40Z")

</div>

The boost recipe in pybombs builds using the --layout=tagged option  
which will generate libraries with the -mt suffix. The ‘mt’ stands  
for multi threaded and is only available for historical reasons,I  
suppose.

Is there any particular reason for using this optionin pybombs? There  
are some linux distributions that have abandoned the -mt suffix and  
gnuradio builds just fine on those. Ubuntu still uses the -mt suffix  
but also creates softlinks without the suffix, so it is safe for an  
application to only link to libboost-xyz without the suffix.

Alex

---

<div class="post-metadata">

**Author:** ![copot](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/49beb7/32.png) [@copot](https://www.ruby-forum.com/u/copot)\
**Post date:** [August 3, 2013, 1:37am UTC](https://www.ruby-forum.com/t/boost-recipe-in-pybombs/245933/2 "2013-08-03T01:37:01Z")

</div>

Tim,

Thanks for the clarification.  
I’ll see what I can come up with for gqrx so that is can be built both  
with and without the -mt suffix.

Alex

---

<div class="post-metadata">

**Author:** ![copot](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/49beb7/32.png) [@copot](https://www.ruby-forum.com/u/copot)\
**Post date:** [August 1, 2013, 9:59pm UTC](https://www.ruby-forum.com/t/boost-recipe-in-pybombs/245933/3 "2013-08-01T21:59:55Z")

</div>

Alex,

This is set because of the unfortunate way some version of  
FindBoost.cmake are written  
the order it searches for libs can look something like

1. check for libboostfoo-mt.so in $BOOST\_ROOT
2. check for libboostfoo-mt.so in /usr/lib/
3. check for libboostfoo.so in $BOOST\_ROOT
4. check for libboostfoo.so in /usr/lib/

A result of this is that if you build without the -mt tag, and you are  
on a distro that has an older version of boost installed into /usr/lib/  
system paths - $BOOST\_ROOT will be ignored because it checks all the  
search directories for each library naming case in an unfortunate order.  
So building with -mt every time to ensures FindBoost.cmake picks up the  
right prefixed boost library (if built from source) every time when  
building other recipes that use boost & cmake.

-Tim