Apply updates from libbitcoin-build for gcc GNU/Linux dynamic builds#393
Merged
thecodefactory merged 1 commit intolibbitcoin:masterfrom Oct 28, 2016
Merged
Apply updates from libbitcoin-build for gcc GNU/Linux dynamic builds#393thecodefactory merged 1 commit intolibbitcoin:masterfrom
thecodefactory merged 1 commit intolibbitcoin:masterfrom
Conversation
Member
Author
|
gcc static failure due to boost download failure (network unreachable). Re-running. |
Member
Author
|
The clang failure was in the middle of building the tests and exceeded the time limit, but appears to not be a real failure. |
thecodefactory
force-pushed
the
master
branch
from
92fa438 to
ec662f3
Compare
thecodefactory
force-pushed
the
master
branch
from
ec662f3 to
547c313
Compare
|
Changes Unknown when pulling 547c313 on thecodefactory:master into * on libbitcoin:master*. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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 is a test. If Travis-CI is happier building dynamic gcc targets with this configuration, we should consider it.