Re: [ros-release] Build failed due to `ar`: command not foun…

Hi Tully,

Thank you very much for your reply and your suggestions.

I will add the binutils dependency first. Then, I will look into how to
rewrite the build system in CMake. I agree about the shortcomings of the
current method. The decision about not installing SDK related headers and
libraries has been made mainly due to complexity of directly using the
framework provided by SDK. I will look into this issue as well.

- Mani




Mani Monajjemi


On Wed, Feb 19, 2014 at 6:30 PM, Tully Foote <tfoote@osrfoundation.org>wrote:

> Hi Mani,
>
> The problem is that ar the executable is not installed. The immediate
> solution is to add add a build dependency on binutils.
>
> However you appear to be calling autotools from insde cmake. That's going
> to be fragile and is not recommended as it's not going to behave well in
> both the devel and install workspaces without quite a few hacks. (Such as
> forcing a rebuild every build) It's probably better to package the
> different package separately or quickly rewrite the build for the package
> in cmake. Note your current cmake does not install any of the SDK so it
> won't work when someone tries to use your installed packages if it needs
> either a library or header from the sdk.
>
> Tully
>
>
> On Wed, Feb 19, 2014 at 6:15 PM, Mani Monajjemi <mani.monajjemi@gmail.com>wrote:
>
>> Hello,
>>
>> This is the first time I am trying to release a package through ROS
>> infrastructure. The local Debian build succeeds, but the online build
>> keeps failing when trying to `ar` a group of object files for creating a
>> static library. The error message is:
>>
>> make[10]: /usr/lib/ccache/ar: Command not found
>>
>> For example here:
>> http://jenkins.ros.org/job/ros-hydro-ardrone-autonomy_binarydeb_precise_amd64/lastFailedBuild/console
>>
>> Looking into the [full] console output, I can see that the PATH is being
>> set as "/usr/lib/ccache:/usr/sbin:/usr/bin:/sbin:/bin" before running
>> `dpkg-buildpackage`. Does the error message imply that `ar` is not
>> installed at all on the build server (Usually `ar` is in /usr/bin which is
>> in the PATH)?
>>
>> Best,
>> Mani
>>
>>
>> _______________________________________________
>> ros-release mailing list
>> ros-release@code.ros.org
>> http://lists.ros.org/mailman/listinfo/ros-release
>>
>>
>
_______________________________________________
ros-release mailing list
ros-release@code.ros.org
http://lists.ros.org/mailman/listinfo/ros-release