hauradou wrote:
> Bruce Dubbs wrote:
>> hauradou wrote:
>>
>>
>>> well, the difference between a big patch and just one option to pass to
>>> the compiler...
>>>
>> I don't consider a 49 line patch big. It is really only adding 8 lines
>> and the rest is explanation. I believe the patch
Bruce Dubbs wrote:
> hauradou wrote:
>
>
>> well, the difference between a big patch and just one option to pass to
>> the compiler...
>>
> I don't consider a 49 line patch big. It is really only adding 8 lines
> and the rest is explanation. I believe the patch came from upstream.
>
>
hauradou wrote:
> well, the difference between a big patch and just one option to pass to
> the compiler...
I don't consider a 49 line patch big. It is really only adding 8 lines
and the rest is explanation. I believe the patch came from upstream.
As I said before, I think your method is sub
Bruce Dubbs wrote:
> hauradou wrote:
>
>> hauradou wrote:
>>
>>> Bruce Dubbs wrote:
>>>
hauradou wrote:
> Is it truely a bug, as stated in the dev book?
>
> After building gcc-4.5.0, found a macro: __i686, expanding to 1
>
> glibc built fine
hauradou wrote:
> hauradou wrote:
>> Bruce Dubbs wrote:
>>> hauradou wrote:
Is it truely a bug, as stated in the dev book?
After building gcc-4.5.0, found a macro: __i686, expanding to 1
glibc built fine in this chapter after adding 'asm-CPPFLAGS += -U
__i686' to confi
hauradou wrote:
> Bruce Dubbs wrote:
>> hauradou wrote:
>>> Is it truely a bug, as stated in the dev book?
>>>
>>> After building gcc-4.5.0, found a macro: __i686, expanding to 1
>>>
>>> glibc built fine in this chapter after adding 'asm-CPPFLAGS += -U
>>> __i686' to configparms, without using any
Bruce Dubbs wrote:
> hauradou wrote:
>
>> Is it truely a bug, as stated in the dev book?
>>
>> After building gcc-4.5.0, found a macro: __i686, expanding to 1
>>
>> glibc built fine in this chapter after adding 'asm-CPPFLAGS += -U
>> __i686' to configparms, without using any patch.
>>
> Y
hauradou wrote:
> Is it truely a bug, as stated in the dev book?
>
> After building gcc-4.5.0, found a macro: __i686, expanding to 1
>
> glibc built fine in this chapter after adding 'asm-CPPFLAGS += -U
> __i686' to configparms, without using any patch.
You don't say what your platform is. The
Is it truely a bug, as stated in the dev book?
After building gcc-4.5.0, found a macro: __i686, expanding to 1
glibc built fine in this chapter after adding 'asm-CPPFLAGS += -U
__i686' to configparms, without using any patch.
Best regards,
boloco
--
http://linuxfromscratch.org/mailman/listinfo
