Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


On Sat, Oct 02, 2010 at 11:00:16PM +0200, Thomas Klausner <wiz@NetBSD.org> wrote:
And I'm stuck at the next point:
9) I run "./autogen.sh --with-distro=LibreOfficeLinux --with-git
--with-max-jobs=16 --with-num-cpus=8" and then gmake (GNU make) and
configure dies with:
(...)
checking build system type... Invalid configuration `3.2.99.1': machine `3.2.99.1' not recognized
configure: error: /bin/bash ./config.sub 3.2.99.1 failed
gmake: *** [stamp/build] Error 1

Cedric had the same problem (he reported on IRC) on OSX:

12:43 <@cbosdonnat> thorsten, the error was: "checking build system type... Invalid configuration 
`3.2.99.1': machine `3.2.99.1' not recognized"

I got a similar one:

checking build system type... config.sub: too many arguments

In my case the problem is that when the build.git's configure passes the
arguments to the internal configure, the build_alias="foo" CFLAGS="bar"
values are parsed together and because of this config.sub reports it as
an error.

A trivial workaround is to sed -i "s|'build_alias=<chost>' ||" bin/setup
(the value is passed already using --build).

i.e. the quotes are missing, and I don't know why. Ideas?

Are you sure? config.log may miss the quotes but look at bin/setup, that
contains the quotes here.

An other idea was that the quotes are messed up when reusing the
parameters from config.log, but I have the problem with a clean build as
well.

Attachment: pgpEs8DnWfK64.pgp
Description: PGP signature


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.