Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rutorrent builds fails on develop head #4158

Closed
Strangelovian opened this issue Sep 1, 2020 · 2 comments
Closed

rutorrent builds fails on develop head #4158

Strangelovian opened this issue Sep 1, 2020 · 2 comments

Comments

@Strangelovian
Copy link
Contributor

For new Package Requests, see the guidelines

Setup

_Package Name: rutorrent
Package Version: develop head

NAS Model: any
NAS Architecture: all arch
DSM version: 6.1

Expected behavior

Should build on all arch

Actual behavior

Tell us what happens instead

Steps to reproduce

1. clone spksrc
2. run docker spkrc image
3. cd spk/ruttorent; make arch-x64

Other logs

Here the compile error with snippet:

wget https://github.com/rakshasa/libtorrent/archive/v0.13.6.tar.gz
2020-08-30 21:54:04 URL:https://codeload.github.com/rakshasa/libtorrent/tar.gz/v0.13.6 [340818] -> "libtorrent-0.13.6.tar.gz.part" [1]
...
===>  Extracting for libtorrent
tar -xzpf /spksrc/cross/libtorrent-rakshasa/../../distrib/libtorrent-0.13.6.tar.gz -C /spksrc/spk/rutorrent/work-x64-6.1
===>  Patching for libtorrent
aclocal...
configure.ac:22: warning: macro 'AM_PATH_CPPUNIT' not found in library
autoheader...
libtoolize... using libtoolize
automake...
configure.ac:3: installing './compile'
configure.ac:3: installing './config.guess'
configure.ac:3: installing './config.sub'
configure.ac:20: installing './install-sh'
configure.ac:20: installing './missing'
src/Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
autoconf...
configure.ac:22: error: possibly undefined macro: AM_PATH_CPPUNIT
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
@publicarray
Copy link
Member

Thanks for your report, Since #4209 is merged it should work again.

@Strangelovian
Copy link
Contributor Author

confirmed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants