https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85007
--- Comment #8 from Eric Reischer <emr-gnu at hev dot psu.edu> ---
N/M -- I found the trigger.
I intend to use the 7.3 tree of "gcc-7.3" to do my compilation rather than the
system-search-provided "gcc". gnatmake-7.3 doesn't seem to want to use the
"gcc-7.3" provided in the same folder as it, so I had to manually provide
"--GCC=" on the gnatmake command line. This worked as expected. However, this
argument was not passed onto the gnatlink command, so I provided it in the GPR
file:
package Linker is
for Default_Switches ("Ada")
use ("-v","--for-linker=-Map","--for-linker="driver.map",
"--GCC=/path/to/gcc-7.3/bin/gcc-7.3");
end Linker;
When you add in the "--GCC" to the linker arguments in the GPR file, it calls
"gcc-7" (I'm unable to determine if it's actually calling my gcc-7.3, or if the
"." is causing it to trip up, and it's terminating the argument there), and
doesn't pass in the "-m32" flag.
If I leave out the "--GCC" argument from the GPR file, it compiles and links
successfully, and passes in the correct arguments to gcc to compile the binder
file (and curiously enough, the ALI file doesn't have the x86-64 line), but it
uses the default system gcc, not the one passed to gnatmake.
