[ccache] ccache on windows

[Patrick Spendrin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I am interested in getting ccache patches for windows upstreams, so I
started a repository, took the patches that Ramiro Polla provided some
weeks ago, and rebased them; they can be found, including my fixes on
git://gitorious.org/ccache-win/ccache-win.git

I'd like to get these fixes upstreams, not all of them are platform
specific though. Since I am not the original author, I hope Ramiro will
also speak up for these patches?!

regards,
Patrick
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.10 (MingW32)

iEYEARECAAYFAkwhUhEACgkQi49rfdk/G3b9FgCfQaZTLKMfoJpNuQZAyX8q/KWH
XfYAn1c1DFTxktbcGGHI3P7ZhVa2aZZN
=bwi8
-END PGP SIGNATURE-
___
ccache mailing list
ccache@lists.samba.org
https://lists.samba.org/mailman/listinfo/ccache

Re: [ccache] globally unique hashes

[Reuben Hawkins]

On Tue, Jun 22, 2010 at 6:07 AM, Martin Pool  wrote:

> On 22 June 2010 15:36, Reuben Hawkins  wrote:
> >
> >
> > On Tue, Jun 22, 2010 at 4:39 AM, Martin Pool  wrote:
> >>
> >> On 22 June 2010 11:42, Reuben Hawkins  wrote:
> >> > On 06/21/2010 06:06 PM, Martin Pool wrote:
> >> >> On 22 June 2010 10:18, Reuben Hawkins  wrote:
> >> >>
> >> >>> Hi Martin,
> >> >>>
> >> >>> Yes, there would need to be a daemon to respond to multicasts.  I
> >> >>> think
> >> >>> distcc requires setting all the hosts manually on each client
> (correct
> >> >>> me if
> >> >>> I'm wrong).  Maybe what I need is distcc servers to respond to
> >> >>> multicast so
> >> >>> I can avoid maintaining the servers manually on the clients...  I
> see
> >> >>> you're
> >> >>> one of the distcc developers.  Would that be a welcome enhancement?
> >> >>>
> >> >> Using multicast would probably still require some configuration on
> the
> >> >> clients about which multicast group to use, etc.  Is there anything
> >> >> wrong with using mdns?
> >> >>
> >> >>
> >> > Maybe I'm misunderstanding exactly what you're suggesting.  There's
> >> > nothing wrong with using mdns, but my understanding is that even with
> >> > mdns, the names must still be known by the client.  For example...
> >> >
> >> > $ distcc-config --set-hosts "localhost c1.local c2.local c3.local ...
> >> > cN.local"
> >> >
> >> > What I'd like to be able to do is...
> >> >
> >> > $ distcc-config --multicast
> >> >
> >> > So when distcc starts a build, it will call out to the local network,
> >> > "who's running distccd?" and the servers will reply such that my local
> >> > machine can automatically update its list of hosts.
> >>
> >> mdns has a mechanism to say "who offers this service?"  Apple's distcc
> >> version in Xcode does this.  I don't know how well that works on
> >> generic unix but it seems like a good place to start, and the distcc
> >> list would be a good place to ask about it.
> >>
> >> > RFC 3307 suggest that permanent IPv6 multicast addresses can be
> assigned
> >> > (which I haven't really looked into yet, I was just going to pick one
> at
> >> > random for now).  I was not planning on using IPv4 at all.
> >> >
> >> > Is that reasonable or am I missing something?
> >>
> >> I don't think it would be reasonable to have one IPv6 address that is
> >> "the global ccache service for the whole world."  If the address is
> >> intended to be just network-wide or organization-wide, then really you
> >> do have per-machine configuration, you're just choosing to hardcode it
> >> into the program.
> >>
> >> --
> >> Martin
> >
> > I also agree it's unreasonable to have a whole world multicast address
> for
> > distcc.  But I'm not suggesting a global multicast address, just a link
> > local address that doesn't route.  Something in the FF02:: scope.  I
> could
> > use the link local all nodes address FF02::1, but the it would get lots
> of
> > unwanted traffic.  Hardcoding should be ok even if it is FF02::1 (all
> link
> > local nodes) as this is what multicast is for...right?
>
> [please reply on the list]
>
> This sounds a lot like a reinvention of mDNS DNS-SD, which provides a
> generalized way to find a service on the local network by multicast
> queries.  See eg .
>
> --
> Martin
>
Looks like someone already had this idea and did it long ago...
http://lists.samba.org/archive/distcc/2004q4/002774.html
Oh well... Thanks for the info.
___
ccache mailing list
ccache@lists.samba.org
https://lists.samba.org/mailman/listinfo/ccache

Re: [ccache] globally unique hashes

[Martin Pool]

On 22 June 2010 15:36, Reuben Hawkins  wrote:
>
>
> On Tue, Jun 22, 2010 at 4:39 AM, Martin Pool  wrote:
>>
>> On 22 June 2010 11:42, Reuben Hawkins  wrote:
>> > On 06/21/2010 06:06 PM, Martin Pool wrote:
>> >> On 22 June 2010 10:18, Reuben Hawkins  wrote:
>> >>
>> >>> Hi Martin,
>> >>>
>> >>> Yes, there would need to be a daemon to respond to multicasts.  I
>> >>> think
>> >>> distcc requires setting all the hosts manually on each client (correct
>> >>> me if
>> >>> I'm wrong).  Maybe what I need is distcc servers to respond to
>> >>> multicast so
>> >>> I can avoid maintaining the servers manually on the clients...  I see
>> >>> you're
>> >>> one of the distcc developers.  Would that be a welcome enhancement?
>> >>>
>> >> Using multicast would probably still require some configuration on the
>> >> clients about which multicast group to use, etc.  Is there anything
>> >> wrong with using mdns?
>> >>
>> >>
>> > Maybe I'm misunderstanding exactly what you're suggesting.  There's
>> > nothing wrong with using mdns, but my understanding is that even with
>> > mdns, the names must still be known by the client.  For example...
>> >
>> > $ distcc-config --set-hosts "localhost c1.local c2.local c3.local ...
>> > cN.local"
>> >
>> > What I'd like to be able to do is...
>> >
>> > $ distcc-config --multicast
>> >
>> > So when distcc starts a build, it will call out to the local network,
>> > "who's running distccd?" and the servers will reply such that my local
>> > machine can automatically update its list of hosts.
>>
>> mdns has a mechanism to say "who offers this service?"  Apple's distcc
>> version in Xcode does this.  I don't know how well that works on
>> generic unix but it seems like a good place to start, and the distcc
>> list would be a good place to ask about it.
>>
>> > RFC 3307 suggest that permanent IPv6 multicast addresses can be assigned
>> > (which I haven't really looked into yet, I was just going to pick one at
>> > random for now).  I was not planning on using IPv4 at all.
>> >
>> > Is that reasonable or am I missing something?
>>
>> I don't think it would be reasonable to have one IPv6 address that is
>> "the global ccache service for the whole world."  If the address is
>> intended to be just network-wide or organization-wide, then really you
>> do have per-machine configuration, you're just choosing to hardcode it
>> into the program.
>>
>> --
>> Martin
>
> I also agree it's unreasonable to have a whole world multicast address for
> distcc.  But I'm not suggesting a global multicast address, just a link
> local address that doesn't route.  Something in the FF02:: scope.  I could
> use the link local all nodes address FF02::1, but the it would get lots of
> unwanted traffic.  Hardcoding should be ok even if it is FF02::1 (all link
> local nodes) as this is what multicast is for...right?

[please reply on the list]

This sounds a lot like a reinvention of mDNS DNS-SD, which provides a
generalized way to find a service on the local network by multicast
queries.  See eg .

-- 
Martin
___
ccache mailing list
ccache@lists.samba.org
https://lists.samba.org/mailman/listinfo/ccache

Re: [ccache] globally unique hashes

[Martin Pool]

On 22 June 2010 11:42, Reuben Hawkins  wrote:
> On 06/21/2010 06:06 PM, Martin Pool wrote:
>> On 22 June 2010 10:18, Reuben Hawkins  wrote:
>>
>>> Hi Martin,
>>>
>>> Yes, there would need to be a daemon to respond to multicasts.  I think
>>> distcc requires setting all the hosts manually on each client (correct me if
>>> I'm wrong).  Maybe what I need is distcc servers to respond to multicast so
>>> I can avoid maintaining the servers manually on the clients...  I see you're
>>> one of the distcc developers.  Would that be a welcome enhancement?
>>>
>> Using multicast would probably still require some configuration on the
>> clients about which multicast group to use, etc.  Is there anything
>> wrong with using mdns?
>>
>>
> Maybe I'm misunderstanding exactly what you're suggesting.  There's
> nothing wrong with using mdns, but my understanding is that even with
> mdns, the names must still be known by the client.  For example...
>
> $ distcc-config --set-hosts "localhost c1.local c2.local c3.local ...
> cN.local"
>
> What I'd like to be able to do is...
>
> $ distcc-config --multicast
>
> So when distcc starts a build, it will call out to the local network,
> "who's running distccd?" and the servers will reply such that my local
> machine can automatically update its list of hosts.

mdns has a mechanism to say "who offers this service?"  Apple's distcc
version in Xcode does this.  I don't know how well that works on
generic unix but it seems like a good place to start, and the distcc
list would be a good place to ask about it.

> RFC 3307 suggest that permanent IPv6 multicast addresses can be assigned
> (which I haven't really looked into yet, I was just going to pick one at
> random for now).  I was not planning on using IPv4 at all.
>
> Is that reasonable or am I missing something?

I don't think it would be reasonable to have one IPv6 address that is
"the global ccache service for the whole world."  If the address is
intended to be just network-wide or organization-wide, then really you
do have per-machine configuration, you're just choosing to hardcode it
into the program.

-- 
Martin
___
ccache mailing list
ccache@lists.samba.org
https://lists.samba.org/mailman/listinfo/ccache

Re: [ccache] globally unique hashes

[Martin Pool]

On 21 June 2010 01:26, Reuben Hawkins  wrote:
> c) distcc takes too much configuration/coordination, however, multicasting
> takes zero configuration/coordination

Really?  You don't have to do much more than run a daemon on the
servers, and presumably you would need a multicast daemon to serve
ccache requests.  I think distcc can find its servers through mdns.

-- 
Martin
___
ccache mailing list
ccache@lists.samba.org
https://lists.samba.org/mailman/listinfo/ccache