[boost] [1.55.0] link.jam: No such file or directory

1,712 views
Skip to first unread message

Richard Hadsell

unread,
Mar 12, 2014, 2:44:09 PM3/12/14
to Boost
I am trying to build Boost 1.55 libraries with Clang 3.4 using g++ 4.8.2 as the toolchain on CentOS 6.5. When I run the command that I used for building 1.52.0, I get a message that seems to be harmless but indicates something has changed in the bjam options:

bin/bjam --user-config=user-config.LINUX_C65 threading=multi instruction-set=core2 address-model=64 variant=release link=static,shared --stagedir=stageC65 stage
link.jam: No such file or directory
...

What's up with that?

--

Dick Hadsell 203-992-6320 Fax: 203-992-6001
Reply-to: had...@blueskystudios.com
Blue Sky Studioshttp://www.blueskystudios.com
1 American Lane, Greenwich, CT 06831-2560

Follow Blue Sky Studios on Facebook <http://www.facebook.com/BlueSkyStudios> and Twitter <http://twitter.com/#%21/blueskystudios>

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Lars Viklund

unread,
Mar 12, 2014, 2:59:12 PM3/12/14
to bo...@lists.boost.org
On Wed, Mar 12, 2014 at 02:44:09PM -0400, Richard Hadsell wrote:
> link.jam: No such file or directory

It's normal and benign, albeit annoying.
It's part of the modularization shenanigans that snuck into the full
release ahead of time.

--
Lars Viklund | z...@acc.umu.se

Steven Watanabe

unread,
Mar 12, 2014, 3:08:08 PM3/12/14
to bo...@lists.boost.org
AMDG

On 03/12/2014 11:44 AM, Richard Hadsell wrote:
> I am trying to build Boost 1.55 libraries with Clang 3.4 using g++ 4.8.2
> as the toolchain on CentOS 6.5. When I run the command that I used for
> building 1.52.0, I get a message that seems to be harmless but indicates
> something has changed in the bjam options:
>
> bin/bjam --user-config=user-config.LINUX_C65 threading=multi
> instruction-set=core2 address-model=64 variant=release
> link=static,shared --stagedir=stageC65 stage
> link.jam: No such file or directory
> ...
>
> What's up with that?
>

It's harmless. It was caused by an overeager merge.
link.jam is needed for git.

In Christ,
Steven Watanabe
Reply all
Reply to author
Forward
0 new messages