Re: [Mingw-w64-public] Linkage issues

2010-05-08 Thread t66...@gmail.com
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

Re: [Mingw-w64-public] Linkage issues

2010-05-08 Thread Doug Semler
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

Re: [Mingw-w64-public] Linkage issues

2010-05-08 Thread t66...@gmail.com
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

Re: [Mingw-w64-public] Linkage issues

2010-05-08 Thread Doug Semler
>> 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

Re: [Mingw-w64-public] Linkage issues

2010-05-08 Thread NightStrike
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

[Mingw-w64-public] Linkage issues

2010-05-08 Thread t66...@gmail.com
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

Re: [Mingw-w64-public] Another new leading underscore link problem

2010-05-08 Thread Ozkan Sezer
On Sat, May 8, 2010 at 10:22 AM, t66...@gmail.com wrote: > On 8/05/2010 4:31 PM, Ozkan Sezer wrote: >> >> On Sat, May 8, 2010 at 6:19 AM, t66...@gmail.com  wrote: >> >>> >>> Hello: >>> Further interests to the 64bit no leading underscore problem... >>> I was trying to compile various library proje

Re: [Mingw-w64-public] Another new leading underscore link problem

2010-05-08 Thread t66...@gmail.com
On 8/05/2010 4:31 PM, Ozkan Sezer wrote: > On Sat, May 8, 2010 at 6:19 AM, t66...@gmail.com wrote: > >> Hello: >> Further interests to the 64bit no leading underscore problem... >> I was trying to compile various library projects using gcc-4_5-branch + >> bin-cvs and then found out there's lin

Re: [Mingw-w64-public] problem with i64 in C, C++

2010-05-08 Thread Tor Lillqvist
> in MSVC++, you do > __int64 n=9223372036854775807i64; > but in all forms of GCC, including mingw-w64, you do > #include > __int64 n=9223372036854775807LL; Welcome to Portable Programming 101. Rule 1: Don't assume that things that happen to work in one compiler also work in another. This goes "b

Re: [Mingw-w64-public] problem with i64 in C, C++

2010-05-08 Thread Ozkan Sezer
On Sat, May 8, 2010 at 9:58 AM, Jim Michaels wrote: > in MSVC++, you do > __int64 n=9223372036854775807i64; > but in all forms of GCC, including mingw-w64, you do > #include > __int64 n=9223372036854775807LL; > > because nothing else works. > could that be fixed?  it would be nice to natively com