"Ronald S. Bultje" writes:
> Hi,
>
> On Sun, Jul 22, 2012 at 5:35 PM, Måns Rullgård wrote:
>> Diego Biurrun writes:
>>
>>> On Mon, Jul 23, 2012 at 01:16:07AM +0100, Måns Rullgård wrote:
Diego Biurrun writes:
> On Mon, Jul 23, 2012 at 12:16:41AM +0100, Mans Rullgard wrote:
>
On Mon, Jul 23, 2012 at 01:35:06AM +0100, Måns Rullgård wrote:
> Diego Biurrun writes:
> > On Mon, Jul 23, 2012 at 01:16:07AM +0100, Måns Rullgård wrote:
> >> Diego Biurrun writes:
> >> > On Mon, Jul 23, 2012 at 12:16:41AM +0100, Mans Rullgard wrote:
> >> >> This allows using non-standard flags f
Hi,
On Sun, Jul 22, 2012 at 5:35 PM, Måns Rullgård wrote:
> Diego Biurrun writes:
>
>> On Mon, Jul 23, 2012 at 01:16:07AM +0100, Måns Rullgård wrote:
>>> Diego Biurrun writes:
>>>
>>> > On Mon, Jul 23, 2012 at 12:16:41AM +0100, Mans Rullgard wrote:
>>> >> This allows using non-standard flags fo
Diego Biurrun writes:
> On Mon, Jul 23, 2012 at 01:16:07AM +0100, Måns Rullgård wrote:
>> Diego Biurrun writes:
>>
>> > On Mon, Jul 23, 2012 at 12:16:41AM +0100, Mans Rullgard wrote:
>> >> This allows using non-standard flags for running the C preprocessor.
>> >> The -o flag must be included in
On Mon, Jul 23, 2012 at 01:16:07AM +0100, Måns Rullgård wrote:
> Diego Biurrun writes:
>
> > On Mon, Jul 23, 2012 at 12:16:41AM +0100, Mans Rullgard wrote:
> >> This allows using non-standard flags for running the C preprocessor.
> >> The -o flag must be included in this setting due to strange sy
Diego Biurrun writes:
> On Mon, Jul 23, 2012 at 12:16:41AM +0100, Mans Rullgard wrote:
>> This allows using non-standard flags for running the C preprocessor.
>> The -o flag must be included in this setting due to strange syntax
>> required by some compilers.
>>
>> --- a/configure
>> +++ b/confi
On Mon, Jul 23, 2012 at 12:16:41AM +0100, Mans Rullgard wrote:
> This allows using non-standard flags for running the C preprocessor.
> The -o flag must be included in this setting due to strange syntax
> required by some compilers.
>
> --- a/configure
> +++ b/configure
> @@ -621,6 +621,10 @@ cc_o
On 22/07/2012 7:54 PM, Måns Rullgård wrote:
> Same reason as cc_o. For both of these variables, the value will
> contain $@ which make expands to the target being built. In the shell,
> $@ expands to all arguments of the script/function. Passing the
> filename as argument to a function and, with
Derek Buitenhuis writes:
> On 22/07/2012 7:39 PM, Måns Rullgård wrote:
+cc_e(){
>> +eval printf '%s\\n' $CC_E
>> +}
>>> >
>>> > I'm probably ignorant here, but why is this needed?
>> Why is what needed?
>
> cc_e(). Something preventing using $CC_E directly (I'm sure there is).
On 22/07/2012 7:39 PM, Måns Rullgård wrote:
>>> +cc_e(){
>>> >> +eval printf '%s\\n' $CC_E
>>> >> +}
>> >
>> > I'm probably ignorant here, but why is this needed?
> Why is what needed?
cc_e(). Something preventing using $CC_E directly (I'm sure there is).
- Derek
_
Derek Buitenhuis writes:
> On 22/07/2012 7:16 PM, Mans Rullgard wrote:
>> This allows using non-standard flags for running the C preprocessor.
>> The -o flag must be included in this setting due to strange syntax
>> required by some compilers.
>>
>> Set the correct flags for tms470.
>>
>> Signe
On 22/07/2012 7:16 PM, Mans Rullgard wrote:
> This allows using non-standard flags for running the C preprocessor.
> The -o flag must be included in this setting due to strange syntax
> required by some compilers.
>
> Set the correct flags for tms470.
>
> Signed-off-by: Mans Rullgard
> ---
> co
This allows using non-standard flags for running the C preprocessor.
The -o flag must be included in this setting due to strange syntax
required by some compilers.
Set the correct flags for tms470.
Signed-off-by: Mans Rullgard
---
configure | 12 ++--
1 file changed, 10 insertions(+), 2
13 matches
Mail list logo
