trunk build error after revision 189603

trunk build error after revision 189603

[niXman]

Hi,

I regularly build MinGW within the MinGW-builds project [1].
I build releases, brunches and snapshots.
I have a problem with the building of trunk. Last successfully built
revision was 189603.

Now, when trying to build trunk, I get the following error:
> gcc-trunk/libgcc/unwind-c.c: In function '__gcc_personality_seh0':
> gcc-trunk/libgcc/unwind-c.c:242:14: error: '__gcc_personality_imp' undeclared (first use in this function)

The arguments / configuration options - were not changed. Trunk simply
stopped to build. The brunches are built successfully.

I suppose that the error had appeared due to the use of this [2] patch.

Any ideas?



[1] http://sourceforge.net/projects/mingwbuilds/
[2] http://gcc.gnu.org/ml/gcc-patches/2012-07/msg00512.html


-- 
Regards,
niXman
___________________________________________________
Dual-target(32 & 64 bit) MinGW compilers for 32 and 64 bit Windows:
http://sourceforge.net/projects/mingwbuilds/

Re: trunk build error after revision 189603

[JonY]

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

On 8/20/2012 00:16, niXman wrote:
> Hi,
> 
> I regularly build MinGW within the MinGW-builds project [1].
> I build releases, brunches and snapshots.
> I have a problem with the building of trunk. Last successfully built
> revision was 189603.
> 
> Now, when trying to build trunk, I get the following error:
>> gcc-trunk/libgcc/unwind-c.c: In function '__gcc_personality_seh0':
>> gcc-trunk/libgcc/unwind-c.c:242:14: error: '__gcc_personality_imp' undeclared (first use in this function)
> 
> The arguments / configuration options - were not changed. Trunk simply
> stopped to build. The brunches are built successfully.
> 
> I suppose that the error had appeared due to the use of this [2] patch.
> 
> Any ideas?
> 
> 
> 
> [1] http://sourceforge.net/projects/mingwbuilds/
> [2] http://gcc.gnu.org/ml/gcc-patches/2012-07/msg00512.html
> 
> 
Are you building for win64 target? If so, you can remove the
--enable-sjlj-exceptions or --disable-sjlj-exceptions option.

win32 target builds should be unaffected.




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 196 bytes --]

Re: trunk build error after revision 189603

[niXman]

2012/8/20 JonY:
> Are you building for win64 target? If so, you can remove the
> --enable-sjlj-exceptions or --disable-sjlj-exceptions option.
>
> win32 target builds should be unaffected.

Yes, if I remove the --enable-sjlj-exceptions, then build for win64
target is successful. But for win32, the build is completed with same
error.

Another question: what will no longer be able to use SJLJ exceptions
for win32/win64?


-- 
Regards,
niXman
___________________________________________________
Dual-target(32 & 64 bit) MinGW compilers for 32 and 64 bit Windows:
http://sourceforge.net/projects/mingwbuilds/

Re: trunk build error after revision 189603

[niXman]

2012/8/20 niXman:
> 2012/8/20 JonY:
>> Are you building for win64 target? If so, you can remove the
>> --enable-sjlj-exceptions or --disable-sjlj-exceptions option.
>>
>> win32 target builds should be unaffected.
>
> Yes, if I remove the --enable-sjlj-exceptions, then build for win64
> target is successful. But for win32, the build is completed with same
> error.
>
> Another question: what will no longer be able to use SJLJ exceptions
> for win32/win64?
>

ping?


-- 
Regards,
niXman
___________________________________________________
Dual-target(32 & 64 bit) MinGW compilers for 32 and 64 bit Windows:
http://sourceforge.net/projects/mingwbuilds/

Re: trunk build error after revision 189603

[JonY]

[-- Attachment #1: Type: text/plain, Size: 874 bytes --]

On 8/21/2012 07:26, niXman wrote:
> 2012/8/20 niXman:
>> 2012/8/20 JonY:
>>> Are you building for win64 target? If so, you can remove the
>>> --enable-sjlj-exceptions or --disable-sjlj-exceptions option.
>>>
>>> win32 target builds should be unaffected.
>>
>> Yes, if I remove the --enable-sjlj-exceptions, then build for win64
>> target is successful. But for win32, the build is completed with same
>> error.
>>
>> Another question: what will no longer be able to use SJLJ exceptions
>> for win32/win64?
>>
> 
> ping?
> 
> 

Well, there is no reason to, once the Borland patents expire for win32.
It is possible with some fix up to allow sjlj EH. I'll leave this to the
GCC devs.

BTW, leaving --enable-sjlj-exceptions or --disable-sjlj-exceptions
should leave you sjlj EH build for win32 target, I'm not getting those
errors you described.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 196 bytes --]

Re: trunk build error after revision 189603

[niXman]

2012/8/21 JonY:
> BTW, leaving --enable-sjlj-exceptions or --disable-sjlj-exceptions
> should leave you sjlj EH build for win32 target, I'm not getting those
> errors you described.
>

Prompt to me please, with what arguments you run configure?



-- 
Regards,
niXman
___________________________________________________
Dual-target(32 & 64 bit) MinGW compilers for 32 and 64 bit Windows:
http://sourceforge.net/projects/mingwbuilds/

Re: trunk build error after revision 189603

[JonY]

[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]

On 8/21/2012 18:01, niXman wrote:
> 2012/8/21 JonY:
>> BTW, leaving --enable-sjlj-exceptions or --disable-sjlj-exceptions
>> should leave you sjlj EH build for win32 target, I'm not getting those
>> errors you described.
>>
> 
> Prompt to me please, with what arguments you run configure?
> 
> 
> 


gcc-trunk/configure --prefix=/opt/mingw64_64_48 --with-sysroot=/opt/mingw64_64_48 --with-build-sysroot=/opt/mingw64_64_48 --enable-multilib --enable-targets=all --disable-win32-registry --enable-languages=c,ada,c++,fortran,objc,obj-c++ --enable-fully-dynamic-string --enable-libgomp --enable-version-specific-runtime-libs --with-dwarf2 --enable-decimal-float=bid --enable-lto --enable-graphite --enable-long-long --enable-c99 --enable-wchar_t --with-gnu-ld --with-gnu-as --with-arch=corei7-avx --with-tune=corei7-avx --with-gmp=/opt/support --with-mpfr=/opt/support --with-isl=/opt/support --with-cloog=/opt/support --with-mpc=/opt/support --enable-version-specific-runtime-libs --enable-cloog-backend=isl --enable-checking=no --build=i686-pc-cygwin --host=i686-pc-cygwin --target=x86_64-w64-mingw32 -C

No errors in the win32 part, it uses SJLJ as usual. So omit the 
x86_64-w64-mingw32 parts for their equivalent and disable multilib 
if you want to use a simple win32 only target GCC.

The only hack I needed is to use a linker script to fix up some 
static support libs.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 196 bytes --]

Re: trunk build error after revision 189603

[niXman]

2012/8/21 JonY:
> --with-dwarf2

Using dwarf I just going to succeed.
But I was interested the build using SJLJ.


-- 
Regards,
niXman
___________________________________________________
Dual-target(32 & 64 bit) MinGW compilers for 32 and 64 bit Windows:
http://sourceforge.net/projects/mingwbuilds/

Re: trunk build error after revision 189603

[JonY]

[-- Attachment #1: Type: text/plain, Size: 264 bytes --]

On 8/21/2012 23:30, niXman wrote:
> 2012/8/21 JonY:
>> --with-dwarf2
> 
> Using dwarf I just going to succeed.
> But I was interested the build using SJLJ.
> 
> 

That is a debug format, not EH. stabs doesn't cut it anymore for large
C++ codebases.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 196 bytes --]

Re: trunk build error after revision 189603

[niXman]

2012/8/22 JonY:

> That is a debug format, not EH. stabs doesn't cut it anymore for large
> C++ codebases.
>
>

Ie now build trunk using '--with-dwarf' is equivalent to that used
previously '--enable-sjlj-exceptions' ?
I'm so confused%)


-- 
Regards,
niXman
___________________________________________________
Dual-target(32 & 64 bit) MinGW compilers for 32 and 64 bit Windows:
http://sourceforge.net/projects/mingwbuilds/

Re: trunk build error after revision 189603

[JonY]

[-- Attachment #1: Type: text/plain, Size: 545 bytes --]

On 8/22/2012 18:56, niXman wrote:
> 2012/8/22 JonY:
> 
>> That is a debug format, not EH. stabs doesn't cut it anymore for large
>> C++ codebases.
>>
>>
> 
> Ie now build trunk using '--with-dwarf' is equivalent to that used
> previously '--enable-sjlj-exceptions' ?
> I'm so confused%)
> 

These 2 options are unrelated to each other, there is dwarf debug format
and there is dwarf EH.

What I did in my build is to use dwarf debug format, but not explicitly
set the EH method, this means SEH for win64, SJLJ for win32.




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 196 bytes --]

Re: trunk build error after revision 189603

[niXman]

2012/8/21 JonY:

I can't still to build trunk %)


> Well, there is no reason to, once the Borland patents expire for win32.
Tell me please, when the patent expires?


-- 
Regards,
niXman
___________________________________________________
Dual-target(32 & 64 bit) MinGW compilers for 32 and 64 bit Windows:
http://sourceforge.net/projects/mingwbuilds/

Re: trunk build error after revision 189603

[JonY]

[-- Attachment #1: Type: text/plain, Size: 491 bytes --]

On 9/5/2012 17:15, niXman wrote:
> 2012/8/21 JonY:
> 
> I can't still to build trunk %)
> 
> 
>> Well, there is no reason to, once the Borland patents expire for win32.
> Tell me please, when the patent expires?
> 
> 

I am not familiar with patent laws, so I can't say how long it lasts.

See USPTO Patent #5,628,016
<http://patft.uspto.gov/netacgi/nph-Parser?Sect2=PTO1&Sect2=HITOFF&p=1&u=/netahtml/PTO/search-bool.html&r=1&f=G&l=50&d=PALL&RefSrch=yes&Query=PN/5628016>



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 196 bytes --]