On 9/05/2010 1:55 PM, Doug Semler wrote:
> I've never heard of ccache, but it seems that by the fact that
> removing it from the chain gave you a good compile, i'd say the
> problem is there...
>
> Aside from the fact that your cache should have been completely
> invalidated by the new compiler, af
On Sat, May 8, 2010 at 10:52 PM, t66...@gmail.com wrote:
> On 9/05/2010 3:53 AM, Doug Semler wrote:
>>
>> If you want to see the actual compile command, either configure with
>> --disable-silent-rules
>>
>> or
>>
>> make V=1 ...
>>
>
> V=1 worked
> I've check the log and tried first removing ccach
On 9/05/2010 3:53 AM, Doug Semler wrote:
>
> If you want to see the actual compile command, either configure with
> --disable-silent-rules
>
> or
>
> make V=1 ...
>
V=1 worked
I've check the log and tried first removing ccache, re-run the command.
This time file size is ok.
Something must have
>> In the build log, gcc command line is silenced.
>> CC libavformat/utils.o
>>
>> Is this a bug in the binutils or gcc-4.5 branch?
>
> You really should provide the actual compiler command.
>
If you want to see the actual compile command, either configure with
--disable-silent-rules
or
mak
On Sat, May 8, 2010 at 5:00 AM, t66...@gmail.com wrote:
> Hello:
> I have another problem compiling ffmpeg...
> Using a cross compiler gcc-4_5-branch + bin-cvs
> ffmpeg exe will not link.
>
> I see lots of output files having 0 byte in size.
> For some reason 0 byte size was written and the compil
Hello:
I have another problem compiling ffmpeg...
Using a cross compiler gcc-4_5-branch + bin-cvs
ffmpeg exe will not link.
I see lots of output files having 0 byte in size.
For some reason 0 byte size was written and the compiling process
continued without errors until linking.
3220 2010-05-08
