When installing gcc from the lang/gcc meta port, there are no configurable options. The result is that if the system has been built without the 32 bit libraries, the gcc build fails.
Work around: Go to the relevant gcc (currently gcc9) port and make config first to disable the MULTILIB Build support for 32-bit and 64-bit targets. Then you can use the gcc meta port to successfully build and install gcc.
I see no reasonable way to address this within the ports infrastructure
(short of cloning ports and manually linking adding things).
And I don't think individual ports should carry responsibility here.
This looks like a deficiency of the system/approach you are leveraging
to install things? Shouldn't there be a way for the user to be asked
about options for ports that are pulled in via a dependency?
(In reply to Gerald Pfeifer from comment #1)
I'm sure you didn't really mean to shoot the messenger... the only system/approach I am leveraging to install gcc is the ports system.
I did try installing gcc9 directly, but then I end up with binaries which have an appended "9" which is not helpful unless one happens to have other versions also installed.
Naive suggestion: ditch the gcc meta port and add an option to the gcc version ports to install without the appendage of any number. Defaulting to adding the appendage should keep everyone happy.