[Issue 18515] freebsd 11 ships with gcc unable to link 32 bit binaries, dmd uses it by default

d-bugmail at puremagic.com d-bugmail at puremagic.com
Sat Feb 24 08:32:20 UTC 2018


https://issues.dlang.org/show_bug.cgi?id=18515

Jonathan M Davis <issues.dlang at jmdavisProg.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |issues.dlang at jmdavisProg.co
                   |                            |m

--- Comment #1 from Jonathan M Davis <issues.dlang at jmdavisProg.com> ---
Looking at the source code for the compiler, the only place I see that the CC
environment variable is used is in src/dmd/link.d, and it looks like back in
October, Martin changed it so that it uses cc if CC is not set, and if I have
neither gcc nor g++ in my PATH on my 64-bit FreeBSD system, it compiles just
fine. I know that that didn't used to be the case, but it appears to be so now
- presumably thanks to Martin's changes to link.d. So, I don't know why the
auto-tester would be trying to use gcc or g++. There is some logic in posix.mak
where it tries to figure out whether clang or gcc is being used - primarily so
that it can figure out which compiler flags to use, I think. Glancing over it,
it looks like it uses c++ --version to figure that out, though if HOST_CXX is
set, it uses that instead of c++, and it might use CXX if that's set. So, maybe
the problem with the auto-tester relates to the makefile somehow? Certainly,
from what I can tell, the issue is not as simple as dmd using gcc by default
now if CC isn't set.

Does the environment for the autoster have CC, CXX, HOST_CC, or HOST_CXX set to
gcc or g++?

--


More information about the Digitalmars-d-bugs mailing list