clang argument error during model compile on MacOS about bridgestan

[WardBrian]

Hi @fonnesbeck -

This is a strange error, since it comes from one of the Stan-math dependencies, but as far as I can tell they only pass that argument when using GCC, not clang:
https://github.com/search?q=repo%3Astan-dev%2Fmath+lifetime-dse+NOT+language%3AText&type=code

Do you use any other Stan interface (e.g. CmdStan)? Was this error present there?

[fonnesbeck]

Yes, I just ran the model successfully using the same data under cmdstanpy. Not sure if their default compile args are the same as under bridgestan or not.

[WardBrian]

Could you show the output of make -d?

there shouldn’t be any differences between cmdstan’s tbb make rules and bridgestans, but clearly something is up

[fonnesbeck]

I've been running bridgestan via nutpie. Do you just want make -d from within the bridgestan source directory?

[WardBrian]

Running make manually would definitely work, but you might be able to pass -v as an extra argument in the nutpie wrapper

[WardBrian]

@fonnesbeck thanks - could you try the same thing but building a model? for example make -v test_models/multi/multi_model.so from the bridgestan folder

[fonnesbeck]

The -v flag just returns the make version. Running with -d seems to hang here when running the multi_model example:

Reading makefiles...
Reading makefile '/Users/cfonnesbeck/GitHub/bridgestan/stan/lib/stan_math/lib/tbb_2020.3/build/Makefile.tbbmalloc'...
Reading makefile '../tbb_2020.3/build/common.inc' (search path) (no ~ expansion)...
make[1]: Entering directory '/Users/cfonnesbeck/GitHub/bridgestan/stan/lib/stan_math/lib/tbb'
Reading makefile '../tbb_2020.3/build/macos.inc' (search path) (no ~ expansion)...
Reading makefile '../tbb_2020.3/build/macos.clang.inc' (search path) (no ~ expansion)...

[WardBrian]

My bad, I meant -d.

That's very interesting, since that file it is reading does not have the -flifetime-dse=1 argument, macos.gcc.inc does.

How long did you let it spin before killing it?

[fonnesbeck]

Still running!

[WardBrian]

Hm, very odd. If you have a working cmdstan you should be able to literally copy the tbb files from that over and it should work, but that doesn't answer why this is happening still

[fonnesbeck]

Yes, very curious. Moreover, it happens on two different machines.

[fonnesbeck]

This appears to be some odd side-effect of running Python from within VSCode. If I run the model from a terminal, the error does not occur. Not sure why, but clearly has nothing to do with bridgestan, so I will close this. Apologies!

[WardBrian]

Oh very odd! I wonder if there are any environment variables being set by VSCode which Make is then picking up

[aseyboldt]

I guess you use conda, right?
Maybe it could also have something to do with environment variables set by conda? Especially if you are not using bash interactively, some variables might then not get set, even if you activate an env? I think CVCode always uses the bash activate scripts.