Fix “checking build system type… Invalid configuration `x86_64-unknown-linux’: machine `x86_64-unknown’ not recognized” on ./configure

I’m trying to compile vqadmin on x86_amd64 (64 bit Debian) and I got error during ./configure . The error I got is as follows:

debian:~/vqadmin-2.3.7# ./configure --enable-cgibindir=/var/www/mail/cgi-bin -enable-htmldir=/var/www/mail/ --enable-isoqlog=y
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/downloads/vqadmin-2.3.7/missing: Unknown `--run' option
Try `/downloads/vqadmin-2.3.7/missing --help' for more information
configure: WARNING: `missing' script is too old or missing
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... Invalid configuration `x86_64-unknown-linux': machine `x86_64-unknown' not recognized

So my compile failed with:
checking build system type… Invalid configuration `x86_64-unknown-linux’: machine `x86_64-unknown’ not recognized

Thanksfully, there is a tiny script which originally is part of the CVS project. I’ve modified a bit the script to remove few lines of code which are not necessery. The `x86_64-unknown-linux’: machine `x86_64-unknown’ not recognized fix script fix_x86_64-unknown-linux-gnu.sh is here

To fix up the broken configure all required is:

debian:~/vqadmin-2.3.7# sh fix_x86_64-unknown-linux-gnu.sh

Next on I could compile normally again vqadmin just fine.

Related Posts

Tags: , , , , , , , , , , , , , , , , , , , , , , , ,

7 Responses to “Fix “checking build system type… Invalid configuration `x86_64-unknown-linux’: machine `x86_64-unknown’ not recognized” on ./configure”

  1. Thibs says:

    Hello,

    I’ve try your fix on the same environment and I have following error :

    fix_x86_64-unknown-linux-gnu.sh: 49: aclocal: not found
    fix_x86_64-unknown-linux-gnu.sh: aclocal failed

    Do you have any idea about it ?

  2. hip0 says:

    Hello,

    You will have to install automake.
    (if debian)
    # apt-get install automake
    ( fedora, centos and other redhat derivatives)
    #yum install automake

    Hope this helps :)

    Best!
    Georgi

  3. Thibs says:

    Thanks for the tips !

    My other alternative was to use the config.sub file from vpopmail-5.4.33 (just replace config.sub in the root directory of vqadmin-2.3.7)

  4. Swarnendu Biswas says:

    Hi,

    I am facing the following error when executing the script.

    oc/api/Makefile.am:1: CREATE_API_DOCS does not appear in AM_CONDITIONAL
    doc/api/Makefile.am:9: CREATE_API_DOCS does not appear in AM_CONDITIONAL
    doc/api/Makefile.am:39: CREATE_API_DOCS does not appear in AM_CONDITIONAL
    lib/Makefile.am:30: INSTALL_GLIBJ_ZIP does not appear in AM_CONDITIONAL
    lib/Makefile.am:36: BUILD_CLASS_FILES does not appear in AM_CONDITIONAL
    lib/Makefile.am:40: INSTALL_CLASS_FILES does not appear in AM_CONDITIONAL
    lib/Makefile.am:106: REGEN_PARSERS does not appear in AM_CONDITIONAL
    fix_x86_64-unknown-linux-gnu.sh: automake failed

    Any idea how this issue can be resolved?

  5. Arthur Helfstein Fragoso says:

    like @Thibs said the file ‘config.sub’ contains the supported CPUs, if it’s an old version, it wont support newer CPUs.

    you can get the latest version of ‘config.sub’ from:
    http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD

    just copy the latest version of ‘config.sub’ and replace to the one that’s in the folder of what you are trying to run the ./configure

    good luck to anyone having the same problem ;)

  6. saza says:

    libtoolize –force

Leave a Reply

Yandex Mail.ru Google LiveJournal myOpenId Flickr claimId Blogger Wordpress OpenID Yahoo Technorati Vidoop Verisign AOL