Try a "make wipe" in ogre, it looks like the tarball didn't download
correctly.
Josh
On Fri, Apr 30, 2010 at 2:51 AM, Bob Mottram <
fuzzgun@gmail.com> wrote:
> On 29 April 2010 22:09, Josh Faust <jfaust@willowgarage.com> wrote:
> > Do you have the libogre-dev package installed? It may be getting the
> system
> > installed version confused with the custom one we build -- the official
> > ubuntu debs don't appear to have the CgProgramManager plugin.
> >
> > If you do, try uninstalling it and doing a make clean/make in the
> ogre_tools
> > and rviz packages.
>
>
> I did have libogre-dev installed, so I've uninstalled that.
> Attempting to make the ogre_tools package produces the following
> error:
>
> You don't have OGRE locally. I'm going to build it in ros-pkg.
> make[1]: Entering directory
> `/home/motters/ros/pkgs/visualization_common/ogre'
> mkdir -p build
> `rospack find rosbuild`/bin/download_checkmd5.py
> http://pr.willowgarage.com/downloads/ogre-v1-6-3.tar.bz2
> build/ogre-v1-6-3.tar.bz2
> touch -c build/ogre-v1-6-3.tar.bz2
> rm -rf build/ogre-v1-6-3 build/ogre
> cd build; tar xf ../build/ogre-v1-6-3.tar.bz2
>
> bzip2: Compressed file ends unexpectedly;
> perhaps it is corrupted? *Possible* reason follows.
> bzip2: Inappropriate ioctl for device
> Input file = (stdin), output file = (stdout)
>
> It is possible that the compressed file(s) have become corrupted.
> You can use the -tvv option to test integrity of such files.
>
> You can use the `bzip2recover' program to attempt to recover
> data from undamaged sections of corrupted files.
>
> tar: Unexpected EOF in archive
> tar: Unexpected EOF in archive
> tar: Error is not recoverable: exiting now
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
(text/plain)