Cython is failing to build (%check) on f24 (gcc6)

[Neal Becker]

Running %check is giving a compile error.  What's the easiest way to see 
what the error message is?

https://kojipkgs.fedoraproject.org//work/tasks/3468/12893468/build.log

[Zbigniew Jędrzejewski-Szmek]

On Fri, Feb 05, 2016 at 09:43:24AM -0500, Neal Becker wrote:
>  Running %check is giving a compile error.  What's the easiest way
> to see 
>  what the error message is?
>  
>  https://kojipkgs.fedoraproject.org//work/tasks/3468/12893468/build.log 
Add at the end of %check:
|| gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4
-grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4
-grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/builddir/build/BUILD/Cython-0.23.4/tests/run
-I/usr/include/python2.7 -c complex_numbers_c89_T398.cpp -o
/builddir/build/BUILD/Cython-0.23.4/BUILD/run/cpp/complex_numbers_c89_T398/complex_numbers_c89_T398.o
-DCYTHON_REFNANNY=1

Zbyszek

[Neal Becker]

Zbigniew Jędrzejewski-Szmek wrote:

>  On Fri, Feb 05, 2016 at 09:43:24AM -0500, Neal Becker wrote:
> > Running %check is giving a compile error.  What's the easiest way to see
> > what the error message is?
> > 
> > https://kojipkgs.fedoraproject.org//work/tasks/3468/12893468/build.log
>  
>  Add at the end of %check:
>  || gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
>  || -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
>  || -fstack-protector-strong --param=ssp-buffer-size=4
>  || -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
>  || -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe
>  || -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
>  || -fstack-protector-strong --param=ssp-buffer-size=4
>  || -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
>  || -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC
>  || -I/builddir/build/BUILD/Cython-0.23.4/tests/run
>  || -I/usr/include/python2.7 -c complex_numbers_c89_T398.cpp -o
>  || 
/builddir/build/BUILD/Cython-0.23.4/BUILD/run/cpp/complex_numbers_c89_T398/complex_numbers_c89_T398.o
>  || -DCYTHON_REFNANNY=1
>  
>  Zbyszek
>  --
>  devel mailing list
>  devel(a)lists.fedoraproject.org
>  http://lists.fedoraproject.org/admin/lists/[e-mail] 
Yes, but I want to see the compiler error message

[Jonathan Wakely]

On 05/02/16 11:33 -0500, Neal Becker wrote:
> Zbigniew Jędrzejewski-Szmek wrote:
>
> > On Fri, Feb 05, 2016 at 09:43:24AM -0500, Neal Becker wrote:
> >> Running %check is giving a compile error.  What's the easiest way to see
> >> what the error message is?
> >>
> >> https://kojipkgs.fedoraproject.org//work/tasks/3468/12893468/build.log
> >
> > Add at the end of %check:
> > || gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall
> > || -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> > || -fstack-protector-strong --param=ssp-buffer-size=4
> > || -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
> > || -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe
> > || -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> > || -fstack-protector-strong --param=ssp-buffer-size=4
> > || -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
> > || -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC
> > || -I/builddir/build/BUILD/Cython-0.23.4/tests/run
> > || -I/usr/include/python2.7 -c complex_numbers_c89_T398.cpp -o
> > ||
> /builddir/build/BUILD/Cython-0.23.4/BUILD/run/cpp/complex_numbers_c89_T398/complex_numbers_c89_T398.o
> > || -DCYTHON_REFNANNY=1
> >
> > Zbyszek
> > --
> > devel mailing list
> > devel(a)lists.fedoraproject.org
> > http://lists.fedoraproject.org/admin/lists/[e-mail]
>
> Yes, but I want to see the compiler error message 
That will run the compiler, and its stdout/stderr will be captured in
the build.log as other output is. You don't see it now because the
command is run by another process which swallows the output.

Alternatively, build in a mock chroot and when it fails enter the
chroot and run the compiler command by hand.