Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Difference in compilations results between AWS for logging. #52

Open
Matthewar opened this issue Nov 23, 2017 · 2 comments
Open

Difference in compilations results between AWS for logging. #52

Matthewar opened this issue Nov 23, 2017 · 2 comments

Comments

@Matthewar
Copy link

Hi,

When compiling on my machine, I get no errors, however in the automated runs the arguments to the log functions are throwing errors - is there some setting that is different between these so they can be diagnosed on the local machine?

@m8pple
Copy link
Contributor

m8pple commented Nov 24, 2017

I'm not sure what you mean - the compilation settings should be in the log file? Do you
mean on your own AWS instance (in which case you should be able to do the same
command as in the log (which is just using your makefile)), or on your laptop?

My guess is that if you're getting errors with the logging, you're trying to pass something
through that is a class, rather than a base C type. e.g. you're trying to log a std::string,
but you need to call .c_str() to pass it to log (as log behaves like printf). Not sure why
that would compile on other machines though.

@Matthewar
Copy link
Author

Yes, I was trying to pass it a c str instead but the bit I was confused about was that it let me compile it with no issues on my machine (although I got some weird outputs when it printed).
On the AWS instance it wouldn't compile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants