Bug 273672

Summary: comms/wsjtx: Fails to build with GCC 13: error: typedef redefinition with different types ('size_t' (aka 'unsigned long') vs 'int')
Product: Ports & Packages Reporter: Lorenzo Salvadore <salvadore>
Component: Individual Port(s)Assignee: hamradio (Nobody) <hamradio>
Status: Open ---    
Severity: Affects Only Me CC: salvadore
Priority: --- Flags: bugzilla: maintainer-feedback? (hamradio)
Version: Latest   
Hardware: Any   
OS: Any   

Description Lorenzo Salvadore freebsd_committer freebsd_triage 2023-09-10 07:06:34 UTC 
This bug report blocks the update of GCC_DEFAULT to 13. This webpage can help finding ta fix: https://gcc.gnu.org/gcc-13/porting_to.html .

[  0%] Building Fortran object CMakeFiles/wsjt_fort_omp.dir/lib/packjt.f90.o
/usr/local/bin/gfortran13 -DBIGSYM=1 -DBOOST_ALL_DYN_LINK -DCMAKE_BUILD -DQT5 -DUNIX -I/wrkdirs/usr/ports/comms/wsjtx/work/.build/wsjtx-prefix/src/wsjtx-build -I/wrkdirs/usr/ports/comms/wsjtx/work/.build/wsjtx-prefix/src/wsjtx -O -Wl,-rpath=/usr/local/lib/gcc13 -fallow-argument-mismatch -O3 -DNDEBUG -O3 -fbounds-check -funroll-all-loops -fno-f2c -ffpe-summary=invalid,zero,overflow,underflow -Wall -Wno-conversion -fno-second-underscore -Jfortran_modules_omp -fvisibility=hidden -fopenmp -c /wrkdirs/usr/ports/comms/wsjtx/work/.build/wsjtx-prefix/src/wsjtx/lib/packjt.f90 -o CMakeFiles/wsjt_fort_omp.dir/lib/packjt.f90.o
--- CMakeFiles/wsjt_cxx.dir/all ---
In file included from <built-in>:1:
/wrkdirs/usr/ports/comms/wsjtx/work/.build/wsjtx-prefix/src/wsjtx-build/wsjtx_config.h:72:20: error: typedef redefinition with different types ('size_t' (aka 'unsigned long') vs 'int')
    typedef size_t fortran_charlen_t;
                   ^
/wrkdirs/usr/ports/comms/wsjtx/work/.build/wsjtx-prefix/src/wsjtx-build/wsjtx_config.h:68:15: note: previous definition is here
  typedef int fortran_charlen_t;
              ^
1 error generated.
Comment 2 Lorenzo Salvadore freebsd_committer freebsd_triage 2023-11-18 10:29:29 UTC 
I remove the block for GCC default version update: latest test on FreeBSD 13.2 did not report any issue with this port. The bug report can probably be safely closed once FreeBSD 12 goes EOL.