Opened 15 years ago

Closed 15 years ago

#1100 closed Bugs (fixed)

Building boost.function_types fails cvs rev-1.1, no chdir command in bash

Reported by: chris.fairles@… Owned by: t_schwinger
Milestone: Boost 1.35.0 Component: Building Boost
Version: Severity: Problem
Keywords: function_types build Cc:

Description

Checked out CVS trunk Friday July 20th. This error occured with boost function_types revision 1.1.

Built with command: ./tools/jam/src/bin.linux/bjam -sICU_PATH=/usr --layout=system variant=release debug-symbols=on --user-config=user-config.jam

user-config.jam had using gcc, python and mpi.

Error 

MkDir1 bin.v2/libs/function_types/build/gcc-4.1.1/release/debug-symbols-on/link-static
MkDir1 bin.v2/libs/function_types/build/gcc-4.1.1/release/debug-symbols-on/link-static/threading-multi
Jamfile</home/cfairles/repos/boost/libs/function_types/build>.wave /home/cfairles/repos/boost/libs/function_types/build/timestamps/arity_loops
/bin/sh: line 1: chdir: command not found
/bin/sh: line 2: /home/cfairles/repos/boost/dist/bin/wave: No such file or directory

  chdir /home/cfairles/repos/boost/libs/function_types/build 
  /home/cfairles/repos/boost/dist/bin/wave -S/home/cfairles/repos/boost libs/function_types/build/preprocess_arity_loops.cpp -o /home/cfairles/repos/boost/libs/function_types/build/timestamps/arity_loops

...failed Jamfile</home/cfairles/repos/boost/libs/function_types/build>.wave /home/cfairles/repos/boost/libs/function_types/build/timestamps/arity_loops...
Jamfile</home/cfairles/repos/boost/libs/function_types/build>.wave /home/cfairles/repos/boost/libs/function_types/build/timestamps/encoding
/bin/sh: line 1: chdir: command not found
/bin/sh: line 2: /home/cfairles/repos/boost/dist/bin/wave: No such file or directory

  chdir /home/cfairles/repos/boost/libs/function_types/build 
  /home/cfairles/repos/boost/dist/bin/wave -S/home/cfairles/repos/boost libs/function_types/build/preprocess_encoding.cpp -o /home/cfairles/repos/boost/libs/function_types/build/timestamps/encoding

...failed Jamfile</home/cfairles/repos/boost/libs/function_types/build>.wave /home/cfairles/repos/boost/libs/function_types/build/timestamps/encoding...
Jamfile</home/cfairles/repos/boost/libs/function_types/build>.wave /home/cfairles/repos/boost/libs/function_types/build/timestamps/cc_names
/bin/sh: line 1: chdir: command not found
/bin/sh: line 2: /home/cfairles/repos/boost/dist/bin/wave: No such file or directory

  chdir /home/cfairles/repos/boost/libs/function_types/build 
  /home/cfairles/repos/boost/dist/bin/wave -S/home/cfairles/repos/boost libs/function_types/build/preprocess_cc_names.cpp -o /home/cfairles/repos/boost/libs/function_types/build/timestamps/cc_names

...failed Jamfile</home/cfairles/repos/boost/libs/function_types/build>.wave /home/cfairles/repos/boost/libs/function_types/build/timestamps/cc_names...

Change History (4)

comment:1 by t_schwinger, 15 years ago

Milestone: To Be Determined → Boost 1.35.0
Owner: set to t_schwinger
Severity: Problem → Showstopper
Status: new → assigned

See ​http://article.gmane.org/gmane.comp.lib.boost.devel/163070

comment:2 by t_schwinger, 15 years ago

Severity: Showstopper → Problem

Full build of Boost should work again. The rest of the problem persists.

comment:3 by anonymous, 15 years ago

I'm not sure if something was reimplemented but I am experiencing the same problem and it is preventing the future linkage of serialization libraries that I need.

comment:4 by t_schwinger, 15 years ago

Resolution: → fixed
Status: assigned → closed

chdir has been removed, explicit has been added in case timestamps get messed up

Note: See TracTickets for help on using tickets.