https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123976
--- Comment #177 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Peter Dyballa from comment #172) > (In reply to Iain Sandoe from comment #169) > > (In reply to Peter Dyballa from comment #168) > > > > > > CC=powerpc-apple-darwin9-gcc CXX=powerpc-apple-darwin9-c++ > > > > so .. gcc10-bootstrap is just a vanilla install without any of the -mp-nn or > > so on? it seems it is ... > leopard pete 233 /\ ls -li /opt/local/libexec/gcc10-bootstrap/bin > total 84528 > 139299438 -rwxr-xr-x 4 root admin 1504800 27 Dez 2024 c++ > 139299439 -rwxr-xr-x 1 root admin 1504884 27 Dez 2024 cpp > 139299438 -rwxr-xr-x 4 root admin 1504800 27 Dez 2024 g++ > 139299442 -rwxr-xr-x 3 root admin 1500704 27 Dez 2024 gcc <snip> > 139299438 -rwxr-xr-x 4 root admin 1504800 27 Dez 2024 > powerpc-apple-darwin9-c++ > 139299438 -rwxr-xr-x 4 root admin 1504800 27 Dez 2024 > powerpc-apple-darwin9-g++ > 139299442 -rwxr-xr-x 3 root admin 1500704 27 Dez 2024 <snip> > > Ah! I should try next time with CXX=powerpc-apple-darwin9-g++ that it > matches CC=powerpc-apple-darwin9-gcc. yes .. configure _will be confused otherwise - configure believes everything you say and that you know what you're doing :) > The compilers are all hardlinks, but > maybe they behave differently based on the name they are invoked. no they don't - but on most newer macOS versions "gcc" and "g++" get intercepted by clang which pretends to be them - but not always successfully .. so it's best to be specific and name GCC if you mean it (and use CC=clang CXX=clang++ if you mean to use clang).. Not relevant on 10.5 at present .. but very relevant on newer OS versions.
