Benjamin Cama wrote:
> Hi,
>
> Le samedi 17 octobre 2009 à 21:44 -0400, Stefan Monnier a écrit :
>> I thought that all the names listed in /etc/hosts are FQDN already
>> (adding domains is done to hostnames that we lookup, not to the
>> hostnames in the hostnames-table), so the additional . is at
Hi Felix,
On Sun, Oct 18, 2009 at 6:39 PM, Felix Fietkau wrote:
> Yep, sounds good. By the way, I'm currently working on integrating a gcc
> version with CodeSourcery patches into OpenWrt. Maybe that way you also
> won't have to use external toolchains anymore. I've stripped the diff of
No :) I
I'm trying to upgrade some packages I just built from an updated trunk
(r18050) and getting:
# opkg install kmod-sched
Collected errors:
* Packages were found, but none compatible with the architectures configured
Hardware is an ASUS WL500GP:
# uname -a
Linux gw 2.6.25.20 #1 Sat Feb 7 13:49:36
> Luigi Mantellini wrote:
> > toolchain... it seems to work fine but I interrupted the compilation
> > (today is sunday... and I need to see also the sun).
The 'sun' is always under the desk.
(in fact it's a full featured 2 x ultra-sparcII with maximum RAM)
If you really want to see it, just pla
Luigi Mantellini wrote:
> Hi Felix
>
> On Sun, Oct 18, 2009 at 4:22 PM, Felix Fietkau wrote:
>> Though you prefer this option, I believe using external toolchain
>> support in OpenWrt will always be the exception, not the rule. We can
>> easily add toolchains like CodeSourcery's or ELDK's to our
Benjamin Cama wrote:
> Hi,
>
> Le samedi 17 octobre 2009 à 21:44 -0400, Stefan Monnier a écrit :
>> I thought that all the names listed in /etc/hosts are FQDN already
>> (adding domains is done to hostnames that we lookup, not to the
>> hostnames in the hostnames-table), so the additional . is at
Luigi Mantellini wrote:
> Hi Daniel,
>
> to have a consistent build it's mandatory to have the same toolchain.
> For this reason I think that distcc should be used only under this
> hypothesis.
> I'm using the external toolchain support and it works fine (I used
> ELDK's and CodeSourcery's toolch
new patch v2
enjoy
On Sun, Oct 18, 2009 at 12:07 PM, Luigi Mantellini
wrote:
> Hi ml,
>
> As we have the external toolchain support, we can consider to add a
> distcc support.
> I produced the following patch that I never tested yet!
>
> Just some information:
> - distcc must be usable only if
Hi Daniel,
to have a consistent build it's mandatory to have the same toolchain.
For this reason I think that distcc should be used only under this
hypothesis.
I'm using the external toolchain support and it works fine (I used
ELDK's and CodeSourcery's toolchains with good results).
I'm not sure
Luigi Mantellini wrote:
> As we have the external toolchain support, we can consider to add a
> distcc support.
> I produced the following patch that I never tested yet!
>
> Just some information:
> - distcc must be usable only if EXTERNAL_TOOLCHAIN is used (it's
> mandatory to have the same co
first mistake: add a "\" after $(MAKE_DISTCC_VARS) into package-defaults.mk
I already said that I never tested ! ;) eheh
ciao
On Sun, Oct 18, 2009 at 12:07 PM, Luigi Mantellini
wrote:
> Hi ml,
>
> As we have the external toolchain support, we can consider to add a
> distcc support.
> I produced
Hi ml,
As we have the external toolchain support, we can consider to add a
distcc support.
I produced the following patch that I never tested yet!
Just some information:
- distcc must be usable only if EXTERNAL_TOOLCHAIN is used (it's
mandatory to have the same compiler on all hosts...)
- pum
12 matches
Mail list logo
