On Mon, 2006-12-18 at 20:51 +, Pedro Alves wrote:
> > I'll start trying to build an RPM based on the current work as soon as I
> > have the --coverage stuff working too. I'm still working on two issues
> > there (a build problem : the build appears to disable a lot of stuff
> > because -Dinhibi
Danny Backx escreveu:
> On Mon, 2006-12-18 at 17:15 +, Pedro Alves wrote:
>> I think cross-toolchains are
>> special, in the sense that they shouldn't be mixed with the
>> system headers/libs. I don't have an official pointer describing
>> it, but it seems everybody does it.
>
> Looks like a
On Mon, 2006-12-18 at 17:15 +, Pedro Alves wrote:
> I think cross-toolchains are
> special, in the sense that they shouldn't be mixed with the
> system headers/libs. I don't have an official pointer describing
> it, but it seems everybody does it.
Looks like a good argument, I won't fiddle wi
Danny Backx wrote:
> On Mon, 2006-12-18 at 10:23 +, Pedro Alves wrote:
>
>>Danny Backx wrote:
>>
>>>The reason I'm also asking about the installation path is I'd want to
>>>create an RPM based on these scripts. Do we keep the funky path for now
>>>(I used to do the same with my scripts in scri
On Mon, 2006-12-18 at 10:23 +, Pedro Alves wrote:
> Danny Backx wrote:
> > The reason I'm also asking about the installation path is I'd want to
> > create an RPM based on these scripts. Do we keep the funky path for now
> > (I used to do the same with my scripts in scripts/linux), or do we mov
Danny Backx wrote:
> Pedro,
>
> Can I commit this patch, and a similar one for the cegcc script?
Ok.
> One of the issues might be where to install the documentation, another
> is where to install the whole toolchain (currently this is what you
> wrote in it - /opt/mingw32ce ).
>
> The reason I
Pedro,
Can I commit this patch, and a similar one for the cegcc script?
One of the issues might be where to install the documentation, another
is where to install the whole toolchain (currently this is what you
wrote in it - /opt/mingw32ce ).
The reason I'm also asking about the installation path