Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#62196 - [tepl] doesn't build due to automatic dependency tracking being enabled
Attached to Project:
Community Packages
Opened by Andreas Baumann (andreas_baumann) - Sunday, 31 March 2019, 07:35 GMT
Last edited by Balló György (City-busz) - Sunday, 31 March 2019, 08:26 GMT
Opened by Andreas Baumann (andreas_baumann) - Sunday, 31 March 2019, 07:35 GMT
Last edited by Balló György (City-busz) - Sunday, 31 March 2019, 08:26 GMT
|
DetailsDescription:
config.status: error: in `/build/tepl/src/tepl': config.status: error: Something went wrong bootstrapping makefile fragments for automatic dependency tracking. Try re-running configure with the '--disable-dependency-tracking' option to at least be able to build the package (albeit without support for automatic dependency tracking). added the following to prepare(): ./configure --prefix=/usr --enable-gtk-doc --disable-Werror --disable-dependency-tracking results in: Makefile:1008: *** missing separator. Stop. @CODE_COVERAGE_RULES@ which is a non-expanded macro. To me it's not clear how this package ever built in the past.. Additional info: * package version(s): 4.2.0-1 Steps to reproduce: asp export tepl cd tepl staging-x86_64-build |
This task depends upon
Closed by Balló György (City-busz)
Sunday, 31 March 2019, 08:26 GMT
Reason for closing: Fixed
Additional comments about closing: tepl 4.2.0-2
Sunday, 31 March 2019, 08:26 GMT
Reason for closing: Fixed
Additional comments about closing: tepl 4.2.0-2
Comment by Balló György (City-busz) -
Sunday, 31 March 2019, 08:25 GMT
Maybe it's related to an update of autoconf-archive. Now I swiched to the released tarball, which does not need to run autogen.sh.