gtest linking warnings with static builds on cray systems about blt HOT 5 OPEN

On Cray, setting the following env var:

export CRAYPE_LINK_TYPE=dynamic

Eliminates these warnings.

I think this might be a good-enough solution.

from blt.

It may achieve the same effect, but the wrappers (cc, CC, ftn) also accept a -dynamic flag. It may have an identical effect.

from blt.

awesome, we can try to provide those as defaults for cray compiler wrappers. Although I don't think we identify the cray compiler wrappers yet.

from blt.

from blt.

Good point -- these cases are actually where we want to create static libs, but some of the deps (gtest in this case, and things like hdf5 in others) have dlopens, etc that we can't avoid, so we have to link to the shared runtime.

So I agree -- maybe we don't default to adding the flag, but if we could direct the compiler wrappers (or even the just that we are on a cray) it would make it easier for projects to add them when necessary.

from blt.