Bug#424038: [pkg-boost-devel] problem for libraries names between ax_boost.m4 and debian packages

2007-05-27 Thread Domenico Andreoli 
On Fri, May 25, 2007 at 08:53:08PM +0200, Gauthier Quesnel wrote:
 Hi all,

hi,
 
 The ax_boost.m4 script does not detect the correct library because the
 debian libraries names are not defined in the script. Now, my
 question:
   what is the best way to correct this ?
   * modify the ax_boost*.m4 script or
   * modify the debian packages ?
   :-)

of course fix the ax_boost*.m4 script :)

please have a look at [0]. yes, it is difficult to believe, but currently
there is no portable way to guess boost library names.

when they started to make such crazy names i provided commodity links
for mortal people, these are the real debian library names, but they
are not portable across linux distributions. i even provided default
links to multi-thread libraries, but it was an arbitrary choice i now
regret to have done.

until few days ago i thought bjam/boost-build could be used to portably
link boost libraries but i was wrong. these names are built in Jamfile.v2
at the root of boost source tree and there is no way to make boost-build
tell you which are they once you are out of the boost source tree.

cheers
domenico

[0] http://www.boost.org/more/getting_started/unix-variants.html#library-naming

-[ Domenico Andreoli, aka cavok
 --[ http://www.dandreoli.com/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#424038: [pkg-boost-devel] problem for libraries names between ax_boost.m4 and debian packages

2007-05-27 Thread Gauthier Quesnel 
Domenico Andreoli a écrit :
 On Fri, May 25, 2007 at 08:53:08PM +0200, Gauthier Quesnel wrote:
 [...]
  The ax_boost.m4 script does not detect the correct library because
  the debian libraries names are not defined in the script. Now, my
  question:
  what is the best way to correct this ?
  * modify the ax_boost*.m4 script or
  * modify the debian packages ?
  :-)
 of course fix the ax_boost*.m4 script :)

I suspected it  :-D

 please have a look at [0]. yes, it is difficult to believe, but
 currently there is no portable way to guess boost library names.

ok.

 when they started to make such crazy names i provided commodity links
 for mortal people, these are the real debian library names, but they
 are not portable across linux distributions. i even provided default
 links to multi-thread libraries, but it was an arbitrary choice i now
 regret to have done.

ok ok. I did not know this policy of libraries names. 

 until few days ago i thought bjam/boost-build could be used to
 portably link boost libraries but i was wrong. these names are built
 in Jamfile.v2 at the root of boost source tree and there is no way to
 make boost-build tell you which are they once you are out of the
 boost source tree.

Ok ok. Thank you for all these precise details.

Now a new problem with the main function of the boost unit
framework: :-(

#include boost/test/unit_test.hpp
using namespace boost::unit_test_framework;

void my_test_function()
{ }

test_suite* init_unit_test_suite( int argc, char* argv[] )
{
test_suite* test = BOOST_TEST_SUITE( Master test suite );   
test-add( BOOST_TEST_CASE( my_test_function ) );
return test;
}

The commands:
$ g++ test.cc -lboost_unit_test_framework-mt
or
$ g++ test.cc -lboost_unit_test_framework-st

return:
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/crt1.o: In
function `_start': (.text+0x18): undefined reference to `main'
collect2: ld a retourné 1 code d'état d'exécution

This function (main) must be provided by the libboost-test1.34 [1].



Gauthier.

|1] http://www.boost.org/libs/test/doc/components/utf/index.html#Example


 cheers
 domenico
 
 [0]
 http://www.boost.org/more/getting_started/unix-variants.html#library-naming
 
 -[ Domenico Andreoli, aka cavok
  --[ http://www.dandreoli.com/gpgkey.asc
---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50