No description provided.
Add AC_MSG_ERROR and AC_MSG_FAILURE for Ubuntu 13.10 libboost1.54-all-dev incompatibility error. #3447
pull sudosurootdev wants to merge 14 commits into bitcoin:master from sudosurootdev:master changing 2 files +20 −3-
sudosurootdev commented at 8:38 AM on December 20, 2013: none
-
Add AC_MSG_ERROR for Ubuntu 13.10 libboost1.54-all-dev error: Could not link against libboost::chrono 1b3efca1ed
-
laanwj commented at 8:43 AM on December 20, 2013: member
Is it possible to add this code to the main configure.ac instead of
m4/ax_boost_chrono.m4? I like to keep those exactly in sync with upstream. -
sudosurootdev commented at 8:48 AM on December 20, 2013: none
I looked at that first, it may be possible, but the error that is alerted now is 'Could not link against libboost::chrono !' which comes directly from m4/ax_boost_chrono.m4
I am sort of newbie at programming, learning, and tried to find where I could add in configure.ac but there is so much in there with so many OS's and arch's that I can't figure it out. Please do add or assign to someone who is familiar with configure.ac as I know that would be the cleaner way.
Also, should probably be added to doc/build-unix.md
-
Update ax_boost_chrono.m4 1da91e7793
-
c2a8999161
Update configure.ac
Added AC_MSG_ERROR to configure.am for Ubuntu 13.10 users with libboost1.54-all-dev and libboost1.53 fatal error alert 'Could not link against libboost::chrono !' instruction to remove libboost1.54-all-dev and install libboost1.53-all-dev.
-
sudosurootdev commented at 9:49 AM on December 20, 2013: none
I moved the alert over to configure.am removed it from the m4 macros, it just took me a but longer to figure it out than most people here, I'm sure. But, I figured it out. I prefer it that way anyway, as everything should be pre-checked in configure.am and it keeps the code cleaner and easier work with having it that way.
--edit-- sorry I did a separate pull request, not sure if that was the way, but I am also new to GIT.
-
Update build-unix.md 2ef355b272
-
3797b8e843
Update build-unix.md
Added Ubuntu 13.10 specific instuctions to deal with libboost1.54-all-dev incompatibility and fatal error alert 'Could not link against libboost::chrono !'
-
Update configure.ac aed4226fb8
-
Update build-unix.md c11e1733ab
-
Update configure.ac 27b8df4290
-
Update ax_boost_chrono.m4 0342101fb5
-
Merge branch 'master' into fix 64b9f937ce
-
be5f630071
Update configure.ac
Attempt to add alert in with `if test x$boost_sleep != xyes; then` statement.
-
Update configure.ac fc48f9857e
-
ef47b826c5
Merge branch 'fix' of https://github.com/sudosurootdev/bitcoin
Conflicts: configure.ac
-
68e15ff88b
Update configure.ac
Only throw AC_MSG_FAILURE about Ubuntu 13.10 libboost1.54-all-dev incompatibility if BOOST_VERSION >= 105300 && <= 105400
-
BitcoinPullTester commented at 10:18 PM on December 20, 2013: none
Automatic sanity-testing: FAILED BUILD/TEST, see http://jenkins.bluematt.me/pull-tester/68e15ff88b669d1cda76892ed4d8addabfd1ff8b for binaries and test log.
This could happen for one of several reasons:
- It chanages paths in makefile.linux-mingw or otherwise changes build scripts in a way that made them incompatible with the automated testing scripts (please tweak those patches in qa/pull-tester)
- It adds/modifies tests which test network rules (thanks for doing that), which conflicts with a patch applied at test time
- It does not build on either Linux i386 or Win32 (via MinGW cross compile)
- The test suite fails on either Linux i386 or Win32
- The block test-cases failed (lookup the first bNN identifier which failed in https://github.com/TheBlueMatt/test-scripts/blob/master/FullBlockTestGenerator.java)
If you believe this to be in error, please ping BlueMatt on freenode or TheBlueMatt here.
This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
-
laanwj commented at 2:21 PM on January 14, 2014: member
Can you squash this into a single commit?
- sudosurootdev closed this on Jan 14, 2014
-
laanwj commented at 10:00 PM on January 14, 2014: member
No need to close the pull, you can make changes and push to the same branch, and it will appear in the current pull request.
-
sudosurootdev commented at 10:11 PM on January 14, 2014: none
It was easier for me this way, I got myself so confused with the multiple commits, plus I deleted the whole fork. Here is new pull #3542
Sincerely, Christopher Latham primary: sudosurootdev@gmail.com secondary: investor2webhost@gmail.com
Bitcoin, Crypto-Currencies, Web development, Programming, Investing, & Marketing are my specialities! Contact me about any!
Donations Always Appreciated and used for projects! My Primary Bitcoin Addresses: https://blockchain.info/address/1GrPK9t5PdXf6Vi8sMend4HN4AWJsuqF4s https://blockchain.info/address/1EBwKjFNHCY4pv3UKsAyhWRdeK1cEHAuyj https://blockchain.info/address/1JUNNsHY1HWJauwZaThnfWLoPkqCfGDmb7 https://blockchain.info/address/148yDGUpse5jkA6F6y9MD2kZ8UCFHUQQ3T https://blockchain.info/address/1hashFXV8J6YPBmgCdjKBv7BrcWzRh7Wb https://blockchain.info/address/1RedJJLBmQXLXFpdtbZ2TXKAPQkUhjK8B
CEX.io - Bitcoin Commodity Exchange https://cex.io/r/0/allbiznessman/0/ [image: Inline image 2] https://cex.io/r/0/allbiznessman/0/ https://cex.io/r/0/allbiznessman/0/
On Tue, Jan 14, 2014 at 5:01 PM, Wladimir J. van der Laan < notifications@github.com> wrote:
No need to close the pull, you can make changes and push to the same branch, and it will appear in the current pull request.
— Reply to this email directly or view it on GitHubhttps://github.com/bitcoin/bitcoin/pull/3447#issuecomment-32312256 .
-
sudosurootdev commented at 4:44 PM on February 22, 2014: none
AllBiznessMan sent you an invitation
Twitter helps you stay connected with what's happening right now and with the people and organizations you care about.
Accept invitationhttps://twitter.com/i/67cf248b-7a52-4c14-9855-9fda0a727b85
This message was sent by Twitter on behalf of Twitter users who entered your email address to invite you to Twitter. Unsubscribe: https://twitter.com/i/o?t=1&iid=c1faf3df111e4cb193afcd6be7c5ad3c&uid=0&c=IuVwbCB3dgFDyhHoz4iUgFLi%2FRgzuJCGEW%2BhCRnMsKk0hZ1i%2FOklXjGLWCwoZaDS%2BlMcAlknyqQwCjdHECCBGoIGcQTJ8ty8muua6cr%2FsEuk1ORIZXcs%2Fg%3D%3D&nid=9+26
Need help? https://support.twitter.com
- DrahtBot locked this on Sep 8, 2021