Update Makefile #3
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…s a part of 'patch' target
…the device part of a src/dst MAC address
…_dst iff a ClassBench-generated rule contains a non-wildcard nw_proto/tp_src/tp_dst field
…eration of IPv4, IPv6, and OpenFlow rule sets
…in the original ClassBench and patch combining ClassBench improvements with IPv6 support
Known issues on Ubuntu 17.04.
…tack smashing error" on (probably not only) Ubuntu 17.04 Patch provided by Salvatore Pontarelli <salvatore.pontarelli@uniroma2.it>.
"Stack smashing error" on Ubuntu 17.04 removed from the list of known issues.
Updated the Known Issues list.
…rce code There was no return type defined for ClassBench's main function.
…rce code Sometimes Null (i.e., an integer constant equal to 0) was used instead of NULL (i.e., a null pointer), which caused an error in newer C++ compilers (because of unsupported comparison of a pointer with an integer).
Add ipaddress gem to Gemfile
…distribution. Both ClassBench and ClassBench-ng represent prefix pair lengths using a total prefix length and a source prefix length.
… its parsing. This approach is more defensive than relying on a users's call of the 'calculate_stats' method and it is more sensible than calling this method at the beginning of the 'generate_seed' method.
…ples Analyser. Similarly fo OpenFlow Analyser, an output seed is printed directly to the stdout.
…yser. The used format (position-based or short parameters) is simpler and it better follows the format already used by other parts of ClassBench-ng (e.g., OpenFlow Analyser).
…er to global stdout and stderr, respectively. Before this commit, everything was put to global stdout only.
…he help. A shorter description is expected to be read by more users.
…n README. A shorter description is expected to be read by more users.
…nning of the Usage section. This kind of information fits better to this place.
…ements. Python3 is required by tuples_analyzer (see the "analyse tuples" mode).
OpenFlow analysis in the code. This order is more logical and applied also throughout the ClassBench-ng paper and documentation.
Nowadays, this is necessary for a successful download of original ClassBench and its parameter files.
The folder path here contains an extra "vendor", causing the compilation process to fail. This is because during the make process, the working directory is already within the "vendor" folder. After testing, modifying it in this way allows for successful compilation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This extra "vendor" in the folder path is causing the compilation process to fail, as it is unable to locate the corresponding files during compilation. The correction involves removing this additional "vendor" to ensure the correct file paths are used. After making this adjustment, the compilation should proceed successfully.
