Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

install_db4.sh configure cannot guess build type on ppc64le #16064

Closed
JeremyRand opened this issue May 21, 2019 · 1 comment · Fixed by #16086
Closed

install_db4.sh configure cannot guess build type on ppc64le #16064

JeremyRand opened this issue May 21, 2019 · 1 comment · Fixed by #16086

Comments

@JeremyRand
Copy link
Contributor

Describe the issue

The configure script called by install_db4.sh fails to detect the build arch on ppc64le systems, producing an error.

What behavior did you expect?

db4 should build properly without errors.

What was the actual behavior (provide screenshots if the issue is GUI-related)?

checking build system type... /home/user/Downloads/bitcoin/db4/db-4.8.30.NC/dist/config.guess: unable to guess system type

This script, last modified 2009-02-03, has failed to recognize
the operating system you are using. It is advised that you
download the most up to date version of the config scripts from

  http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
and
  http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD

If the version you run (/home/user/Downloads/bitcoin/db4/db-4.8.30.NC/dist/config.guess) is already up to date, please
send the following data and any information you think might be
pertinent to <config-patches@gnu.org> in order to provide the needed
information to handle your system.

config.guess timestamp = 2009-02-03

uname -m = ppc64le
uname -r = 4.19.0-5-powerpc64le
uname -s = Linux
uname -v = #1 SMP Debian 4.19.37-3 (2019-05-15)

/usr/bin/uname -p = 
/bin/uname -X     = 

hostinfo               = 
/bin/universe          = 
/usr/bin/arch -k       = 
/bin/arch              = 
/usr/bin/oslevel       = 
/usr/convex/getsysinfo = 

UNAME_MACHINE = ppc64le
UNAME_RELEASE = 4.19.0-5-powerpc64le
UNAME_SYSTEM  = Linux
UNAME_VERSION = #1 SMP Debian 4.19.37-3 (2019-05-15)
configure: error: cannot guess build type; you must specify one

How reliably can you reproduce the issue, what are the steps to do so?

  1. ./contrib/install_db4.sh `pwd`

What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)?

2d1583e , self-compiled.

What type of machine are you observing the error on (OS/CPU and disk type)?

In a VM running Whonix 15 (based on Debian Buster); host is Debian Buster. ppc64le / POWER9. HDD.

Any extra information that might be useful in the debugging process.

The following does work: ./contrib/install_db4.sh `pwd` --build=powerpc64le

While it would be nice to fix the configure script to properly detect powerpc64le, I'd settle for a note in build-unix.md that specifies the above workaround so that newbies don't have to figure out the configure flag on their own.

@fanquake
Copy link
Member

@JeremyRand Can you test #16086 ?

laanwj added a commit that referenced this issue May 29, 2019
…_db4.sh

00fade0 contrib: use newer config.guess & config.sub in install_db4.sh (fanquake)

Pull request description:

  The `config.guess` and `config.sub` packaged with `db-4.8.30.NC.tar.gz` are fairly old (2009) and fail to identify some system types i.e `ppc64le`. Replace them with more modern versions before configuring `db4`.

  Fixes #16064.

ACKs for commit 00fade:
  jamesob:
    tACK 00fade0
  dongcarl:
    utACK 00fade0
  laanwj:
    Tested ACK 00fade0

Tree-SHA512: 54f9f2b0fcf802e6a284214035fcb3833577aa5881beb293921b6036b71d0bcd0872f06d14ddc76a4f8c0eee7ba71461dcc99dc907e7ddb5ae403fc02b245538
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Dec 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
@JeremyRand @fanquake @maflcko and others