https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122807
--- Comment #9 from Michael Pot <fmw at actrix dot co.nz> --- (In reply to Andrew Pinski from comment #8) > As I mentioned before, target libraries are multi-lib'ed. But libgccjit is > NOT a target library, it is a host library. The only way for the host > library to be multi-lib (arch'ed) is building GCC twice. Because GCC itself > is only built for the host rather than built for the target too. Hi Andrew, Yes, I noted that as you mentioned above. Thank you for further explaining it, and I'll take that into account as I struggle through the portfile. I worried libgccjit is being built for the build arch, rather than the host arch. It will take me a few days to find the bandwidth to get back to working through the portfile :-) My main reason for identifying this software problem as an emerging issue for gcc, is concerns other programs use libgccjit just like the others in the same gcc directory. It may be catching out others who are cross compiling on other platforms too. I find the linker error messages quite cryptic for working out what the bad function call library is. Regardless of exactly which ones depend on libgccjit, everything that depends on the libraries provided by the projects using libgccjit, now can't be built universal, and so it goes on.... Thank you for your help and patience. Cheers Michael
