[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#817757: motion: FTBFS on kfreebsd-amd64: #error This header is not available for amd64

tags 817757 + patch
user debian-bsd@lists.debian.org
usertags 817757 + kfreebsd


Andreas Beckmann wrote:
> motion FTBFS on kfreebsd-amd64 (but not on kfreebsd-i386), after
> the -6 and -7 versions successfully built there:
> https://buildd.debian.org/status/fetch.php?pkg=motion&arch=kfreebsd-amd64&ver=3.2.12%2Bgit20140228-8&stamp=1453308422

> /usr/include/x86_64-kfreebsd-gnu/machine/ioctl_meteor.h:8:3: error: #error This header is not available for amd64
>  # error This header is not available for amd64
>    ^

The FreeBSD <machine/ioctl_*.h> headers have been deprecated for a long
time.  motion only tries to use those because this configure check
fails now:

| checking bktr headers in /usr/include/dev/bktr...no

That broke because we recently moved kfreebsd headers to multiarch
paths, e.g. /usr/include/x86_64-kfreebsd-gnu/dev/bktr/ioctl_*.h

A lot of the configure.in checks look at hard-coded include paths
(like the ffmpeg and pgsql checks, which had to be overridden
already on the configure command line).

I've attached a quick and easy fix for this, but it's not suitable to go

The correct fix would use some autoconf macro to runs the build
architecture compiler, and check for the existence of those headers in
the compiler's include search paths.  But possibly, OLD_BKTR is so old
that it could be removed altogether, so it's probably not worth doing.

Steven Chamberlain

Attachment: signature.asc
Description: Digital signature

Reply to: