于 2011/10/20 14:44, Ozkan Sezer 写道:
> What fixed it? Solved it or hidden it?
I download gcc-4.6.2-RC-20111019 to build it.
Using the edition to build gdb with "-Os", no crash anymore.
I think this may be solved at some time.
--
Best Re
g session is active.
>
> Inferior 1 [process 2212] will be killed.
>
> Quit anyway? (y or n)
>
>
> And if I replace "-Os" with "-O2" to rebuild again, gdb will work ok.
>
&g
ad, and it's also
crash.
So it's gcc's -Os bug?
But I only found the issue when I built gdb, other projects with "-Os"
work well.
Ruben, can you try to build gdb with "-Os" using your edition, test it
debugging?
Kai, what changes gcc's "-Os"
Hi, K. Frank
On Thu, Oct 20, 2011 at 1:54 AM, K. Frank wrote:
> Hello xunxun!
>
> On Wed, Oct 19, 2011 at 11:43 AM, xunxun wrote:
>> 于 2011/10/19 23:38, Morcego Vermelho 写道:
>> ...
>> If you refer to Qt build, you can modify
>>
>> mkspecs/win32-g++/qmake.conf (similar it is, I forgot that)
>>
2011/10/19 K. Frank
> Hello xunxun!
>
> On Wed, Oct 19, 2011 at 11:43 AM, xunxun wrote:
> > 于 2011/10/19 23:38, Morcego Vermelho 写道:
> > ...
> > If you refer to Qt build, you can modify
> >
> > mkspecs/win32-g++/qmake.conf (similar it is, I forgot that)
> >
> > QMAKE_CFLAGS_RELEASE = -O2 -fno-k
Hello xunxun!
On Wed, Oct 19, 2011 at 11:43 AM, xunxun wrote:
> 于 2011/10/19 23:38, Morcego Vermelho 写道:
> ...
> If you refer to Qt build, you can modify
>
> mkspecs/win32-g++/qmake.conf (similar it is, I forgot that)
>
> QMAKE_CFLAGS_RELEASE = -O2 -fno-keep-inline-dllexport
Thank you. I will
Hi Ruben!
On Wed, Oct 19, 2011 at 11:18 AM, Ruben Van Boxem
wrote:
> 2011/10/19 xunxun
>>
>> 于 2011/10/19 22:32, K. Frank 写道:
>> > Hello Lists!
>> >
>> > I get the following error:
>> >
>> > ./tmp\obj\debug_shared\moc_qgraphicsanchorlayout.o: file not
>> > recognized: Memory exhausted
>> >
>
于 2011/10/19 23:38, Morcego Vermelho 写道:
this answer is enigmatic
I dont know how to reduce it
If you refer to Qt build, you can modify
mkspecs/win32-g++/qmake.conf (similar it is, I forgot that)
QMAKE_CFLAGS_RELEASE = -O2 -fno-keep-inline-dllexport
--
Best Regards,
xunxun
---
this answer is enigmatic
I dont know how to reduce it
2011/10/19 xunxun
> 于 2011/10/19 23:18, Ruben Van Boxem 写道:
> > reduce DLL size
>
> reduce DLL obj size
>
> --
> Best Regards,
> xunxun
>
>
>
> --
> All the data con
于 2011/10/19 23:18, Ruben Van Boxem 写道:
> reduce DLL size
reduce DLL obj size
--
Best Regards,
xunxun
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, applicat
2011/10/19 xunxun
> 于 2011/10/19 22:32, K. Frank 写道:
> > Hello Lists!
> >
> > I get the following error:
> >
> > ./tmp\obj\debug_shared\moc_qgraphicsanchorlayout.o: file not
> > recognized: Memory exhausted
> >
> > in the build step that links QtGuid4.dll when trying to build Qt
> 4.8.0-rc1
>
于 2011/10/19 22:32, K. Frank 写道:
> Hello Lists!
>
> I get the following error:
>
> ./tmp\obj\debug_shared\moc_qgraphicsanchorlayout.o: file not
> recognized: Memory exhausted
>
> in the build step that links QtGuid4.dll when trying to build Qt 4.8.0-rc1
> with mingw-w64 4.7.0
>
> Would anyone h
Hello Lists!
I get the following error:
./tmp\obj\debug_shared\moc_qgraphicsanchorlayout.o: file not
recognized: Memory exhausted
in the build step that links QtGuid4.dll when trying to build Qt 4.8.0-rc1
with mingw-w64 4.7.0
Would anyone have some suggestions about how I might fix this?
(Ta
On Wed, Oct 19, 2011 at 11:25 AM, Ruben Van Boxem
wrote:
> Op 19 okt. 2011 10:07 schreef "Ozkan Sezer" het
> volgende:
>
>>
>> >>
>> >> Doing #include in your *.c and -I[somepath]/ddk in
>> >> your CFLAGS or something?
>
> Why not ? Shouldn't the ddk headers be in a standard include
> directory
On Wed, Oct 19, 2011 at 12:25 PM, Ruben Van Boxem
wrote:
> Op 19 okt. 2011 10:07 schreef "Ozkan Sezer" het
> volgende:
>
>>
>> On Wed, Oct 19, 2011 at 10:45 AM, Luis Lavena
>> wrote:
>> > On Wed, Oct 19, 2011 at 9:32 AM, Ozkan Sezer wrote:
>> >> On Wed, Oct 19, 2011 at 10:23 AM, Luis Lavena
>>
Op 19 okt. 2011 10:07 schreef "Ozkan Sezer" het
volgende:
>
> On Wed, Oct 19, 2011 at 10:45 AM, Luis Lavena
wrote:
> > On Wed, Oct 19, 2011 at 9:32 AM, Ozkan Sezer wrote:
> >> On Wed, Oct 19, 2011 at 10:23 AM, Luis Lavena
wrote:
> >>>
> >>> I'm missing a way to trigger the inclusion of DDK?
> >
On Wed, Oct 19, 2011 at 10:45 AM, Luis Lavena wrote:
> On Wed, Oct 19, 2011 at 9:32 AM, Ozkan Sezer wrote:
>> On Wed, Oct 19, 2011 at 10:23 AM, Luis Lavena wrote:
>>>
>>> I'm missing a way to trigger the inclusion of DDK?
>>
>> Doing #include in your *.c and -I[somepath]/ddk in
>> your CFLAGS o
On Wed, Oct 19, 2011 at 9:32 AM, Ozkan Sezer wrote:
> On Wed, Oct 19, 2011 at 10:23 AM, Luis Lavena wrote:
>>
>> I'm missing a way to trigger the inclusion of DDK?
>
> Doing #include in your *.c and -I[somepath]/ddk in
> your CFLAGS or something?
>
Thank you,
Problem with that is means I would
On Wed, Oct 19, 2011 at 10:23 AM, Luis Lavena wrote:
> Hello,
>
> While attempting to use Ruben's GCC 4.6.2 build under Windows 7 to
> compile libuv [1], I found that REPARSE_DATA_BUFFER is undefined:
>
> gcc -Iinclude -Iinclude/uv-private -g --std=gnu89
> -D_WIN32_WINNT=0x0501 -Isrc/ares/config_w
Hello,
While attempting to use Ruben's GCC 4.6.2 build under Windows 7 to
compile libuv [1], I found that REPARSE_DATA_BUFFER is undefined:
gcc -Iinclude -Iinclude/uv-private -g --std=gnu89
-D_WIN32_WINNT=0x0501 -Isrc/ares/config_win32 -o src/win/fs.o -c
src/win/fs.c
src/win/fs.c: In function 'fs
20 matches
Mail list logo
