pkgsrc-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: lang/gcc10 failed to compile on SunOS



My build issue is seemed to be something with gfortran. But you are right, the build is parallel so it's difficult to know what actually faulty.

libtool: link: ranlib .libs/libgfortran.a
libtool: link: rm -fr .libs/libgfortran.lax .libs/libgfortran.lax
libtool: link: ( cd ".libs" && rm -f "libgfortran.la" && ln -s "../libgfortran.la" "libgfortran.la" )
gmake[6]: Leaving directory '/export/home/hung/pkgsrc/lang/gcc10/work/build/x86_64-sun-solaris2.11/32/libgfortran'
gmake[5]: Leaving directory '/export/home/hung/pkgsrc/lang/gcc10/work/build/x86_64-sun-solaris2.11/32/libgfortran'
gmake[4]: Leaving directory '/export/home/hung/pkgsrc/lang/gcc10/work/build/x86_64-sun-solaris2.11/libgfortran'
gmake[3]: Leaving directory '/export/home/hung/pkgsrc/lang/gcc10/work/build/x86_64-sun-solaris2.11/libgfortran'
gmake[2]: Leaving directory '/export/home/hung/pkgsrc/lang/gcc10/work/build/x86_64-sun-solaris2.11/libgfortran'
gmake[1]: Leaving directory '/export/home/hung/pkgsrc/lang/gcc10/work/build'
gmake: *** [Makefile:1008: all] Error 2
*** Error code 2

Stop.
bmake[1]: stopped in /export/home/hung/pkgsrc/lang/gcc10
*** Error code 1

Stop.
bmake: stopped in /export/home/hung/pkgsrc/lang/gcc10 




---- On Tue, 19 Jan 2021 16:34:54 +0700 Jonathan Perkin <jperkin%joyent.com@localhost> wrote ----

 > * On 2021-01-19 at 03:52 GMT, Hung Nguyen Gia wrote: 
 >  
 > > There is no error message printed on the screen. It just silently 
 > > fail after have going for more than 2 hours. I have no idea. 
 >  
 > It's a known failure.  You can see the full log here: 
 >  
 >  https://us-east.manta.joyent.com/pkgsrc/public/reports/upstream-trunk/20210117.2254/gcc10-10.2.0nb1/build.log 
 >  
 > The error being: 
 >  
 >  ../../../../gcc-10.2.0/libsanitizer/sanitizer_common/sanitizer_linux.cpp:903:63: error: 'O_DIRECTORY' was not declared in this scope 
 >  
 > Given the heavily threaded nature of the GCC build it can be difficult 
 > to find the actual error as so many other builds will be happening at 
 > the same time. 
 >  
 > The fix would be to apply a similar patch to this: 
 >  
 >  https://github.com/omniosorg/gcc/commit/7ce599ce25dc0b6d793c6bbedc21d6acdf4587c3#diff-8ae71675698739f1650d88779904f669f3294f69458ae94a693efe5a697f1ed3 
 >  
 > Generally on SunOS systems we use the illumos GCC tree, as it has a 
 > large number of patches that have not yet been (or will never be) 
 > upstreamed to mainline GCC. 
 >  
 > -- 
 > Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com 
 > 


Home | Main Index | Thread Index | Old Index