<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">log for gcc build: <a href="https://pastebin.com/qbmWHm1M" class="">https://pastebin.com/qbmWHm1M</a></div><div class=""><br class=""></div><div class="">log for clang12 build: <a href="https://pastebin.com/4WG7VsfA" class="">https://pastebin.com/4WG7VsfA</a></div><div class=""><br class=""></div><div class="">clang14 is more restrictive on C implementation:<br class=""><br class="">:info:build /usr/bin/clang -O2 -Wall -Wno-narrowing -I./ -I/opt/local/include -I/opt/local/include/GL -I../../libSNL/src -I../../glut-3.5/src -c -o parser.o parser.c<br class="">:info:build parser.c:85:5: error: implicit declaration of function 'DrawCommandLine' is invalid in C99 [-Werror,-Wimplicit-function-declaration]<br class="">:info:build DrawCommandLine(keystroke, strlen(keystroke)+*curshft);<br class="">:info:build ^<br class="">:info:build 1 error generated.<br class="">:info:build make: *** [parser.o] Error 1<br class=""></div><br class=""><div class="">
<div class="">Mark Brethen</div><div class=""><a href="mailto:mark.brethen@gmail.com" class="">mark.brethen@gmail.com</a></div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Jul 27, 2022, at 3:49 AM, Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk" class="">jonesc@hep.phy.cam.ac.uk</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class="">Please post a complete, clean, build log for the port in question.<br class=""><br class="">In general GCC should not be used to build c++ (*) as doing so leads to these c++ runtime mis-matches. You should use clang for c++ (and c as well, although there is no runtime issues there).<br class=""><br class="">cheers Chris<br class=""><br class="">* The latest GCC versions now actually support building against libc++, the clang runtime, which would make this possible in theory. It needs support in base though (<a href="https://github.com/macports/macports-base/pull/275" class="">https://github.com/macports/macports-base/pull/275</a>) so cannot be used until that is available.<br class=""><br class="">On 27/07/2022 1:15 am, Mark Brethen wrote:<br class=""><blockquote type="cite" class="">Installing CalculiX with a clang variant is successful, however when selecting a gcc variant:<br class="">---> Scanning binaries for linking errors<br class="">---> No broken files found.<br class="">CalculiX is using libstdc++ (this installation is configured to use libc++)<br class="">---> Found 1 broken port, determining rebuild order<br class="">You can always run 'port rev-upgrade' again to fix errors.<br class="">The following ports will be rebuilt: CalculiX @2.18+docs+examples+gcc12<br class="">Continue? [Y/n]:<br class="">Choosing ‘Y’ puts it into and endless re-install. Adding 'configure.cxx_stdlib macports-libstdc++’ seems to fix things.<br class="">1. What is causing this?<br class="">2. Should the compilers group be removed and stick with clang?<br class="">3. What changes to the portfile would need to made to permit either compiler variant?<br class="">Thanks,<br class="">Mark<br class=""></blockquote></div></div></blockquote></div><br class=""></body></html>