Opened 9 years ago

Closed 9 years ago

Last modified 7 years ago

#9534 closed Bugs (fixed)

b2 emits link.jam No such file

Reported by: Richard <legalize@…> Owned by: Vladimir Prus
Milestone: To Be Determined Component: build
Version: Boost 1.55.0 Severity: Problem
Keywords: Cc:

Description

On a fresh download, having done bootstrap.bat on Windows, I get:

D:\Code\boost\boost_1_55_0

b2 --build-type=complete stage

link.jam: No such file or directory

Change History (17)

comment:1 by Richard <legalize@…>, 9 years ago

I'm using Visual Studio 2012 and Windows 7.

comment:2 by viboes, 9 years ago

Component: Building Boostbuild
Owner: set to Vladimir Prus

comment:3 by anonymous, 9 years ago

On MacOS, Compiling for iOS with llvm5.0 we have the same problem

comment:4 by Vladimir Prus, 9 years ago

This is a result of too-eager merge into release branch for 1.55, this problem does not exist in current git. Even in 1.55, this is just a diagnostic, and does not break anything.

So, unless I somehow misunderstood the problem, I'm gonna close this issue as wontfix.

comment:5 by Richard <legalize@…>, 9 years ago

Fine, although it sounds like you're saying it's already fixed, as opposed to won't be fixed.

comment:6 by Steven Watanabe, 9 years ago

Resolution: fixed
Status: newclosed

comment:7 by anonymous, 8 years ago

...

comment:8 by anonymous, 8 years ago

I've got the same error

comment:9 by anonymous, 8 years ago

Same error on Visual Studio 2012 and Windows 7 x86

comment:10 by anonymous, 8 years ago

Run the bootstarper as administrator in your build cmd environment. and run bjam as admin

comment:11 by manoj.patil@…, 8 years ago

I am getting same error on Ubantu.

link.jam: No such file or directory

comment:12 by Vladimir Prus, 8 years ago

Hi,

it should not be an error, just a warning, and the build should continue after that. Is that the case?

Also, it's fixed in git.

in reply to:  12 comment:13 by anonymous, 8 years ago

Replying to vladimir_prus:

Hi,

it should not be an error, just a warning, and the build should continue after that. Is that the case?

Also, it's fixed in git.

Thanks for the quick reply...

But i am getting an error like this -

Manoj@firstouch-Vostro-1540:~/mosesDemo/boost_1_55_0$ ./bjam --with-boost=~/workspace/temp/boost_1_55_0 -j8 link.jam: No such file or directory error: wrong library name 'boost=~/workspace/temp/boost_1_55_0' in the --with-<library> option.

comment:14 by Vladimir Prus, 8 years ago

The error you get is due to the --with-boost option - which does not exist, it's unrelated to link.jam.

What are you trying to accomplish with that option? If you want to use a different build directory, use --build-dir.

in reply to:  14 comment:15 by anonymous, 8 years ago

Replying to vladimir_prus:

The error you get is due to the --with-boost option - which does not exist, it's unrelated to link.jam.

What are you trying to accomplish with that option? If you want to use a different build directory, use --build-dir.

Hi,

I am following just steps described in document given below -

like -

tar zxvf boost_1_55_0.tar.gz cd boost_1_55_0/ ./bootstrap.sh

./b2 -j8 --prefix=$PWD --libdir=$PWD/lib64 --layout=system link=static install
echo FAILURE

Once boost is installed, you can then compile Moses. However, you must tell Moses where boost is with the --with-boost flag. This is the exact commands I use to compile Moses:

./bjam --with-boost=~/workspace/temp/boost_1_55_0 -j8

comment:16 by Vladimir Prus, 8 years ago

I am not familiar with what Moses is, but I believe the last command must be run from the source directory of Moses, and you appear to be running it from source of Boost C++ libraries. Could you go to source dir of Moses, and try this

    ~/workspace/temp/boost_1_55_0/b2 --with-boost=~/workspace/temp/boost_1_55_0 -j8

comment:17 by anonymous, 7 years ago

Thank you vladimir_prus. I got the same issue and have to exec bjam under the mosesdecoder folder, ex: cd /usr/local/src/mosesdecoder/ ./bjam --with-boost=/usr/local/src/boost_1_55_0 -j4

Note: See TracTickets for help on using tickets.