configure error on 32-bit Ubuntu Saucy

TheBlueMatt commented at 9:39 pm on March 23, 2014: member

checking for main in -lminiupnpc… (cached) yes checking for boostlib >= 1.20.0… yes checking whether the Boost::System library is available… yes configure: error: Could not find a version of the library! make[1]: *** [override_dh_auto_configure] Error 1

works on amd64, however…

See https://launchpadlibrarian.net/170491643/buildlog_ubuntu-saucy-i386.bitcoin_0.9.0-saucy1_FAILEDTOBUILD.txt.gz

TheBlueMatt commented at 9:40 pm on March 23, 2014: member

Quite possibly me missing something, but that error message is completely indecipherable.

laanwj added the label Build system on Mar 24, 2014

laanwj commented at 7:22 am on March 24, 2014: member

Do you have config.log output?

TheBlueMatt commented at 3:54 pm on March 24, 2014: member

The above log is all I have, sorry.

TheBlueMatt commented at 3:55 pm on March 24, 2014: member

If I have time, I’ll try to rerun the build with a cat config.log at the end.

laanwj commented at 9:25 am on March 31, 2014: member

Usually this means that boost libraries are installed in multiple locations, and autoconf picks the wrong location. You could –with-boost-libdir= to explicitly set a directory.

theuni commented at 4:43 pm on April 7, 2014: member

http://git.savannah.gnu.org/cgit/autoconf-archive.git/commit/m4/ax_boost_base.m4?id=7a97956f261a43897e88c14ef3b2f650fadc8556

Updating to #serial 23 should fix. Will PR it.

theuni referenced this in commit 13a2283a6d on Apr 7, 2014

theuni commented at 5:23 pm on April 7, 2014: member

@TheBlueMatt This should fix your issue, but I’m unable to test. Could you please confirm?

laanwj closed this on Apr 8, 2014

TheBlueMatt commented at 2:03 am on April 20, 2014: member

Nope, this bug still exists on both saucy and trusty: https://launchpad.net/~bitcoin/+archive/bitcoin/+packages

sipa reopened this on Apr 20, 2014

theuni commented at 8:03 pm on April 23, 2014: member

@TheBlueMatt Could you please grab a config.log for this?

floe commented at 7:28 pm on May 29, 2014: none

I’ve tried to reproduce this, finally managed to extract the config.log from the pbuilder environment. See here: http://pastebin.com/ML1PYR93

theuni commented at 4:48 am on June 11, 2014: member

Debian is building 0.9.1 which didn’t get 13a2283a6. 0.9.2 contains it, so that should work. @floe unless you’re able to reproduce with the 0.9.2 branch or rc tags, this has been taken care of.

floe commented at 11:50 am on June 11, 2014: none

@TheBlueMatt could you push new packages for 0.9.2 to your PPA? Would probably be the quickest way to test this.

laanwj commented at 12:01 pm on June 11, 2014: member

0.9.2 final is not released yet, so pushing packages for it makes no sense. We’ve never done PPAs for release candidates.

floe commented at 12:43 pm on June 11, 2014: none

@laanwj oops, my bad. will test on my machine, then.

TheBlueMatt commented at 7:44 pm on June 11, 2014: member

@theuni: I had tried with 13a2283, but that did not resolve the problem. Have there been any other changes which could effect this?

theuni commented at 9:26 pm on June 11, 2014: member

No, that should do it. You made sure to re-run autogen.sh ?

TheBlueMatt commented at 9:40 pm on June 11, 2014: member

yea, they all run from a clean state.

TheBlueMatt commented at 1:44 am on August 5, 2014: member

Seems to have worked with 0.9.2.1.

TheBlueMatt closed this on Aug 5, 2014

MathyV referenced this in commit 088dc2beb2 on Oct 27, 2014

MarcoFalke locked this on Sep 8, 2021

configure error on 32-bit Ubuntu Saucy #3945