Add AC_MSG_ERROR and AC_MSG_FAILURE for Ubuntu 13.10 libboost1.54-all-dev incompatibility error.

[sudosurootdev]

No description provided.

[laanwj]

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]

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

[laanwj]

The only one around here that has a real clue about autotools is @cfields, and he's very busy with other things.

I'd suggest to just add a warning in the documentation in doc/build-unix.md for now.

[sudosurootdev]

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.

[BitcoinPullTester]

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:

1. 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)
2. It adds/modifies tests which test network rules (thanks for doing that), which conflicts with a patch applied at test time
3. It does not build on either Linux i386 or Win32 (via MinGW cross compile)
4. The test suite fails on either Linux i386 or Win32
5. 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]

Can you squash this into a single commit?

[laanwj]

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]

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//pull/3447#issuecomment-32312256
.

[sudosurootdev]

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 invitation

https://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