Indigo ros_core source compile error in actionlib_msgs

edit

I'm compiling indigo-ros_core from source on Debian and I'm getting stuck at actionlib_msgs with the following error:

<== Finished processing package [43 of 63]: 'std_msgs'

==> Processing catkin package: 'actionlib_msgs'
==> Building with env: '/opt/ros/indigo/env.sh'
==> cmake /home/crunchex/uproot/iso_catkin_ws/src/common_msgs/actionlib_msgs -DCATKIN_DEVEL_PREFIX=/home/crunchex/uproot/iso_catkin_ws/devel_isolated/actionlib_msgs -DCMAKE_INSTALL_PREFIX=/opt/ros/indigo -DCMAKE_BUILD_TYPE=Release -G Unix Makefiles in '/home/crunchex/uproot/iso_catkin_ws/build_isolated/actionlib_msgs'
-- Using CATKIN_DEVEL_PREFIX: /home/crunchex/uproot/iso_catkin_ws/devel_isolated/actionlib_msgs
-- Using CMAKE_PREFIX_PATH: /opt/ros/indigo
-- This workspace overlays: /opt/ros/indigo
-- Using PYTHON_EXECUTABLE: /usr/bin/python
-- Using Debian Python package layout
-- Using empy: /usr/bin/empy
-- Using CATKIN_ENABLE_TESTING: ON
-- Call enable_testing()
-- Using CATKIN_TEST_RESULTS_DIR: /home/crunchex/uproot/iso_catkin_ws/build_isolated/actionlib_msgs/test_results
-- Found gtest sources under '/usr/src/gtest': gtests will be built
-- Using Python nosetests: /usr/bin/nosetests-2.7
-- catkin 0.6.16
-- Using these message generators: gencpp;genlisp;genpy
CMake Error at /home/crunchex/uproot/iso_catkin_ws/build_isolated/actionlib_msgs/cmake/actionlib_msgs-genmsg.cmake:3 (message):
  Could not find messages which
  '/home/crunchex/uproot/iso_catkin_ws/src/common_msgs/actionlib_msgs/msg/GoalStatusArray.msg'
  depends on.  Did you forget to specify generate_messages(DEPENDENCIES ...)?

  Cannot locate message [Header] in package [std_msgs] with paths
  [['/home/crunchex/uproot/iso_catkin_ws/devel_isolated/std_msgs/share/std_msgs/cmake/../msg']]
Call Stack (most recent call first):
  /home/crunchex/uproot/iso_catkin_ws/devel_isolated/genmsg/share/genmsg/cmake/genmsg-extras.cmake:304 (include)
  CMakeLists.txt:12 (generate_messages)

At this point, I've already finished processing std_msgs, which is where the Header message is defined. So I'm not really sure why it would be failing at this point. Anyone have a clue?