Bug#728146: pd-iemambi: FTBFS on kfreebsd-*: #error No byte order defined

[Sebastian Ramacher]

On 2013-10-30 15:41:51, IOhannes m zmoelnig wrote:
> On 2013-10-30 15:12, Sebastian Ramacher wrote:
> >> could anybody please confirm that it pd-iemambi does (not) build
> >> on their kfreebsd-* systems?
> > 
> > I confirmed the build failure on fischer.d.o. Note that 
> > /usr/include/machine/endian.h guards the definition of BYTE_ORDER
> > and LITTLE_ENDIAN with #if __BSD_VISIBLE. __BSD_VISIBLE is not
> > defined and hence only the versions with leading underscores are
> > available.
> 
> thx.
> however, do you have an idea why it would *not* fail on my system?
> 
> also note that my <machine/endian.h> (as provided by
> kfreebsd-kernel-headers_9.2~4) does not have any protectors, but
> instead only includes machine-amd64/endian.h (or
> machine-i386/endian.h; depending on the actual architecture) which
> also don't have these protectors.

Oh, seems like I didn't update kfreebsd-kernel-headers and built with
the same version (9.0-something) as in the failed build on the buildds.
I've now successfully built it using the current kfreebsd-kernel-headers
version.

> 
> anyhow, i'd rather have the problem fixed. so what is the portable
> solution? should i simply define `__BSD_VISIBLE` for kfreebsd-*?

I guess it's best to ask the kfreebsd-porters about that. CCing them.

Regards
-- 
Sebastian Ramacher
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20131101/68a16112/attachment.sig>