Skip to content

Make changes - #11

Open
tkraiser-arista wants to merge 8 commits into
yahoo:candidate_release_1_2from
tkraiser-arista:makeChanges
Open

Make changes#11
tkraiser-arista wants to merge 8 commits into
yahoo:candidate_release_1_2from
tkraiser-arista:makeChanges

Conversation

@tkraiser-arista

Copy link
Copy Markdown

Description

Change Makefiles to not hard-code bin64/lib64. Use GNUIncludes to find the right architecture.
Don't use hard-coded CMAKE_INSTALL_PREFIX. Pass it via the Makefile. That allows people using different destination install prefixes to call cmake passing their own defaults.
Change tests so they can be run with slim-build defines.

Related Issue

Motivation and Context

Allows netchasm to be linked as a 32-bit platform and the installation to reach the right directories.
Allows unit tests to be run when slim-build defines are used.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • [ X] My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • [ X] I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • [ X] All new and existing tests passed.

tkraiser-arista and others added 8 commits October 14, 2019 14:06
Change test files so it can compile for slim-builds
- HMStorageObserver can be extended and don't affect NetCHASM code.
Fix code that is formatting int64_t as %u for 32 bits platforms
Get rid of signal action initializations
Make routine non blocking.
Shutdown routine can be called standalone.
curl_global_init is called from curl_easy_init and is not thread-safe.  Since NetCHASM has multiple threads calling curl_easy_init we hit at least in one of our stress tests a double-free on the stack call of curl_global_init.  We could see from the core that other threads were executing curl calls while the thread that hit the double-free was still finishing the curl_global_init.
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

Successfully merging this pull request may close these issues.

1 participant