[pkg-boost-devel] Package using boost.build v2

Paul van Tilburg paulvt at debian.org
Thu Jan 17 09:29:42 UTC 2008

Hello everyone,

Very recently I started working on a package, mcrl2, that uses 
boost.build v2 as its build & install system.  However, I ran into some
issues and I hope that you can advise me.

1) The upstream tarball ships boost under 3rd-party/boost.  This is
   quite a big chunk of source, namely 24MB.  Would you advise for or
   against creating a tarball without this part and use boost-build
   and/or bjam from Debian?

2) In debian/rules I perform (in different targets), the following

     % ./configure
        (creates build/{Makefile,config.jam})
     % make
        (which is: build/bin/bjam --prefix=/usr)
     % make install prefix=`pwd`/debian/tmp/usr
        (which is: build/bin/bjam --prefix=`pwd`/debian/tmp/usr --install)

   However, during the install phase, bjam for some reason relinks all
   the binaries and libraries to `pwd`/debian/tmp/usr, which I
   obviously do not want.  How can I prevent this?

3) When I submit the resulting package to lintian, lintian gives the
   following complaint:
     W: mcrl2: binary-or-shlib-defines-rpath ./usr/bin/chi2mcrl2

   How or where can I tell boost.build not to do the RPATH stuff?

Note that I am quite new at this boost.build system.  I know some
autotools, but haven't fully grasped what boost.build and bjam
are exactly doing.

N.B. If you want to have a look at the upstream tarball, see: 

Thanks in advance,

P.S. Please Cc me! I am not on this list (yet).

PhD Student @ Eindhoven                     | email: paulvt at debian.org
University of Technology, The Netherlands   | JID: paul at luon.net
>>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-boost-devel/attachments/20080117/bec0f84e/attachment.pgp 

More information about the pkg-boost-devel mailing list