Hi everyone,
I am part of the group of MIPS porters, and we missed to officially
respond to this email. Here is for the record:
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the jessie release:
For MIPS,MIPSEL,MIPS64,MIPS64EL, I
On 31/10/2013 22:02, Steven Chamberlain wrote:
> On 31/10/13 19:53, Robert Millan wrote:
+#ifndef INADDR_PFSYNC_GROUP
+#define INADDR_PFSYNC_GROUP (uint32_t)0xf0e0
+#endif
>
>> This is an IPv4 address right? Any idea what is it used for? What's
>> special about packets sent to
Hi everyone,
I am part of the group of MIPS porters, and we missed to officially
respond to this email. Here is for the record:
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the jessie release:
For MIPS,MIPSEL,MIPS64,MIPS64EL, I
-
Processing commands for cont...@bugs.debian.org:
> tags 728374 + pending
Bug #728374 [freebsd-net-tools] freebsd-net-tools: /sbin/ifconfig is missing
options for pfsync
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
728374: http://bugs.debi
Hi everyone,
I am part of the group of MIPS porters, and we missed to officially
respond to this email. Here is for the record:
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the jessie release:
For MIPS,MIPSEL,MIPS64,MIPS64EL, I
-
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/endi
On 01/11/2013 15:21, Sebastian Ramacher wrote:
>> anyhow, i'd rather have the problem fixed. so what is the portable
>> solution? should i simply define `__BSD_VISIBLE` for kfreebsd-*?
No, that's an internal macro. Applications are not supposed to provide it.
As far as I can see, starting with kf
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 30 Sep 2013 15:57:56 +0200
Source: kfreebsd-downloader-10
Binary: kfreebsd-downloader-10.0 kfreebsd-downloader-10
Architecture: source kfreebsd-amd64
Version: 10.0~alpha4-1
Distribution: experimental
Urgency: low
Mai
kfreebsd-downloader-10_10.0~beta2-1_kfreebsd-amd64.changes uploaded
successfully to localhost
along with the files:
kfreebsd-downloader-10_10.0~beta2-1.dsc
kfreebsd-downloader-10_10.0~beta2.orig.tar.gz
kfreebsd-downloader-10_10.0~beta2-1.debian.tar.gz
kfreebsd-downloader-10.0_10.0~beta2-1_
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 01 Nov 2013 17:07:43 +0100
Source: kfreebsd-downloader-10
Binary: kfreebsd-downloader-10.0 kfreebsd-downloader-10
Architecture: source kfreebsd-amd64
Version: 10.0~beta2-1
Distribution: experimental
Urgency: low
Main
On 2013-11-01 15:59, Robert Millan wrote:
> On 01/11/2013 15:21, Sebastian Ramacher wrote:
>>> anyhow, i'd rather have the problem fixed. so what is the portable
>>> solution? should i simply define `__BSD_VISIBLE` for kfreebsd-*?
>
> No, that's an internal macro. Applications are not supposed to
On 01/11/2013 21:09, IOhannes m zmölnig wrote:
> thanks for the confirmation.
> the code already includes for BSD-like platforms
> (__FreeBSD__, __APPLE__ *and* __FreeBSD_kernel__) whereas is
> only included on linux and the hurd.
> so i wonder what's the difference between and
> ? can/should i
12 matches
Mail list logo
