and
> ? can/should i use the latter on kfreebsd-*?
is available on systems using kernel of FreeBSD.
is available on systems using Glibc.
As GNU/kFreeBSD is both things, you can have the one you prefer. Just
check for the component that provides it (i.e. __GLIBC__ or
__FreeBSD_kernel__) then
can see, starting with kfreebsd-kernel-headers 9.2~3 the
macros you want are defined unconditionally (by way of #include
). Maybe you just need a versioned B-D?
--
Robert Millan
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.
2011/11/15 Robert Millan :
> Note: patch is UNTESTED. I can test it but not right now. Maybe in
> ~12 hours if noone beats me to it.
Grmf. Now it fails to build somewhere else, presumably due to xulrunner update.
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../.. -I../../include
-I../../i
s. However now that libv4l-dev is available
on GNU/kFreeBSD, it's probably better to include the other plugin as
well. E.g. see attached patch.
Note: patch is UNTESTED. I can test it but not right now. Maybe in
~12 hours if noone beats me to it.
--
Robert Millan
=== modified file 'd
out breaking things!
In case you're wondering, just go ahead and install that file ;-)
--
Robert Millan
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mai
ldn't be included directly anyway,
it is dragged in by . On GNU/kFreeBSD, drags in
, so this problem can be solved simply by including
unconditionally.
--
Robert Millan
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-ma
ad, which does the right thing on each
platform.
--
Robert Millan
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Note that this FTBFS only happens on i386.
--
Robert Millan
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Package: libquicktime
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in libquicktime uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Dep
Package: xjadeo
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in xjadeo uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo
Package: brutefir
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in brutefir uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: li
Package: mixxx
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in mixxx uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo-d
Package: mplayer
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in mplayer uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libf
Package: snd
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in snd uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo-dev [
Package: bitmeter
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in bitmeter uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: li
Package: vlc
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in vlc uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo-dev [
Package: phasex
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in phasex uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo
Package: mhwaveedit
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in mhwaveedit uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends
Package: cmus
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in cmus uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo-dev
Package: gjacktransport
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in gjacktransport uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build
Package: ices2
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in ices2 uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo-d
Package: amsynth
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in amsynth uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libf
Package: stk
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in stk uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo-dev [
Package: audacious-plugins
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in audacious-plugins uses a negated list of
architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: sndobj
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in sndobj uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo
Package: csound
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in csound uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo
Package: libav
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in libav uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo-d
Package: jamin
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in jamin uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo-d
Package: lives
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in lives uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo-d
Package: jack-audio-connection-kit
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in jack-audio-connection-kit uses a negated list of
architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e.
Package: audacity
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in audacity uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: li
Package: fluidsynth-dssi
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in fluidsynth-dssi uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Bui
Package: jackd2
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in jackd2 uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Build-Depends: libfoo
Package: ardour
Version: 1:2.8.11-6
Severity: wishlist
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd
Please consider this patch so that ardour is buildable on future ports of
Debian GNU/kFreeBSD (such as the upcoming kfreebsd-mipsel).
-- System Information:
Debian Release: whee
build system to stop
>> doing so on kFreeBSD. Probably not that much work, but I'm too busy with
>> other stuff right now.
>
> Proposed patch is in #612480.
kFreeBSD 8.2 has v4l already, its header is in
sys/compat/linux/linux_videodev.h
Shouldn't we provid
Package: mplayer
Version: 2:1.0~rc3++final.dfsg1-1
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd
mplayer.conf defaults to:
# Use pulse, then alsa, then SDL video with the aalib subdriver by default.
ao=pulse,alsa,sdl:aalib
but "alsa" backend is Linux-only. On
36 matches
Mail list logo
