On 15 Jul 2003, Juliusz Chroboczek wrote:
> MLF> I think the best thing to do here is to recode DPS to rely on xtrans.
> Shall we remove libdps from the tree?
Why? Is DPS dead? It's just a matter of time before I find the time to
convert it. And that doesn't preclude someone else beating me t
MLF> I think the best thing to do here is to recode DPS to rely on xtrans.
Shall we remove libdps from the tree?
Juliusz
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
On Mon, 14 Jul 2003, Andrew C Aitchison wrote:
> On Sun, 13 Jul 2003, Alan Coopersmith wrote:
> > > ../../lib/xtrans/Xtranssock.c: At top level:
> > > ../../lib/xtrans/Xtranssock.c:1315: `MAXHOSTNAMELEN' undeclared here (not in a
> > > function)
> > Is there some other file that needs to be inc
On Sun, 13 Jul 2003, Alan Coopersmith wrote:
> Andrew C Aitchison wrote:
> > ../../lib/xtrans/Xtrans.h:462: warning: redundant redeclaration of
> > `_X11TransFreeConnInfo' in same scope
> > ../../lib/xtrans/Xtrans.h:267: warning: previous declaration of
> > `_X11TransFreeConnInfo'
> This one's
On Wed, 9 Jul 2003, Marc Aurele La France wrote:
> > > - libdps needs IPv6 work. Perhaps other things (not included in X.Org's
> > > tree) do also.
> > True. I did not touch DPS at all - I didn't think anyone made a DPS/NX
> > standalone agent that was IPv6 capable, nor that anyone was workin
On Sun, 13 Jul 2003, Alan Coopersmith wrote:
> What is the family member of struct sockaddr_storage then?
> This could probably be worked around by changing line 338 from:
> ciptr->family = sockname.ss_family;
> to something like:
> ciptr->family = ((struct sockaddr *)&sockname)->sa_fami
Andrew C Aitchison wrote:
../../lib/xtrans/Xtrans.h:462: warning: redundant redeclaration of
`_X11TransFreeConnInfo' in same scope
../../lib/xtrans/Xtrans.h:267: warning: previous declaration of `_X11TransFreeConnInfo'
This one's my fault. X11R6.6 didn't have a declaration of FreeConnInfo in
Xtr
On Sat, 12 Jul 2003, Marc Aurele La France wrote:
> In my book, only redeclaration warnings due to [g]libc are "redundant".
> Is there anything else here you're omitting? It certainly seems like it.
Most are glibc, but looking again I did omit one significant one.
Here is the full log for x11tra
On Sat, 12 Jul 2003, Andrew C Aitchison wrote:
> On Sat, 12 Jul 2003, Todd T. Fries wrote:
> > Looks good to me (sorry for my previous email, I should have checked this
> > mailbox first).
> > Is there known any OS that does not have
> > IPV6_JOIN_MULTICAST/IPV6_LEAVE_MULTICAST ? I understand y
>On Sat, 12 Jul 2003, Todd T. Fries wrote:
>
>> Looks good to me (sorry for my previous email, I should have checked this
>> mailbox first).
>>
>> Is there known any OS that does not have
>> IPV6_JOIN_MULTICAST/IPV6_LEAVE_MULTICAST ? I understand you provide the
>> defines for backwards compatibi
On Sat, 12 Jul 2003, Todd T. Fries wrote:
> Looks good to me (sorry for my previous email, I should have checked this
> mailbox first).
>
> Is there known any OS that does not have
> IPV6_JOIN_MULTICAST/IPV6_LEAVE_MULTICAST ? I understand you provide the
> defines for backwards compatibility, bu
Looks good to me (sorry for my previous email, I should have checked this
mailbox first).
Is there known any OS that does not have
IPV6_JOIN_MULTICAST/IPV6_LEAVE_MULTICAST ? I understand you provide the
defines for backwards compatibility, but I'd be curious if this is truly
necessary...
Thanks,
I have no objection if the semantics are the same. I was merely
following Steven's Unix Network Programming (Vol 1 2nd Ed) which
predates this change in the RFC's and did not realize they had been
changed.
-Alan Coopersmith- [EMAIL PROTECTED]
Sun Microsystems, Inc. -
On Wed, 9 Jul 2003, Matthieu Herrb wrote:
> I had to make the following change to get the code to
> compile on OpenBSD, where IPV6_ADD_MEMBERSHIP is not defined.
> According to Jun-ichiro itojun Hagino, from the Kame project
> and *BSD's IPv6 guru, IPV6_{ADD,DROP}_MEMBERSHIP are obsoleted and
> re
I had to make the following change to get the code to
compile on OpenBSD, where IPV6_ADD_MEMBERSHIP is not defined.
According to Jun-ichiro itojun Hagino, from the Kame project
and *BSD's IPv6 guru, IPV6_{ADD,DROP}_MEMBERSHIP are obsoleted and
replaced by IPV6_{JOIN,LEAVE}_GROUP, that's why I chan
Marc Aurele La France wrote:
True. I did not touch DPS at all - I didn't think anyone made a DPS/NX
standalone agent that was IPv6 capable, nor that anyone was working on it.
I believe as long as you only use DPS as an extension built into the X server
it will work fine (at least we haven't seen p
On Wed, 9 Jul 2003, Alan Coopersmith wrote:
> Marc Aurele La France wrote:
> >>- Incorporate X.Org responses to comments #'s 1, 2, 4, 5, 7, 10, 11, 12,
> >> 13, 14 and 15 (taken from an X.Org-internal document dated 2003.06.17).
> I'm still working on a second round of patches fo
Marc Aurele La France wrote:
- Incorporate X.Org responses to comments #'s 1, 2, 4, 5, 7, 10, 11, 12,
13, 14 and 15 (taken from an X.Org-internal document dated 2003.06.17).
I'm still working on a second round of patches for the X.org review
to incorporate the changes from the comme
On Wed, 9 Jul 2003, Marc Aurele La France wrote:
> CVSROOT: /home/x-cvs
> Module name: xc
> Changes by: [EMAIL PROTECTED] 03/07/09 08:27:41
> Log message:
>300. X.Org IPv6 changes (Bugzilla #227, Alan Coopersmith, Marc La France).
> See http://www.x.org/IPV6_Specific_Cha
19 matches
Mail list logo
