[git] "headers" target fails
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I see the same error that Vicente reported yesterday, when trying to follow the wiki approach to the modularised boost: Monty: ~/programming/boost +[git:master] → ./b2 headers link.jam: No such file or directory Jamroot:145: in modules.load ERROR: rule "link-directory" unknown in module "Jamfile". /home/brian/programming/boost/tools/build/v2/build/project.jam:311: in load-jamfile /home/brian/programming/boost/tools/build/v2/build/project.jam:64: in load /home/brian/programming/boost/tools/build/v2/build/project.jam:145: in project.find /home/brian/programming/boost/tools/build/v2/build-system.jam:535: in load /home/brian/programming/boost/tools/build/v2/kernel/modules.jam:289: in import /home/brian/programming/boost/tools/build/v2/kernel/bootstrap.jam:139: in boost-build /home/brian/programming/boost/boost-build.jam:17: in module scope Monty: ~/programming/boost +[git:master] → I don't think we can blame retention on the convert script anymore. Regards, /Brian Ravnsgaard Riis -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJScU45AAoJEFES4N8QrEod+wIH/RYF/GpB0nh+T6/fYEP6iQSO l8XVA0dyPuFx/LY9eLZFYFVQlJut7EJYujk3SUSqN3UUmphmnm2yNPeYkIzNMUzz 07PYvs9/2n74dWsJkfusxbvwXLcuBbGQlMfmaDsKj3UTjdUScrD3dFjH3fyhC5Il gvyH68YyWkX1V3at09hCyqplslum70WT2HAJty4ra+sXfxcbqSq95N6YdvOkbYRD QGjlpAABxdtLym9WzEekQV+H32t7T/CzqRw8Ay4n89DeFNI7T/1twOtCFVZjwtVG JbFVpDCjUtKpLBEqSwP5WkdcAbXmHYD2MuhhaK1tYAuXkPT1Uz1PrL23D0ZB2BA= =iiDy -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-10-30 19:21, Brian Ravnsgaard Riis wrote:
Hi,
I see the same error that Vicente reported yesterday, when trying to follow the wiki approach to the modularised boost:
Monty: ~/programming/boost +[git:master] → ./b2 headers link.jam: No such file or directory Jamroot:145: in modules.load ERROR: rule "link-directory" unknown in module "Jamfile". /home/brian/programming/boost/tools/build/v2/build/project.jam:311: in load-jamfile /home/brian/programming/boost/tools/build/v2/build/project.jam:64: in load /home/brian/programming/boost/tools/build/v2/build/project.jam:145: in project.find /home/brian/programming/boost/tools/build/v2/build-system.jam:535: in load /home/brian/programming/boost/tools/build/v2/kernel/modules.jam:289:
in import
/home/brian/programming/boost/tools/build/v2/kernel/bootstrap.jam:139:
in boost-build
/home/brian/programming/boost/boost-build.jam:17: in module scope
Monty: ~/programming/boost +[git:master] →
I don't think we can blame retention on the convert script anymore.
Regards, /Brian Ravnsgaard Riis
Indeed, there is no such rule. Monty: ~/programming/boost +[git:master] → grep -r "link-directory" . ./Jamroot: link-directory $(dir)-headers : libs/$(dir)/include/boost : <location>. ; ./Jamroot: link-directory numeric-$(dir)-headers : libs/numeric/$(dir)/include/boost : <location>. ; Regards, /Brian Ravnsgaard Riis -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJScVH4AAoJEFES4N8QrEodCBYH/iJFfjQPAyOcvSDvo1KhQvPc Qsw2W+YXSeQoxPrXkra8koGBUrwrkjbGdYMIeCsUXyt/KC7YriqiBLyAUEkBh2aT 9rMQp3qeyroDnH5jroX5Aq27fWF8GQhXUcJGjHKRBDpUAYz5pkkPSpkhSa8lFg4a kLc26GEDcwPqXe5q6POBlJuvbjnAc3yvy+ZJ3blwsA9m0T/CEi1Ia1KGYJ6YwEFI sIt3dKEhSHMF89yym/ipyedUMX7oZ1r3EoFFf8NQYxBCknjkzwN95qj2Xou5RDAu bfT2tXb0b2rUMVfoS1QOPVxhts6QObprN0OfXfeXICjEwi8qLcAcIRuLi17ub04= =89uA -----END PGP SIGNATURE-----
AMDG On 10/30/2013 11:21 AM, Brian Ravnsgaard Riis wrote:
Hi,
I see the same error that Vicente reported yesterday, when trying to follow the wiki approach to the modularised boost:
Monty: ~/programming/boost +[git:master] ? ./b2 headers link.jam: No such file or directory Jamroot:145: in modules.load ERROR: rule "link-directory" unknown in module "Jamfile". /home/brian/programming/boost/tools/build/v2/build/project.jam:311: in load-jamfile /home/brian/programming/boost/tools/build/v2/build/project.jam:64: in load /home/brian/programming/boost/tools/build/v2/build/project.jam:145: in project.find /home/brian/programming/boost/tools/build/v2/build-system.jam:535: in load /home/brian/programming/boost/tools/build/v2/kernel/modules.jam:289: in import /home/brian/programming/boost/tools/build/v2/kernel/bootstrap.jam:139: in boost-build /home/brian/programming/boost/boost-build.jam:17: in module scope
Monty: ~/programming/boost +[git:master] ?
I don't think we can blame retention on the convert script anymore.
There are significant unmerged changes to Boost.Build in the trunk, which are necessary for the modularized build to work. I'm not about to merge them until after the release ships. In Christ, Steven Watanabe
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-10-30 19:48, Steven Watanabe wrote:
AMDG
On 10/30/2013 11:21 AM, Brian Ravnsgaard Riis wrote:
Hi,
I see the same error that Vicente reported yesterday, when trying to follow the wiki approach to the modularised boost:
Monty: ~/programming/boost +[git:master] ? ./b2 headers link.jam: No such file or directory Jamroot:145: in modules.load ERROR: rule "link-directory" unknown in module "Jamfile". /home/brian/programming/boost/tools/build/v2/build/project.jam:311: in load-jamfile /home/brian/programming/boost/tools/build/v2/build/project.jam:64: in load /home/brian/programming/boost/tools/build/v2/build/project.jam:145: in project.find /home/brian/programming/boost/tools/build/v2/build-system.jam:535: in load /home/brian/programming/boost/tools/build/v2/kernel/modules.jam:289:
in import
/home/brian/programming/boost/tools/build/v2/kernel/bootstrap.jam:139:
in boost-build
/home/brian/programming/boost/boost-build.jam:17: in module scope
Monty: ~/programming/boost +[git:master] ?
I don't think we can blame retention on the convert script anymore.
There are significant unmerged changes to Boost.Build in the trunk, which are necessary for the modularized build to work. I'm not about to merge them until after the release ships.
In Christ, Steven Watanabe
Hi, That'll explain it. I'll try to nose around on my own... :-) Regards, /Brian Ravnsgaard Riis -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJScVgbAAoJEFES4N8QrEodsMQH/3dk+5LmrMENdegqefdFev3M rEReWQkN0FXph6crs5JMqOIEyh7TaGj7gFYQPDTJTY5YP/cN+o17oYo9trLNiDFq 6k1Yk5UUrlBOceHRk+tBz7FOv3CSr4g3DwDe+F9L6gWThnPOS5kcUGWwzJke7vWu gUZTomhQHMGNtdMw0pFIvu17I4ssS5cD5iheAw9gVXoDhhUE0yFQl+/NBrD1hFir iDkLBjx6PnhbPJh04aUy3zGPMO4C4FuD3vzDdU3W+qpM3VgTk+8bqaA7FrEb4H0u ngVKYhAjjky6WDoReYRlqHxFWsg7ynsxGd8velTUuD7jnzdnVQCtL1Q9JkWrk9k= =0yco -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-10-30 20:03, Brian Ravnsgaard Riis wrote:
Hi,
That'll explain it. I'll try to nose around on my own... :-)
Regards, /Brian Ravnsgaard Riis
Hi list, So, for now the solution seems pretty simple. Here's how I proceeded: $ git clone --recursive git://github.com/boostorg/boost modular-boost $ cd modular-boost/tools/build $ git checkout develop $ cd v2 $ ./bootstrap.sh --with-toolset=clang $ sudo ./b2 --prefix=/usr/local $ cd ../../.. $ ./bootstrap.sh --with-toolset=clang $ ./b2 headers $ ./b2 stage Lines 4-6 are for installing Boost.Build to a system location. Omit as you please. Also, I use clang; substitute your favourite toolset and add options as you usually would. The above sequence worked for me. (Well, I think... It's still compiling...) Regards, /Brian Ravnsgaard Riis -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJScVvsAAoJEFES4N8QrEodeTkH/0OgN2VZbROQv+qYcoza7BOc pNCFeADZBE07CrH2ksPZsFcEv496JIjT9egQMl5/ntbHeacOaMaqoZNuUGU+AWY5 z+VzrX/7gl6lBVDxu16XHWughc+S+3pXtX4mlZFp+ThRSQv+U20qdVd0roT20yRK PMF5JIuq6I8h5/nIdtGsJDD9Bcfw0DvQQamRJu14udgRMfoSquRbOQ/j8T4nI+Pa ms1X54ZzloIFoQxJuQOh3p7sP2OY/ls6TBrD/g3Kx+79zIduzg3Z21gVOAJuqf7i pPc47PIlbiEFFfyoC/shNWBv5z/c+1NZ8bUBvdKSDJz5RVnkQVNKTJ6G9RcpJkM= =kc0Z -----END PGP SIGNATURE-----
Le 30/10/13 20:20, Brian Ravnsgaard Riis a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2013-10-30 20:03, Brian Ravnsgaard Riis wrote:
Hi,
That'll explain it. I'll try to nose around on my own... :-)
Regards, /Brian Ravnsgaard Riis Hi list,
So, for now the solution seems pretty simple. Here's how I proceeded:
$ git clone --recursive git://github.com/boostorg/boost modular-boost $ cd modular-boost/tools/build $ git checkout develop $ cd v2 $ ./bootstrap.sh --with-toolset=clang $ sudo ./b2 --prefix=/usr/local $ cd ../../.. $ ./bootstrap.sh --with-toolset=clang $ ./b2 headers $ ./b2 stage
Lines 4-6 are for installing Boost.Build to a system location. Omit as you please.
Also, I use clang; substitute your favourite toolset and add options as you usually would.
The above sequence worked for me. (Well, I think... It's still compiling...)
Thanks, it's compiling for me also :) Vicente
participants (3)
-
Brian Ravnsgaard Riis -
Steven Watanabe -
Vicente J. Botet Escriba