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

Issue with building OpenFast on Ubuntu 18.04 using CMake #383

Closed
rhaghi opened this issue Jan 21, 2020 · 3 comments
Closed

Issue with building OpenFast on Ubuntu 18.04 using CMake #383

rhaghi opened this issue Jan 21, 2020 · 3 comments
Assignees

Comments

@rhaghi
Copy link

rhaghi commented Jan 21, 2020

Hello,

I am new to compiling Fortran and C on my machine. I followed the same steps that you explained here. However, while building OpenFast, I faced with some errors. All the errors seem to say the same: Warning: __builtin_memset: specified size 18446744073709551598 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=], but the ErrMsg is different. I uploaded screenshots from my terminal. My machine OS is Ubuntu 18.04 running on IntelCore i7-2600 CPU with 16GB ram. The cmake version on my machine is 3.10.2, gcc version is 7.4.0, and make version is 4.1.

I am not sure if you can reproduce the error as it might be my machine specific. However, to reproduce the error run the following on a Linux machine terminal (this is mainly a copy-paste from the installation instruction page):

  1. git clone https://github.com/OpenFAST/OpenFAST.git
  2. cd OpenFAST
  3. mkdir build
  4. cd build
  5. cmake ..
  6. make

Thanks a lot for the help.
Screenshot from 2020-01-21 14-46-07
Screenshot from 2020-01-21 14-44-34
Screenshot from 2020-01-21 14-45-03
Screenshot from 2020-01-21 14-45-33

@andrew-platt
Copy link
Collaborator

Thanks for the bug report. This is a known error that can be safely ignored.

You will notice that this only occurs on string manipulations involving ErrMsg. In these cases, we are truncating a string and prepending a few characters or words. The newly created string can't actually exceed the allocated size, so it isn't actually an issue to worry about. We simply haven't gotten around to modifying the logic to make that cleaner.

@rhaghi
Copy link
Author

rhaghi commented Jan 22, 2020

Thanks a lot @andrew-platt :)

@rafmudaf
Copy link
Collaborator

rafmudaf commented Jan 22, 2020

Its also only a thing on GCC 7 ¯\_(ツ)_/¯

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

No branches or pull requests

3 participants