Thank you Adam for testing my package.
Can you send me the build log, so I can analyse the problem?
I have been building my package on my Debian/Testing machine without
problems. Are you using a different build environment? What is the minimum
required build environment (except for the build dependencies)?
Regards,
Vincent
Op wo 22 sep. 2021 om 14:57 schreef Adam Borowski <kilob...@angband.pl>:
> On Mon, Sep 20, 2021 at 07:16:30PM +0200, Vincent Smeets wrote:
> > * Package name : binutils-m68hc1x
>
> > Changes since the last upload:
> >
> > binutils-m68hc1x (1:3) unstable; urgency=medium
> > .
> > * Repackaged as a native package based on binutils-source (Closes:
> #982848)
>
> Fails to build with:
>
> cd obj-x86_64-linux-gnu && ../src/configure
> --build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include
> --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info
> --sysconfdir=/etc --localstatedir=/var --disable-option-checking
> --disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu
> --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking
> --target=m68hc11 --libdir=\${prefix}/lib/m68hc11 --with-bugurl=
> https://www.debian.org/Bugs/ --with-system-zlib
> --with-pkgversion=1:2.37\+3 --enable-deterministic-archives
> --enable-targets=m68hc11,m68hc12
> configure: error: unrecognized option: `--runstatedir=/run'
>
>
> Meow!
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ If you ponder doing what Jesus did, remember than flipping tables
> ⢿⡄⠘⠷⠚⠋⠀ and chasing people with a whip is a prime choice.
> ⠈⠳⣄⠀⠀⠀⠀
>
