On Sun, May 18, 2008 at 12:32:09 +0200, Johannes Winkelmann wrote:
Hi there,
My qt4 port triggered an error [1] when using distcc to build it. After
some investigation, I realized that Qt4 by default uses precompiled
headers [2], which break when the compilation is done on a different
Johannes Winkelmann wrote:
Hi,
On Mon, May 19, 2008 at 13:42:18 +1000, Danny Rawlins wrote:
Johannes Winkelmann wrote:
Hi there,
[...]
There are a couple of ways to address that:
3. make the Pkgfiles aware that they're build with distcc, so they can
react (might
On Tue, May 20, 2008 at 22:27:30 +1000, Danny Rawlins wrote:
Johannes Winkelmann wrote:
[...]
Well, currently build() should be independent from the set of installed
packages,
OK but... configure scripts can also detect if a program is installed or
not. Does this also imply that we should
Danny Rawlins [2008-05-19 13:42]:
area that interests me. I would guard my ports but it seems I'll lose
some ports like mpfr later since gcc will require it in later versions.
That seems to be a huge problem for you, which I really don't
understand. What's the deal about not maintaining one of
Hi,
On Mon, May 19, 2008 at 13:42:18 +1000, Danny Rawlins wrote:
Johannes Winkelmann wrote:
Hi there,
[...]
There are a couple of ways to address that:
3. make the Pkgfiles aware that they're build with distcc, so they can
react (might need a more generic solution than just distcc,
Johannes Winkelmann wrote:
Hi there,
My qt4 port triggered an error [1] when using distcc to build it. After
some investigation, I realized that Qt4 by default uses precompiled
headers [2], which break when the compilation is done on a different
machine since the precompiled headers are not
