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


Hmmm, that looks like a quoting problem with the $CPP variable.

What does your $CPP variable look like?

On Mon, Nov 21, 2011 at 13:07, Winfried Donkers
<W.Donkers@dci-electronics.nl> wrote:
Excellent. Feel free to ask for help if you get stuck setting it up.

-- Noel Grandin

.autogen.sh succeeded, now make give a strange error:
...
configure: creating ./config.status
./configure: line 8411: test: too many arguments
./configure: line 8411: test: too many arguments
./configure: line 8411: test: too many arguments
./configure: line 8411: test: too many arguments
./configure: line 8411: test: too many arguments
./configure: line 8411: test: too many arguments
configure: error: could not make ./config.status
...
line 8411 of configure is 'if test -z "$CPP"; then', whicj looks perfectly ok to me
config.status has not been altered (size is 0bytes, timestamp is before starting time of make)

Also, considering the vast amount of messages added to bug 36555 by Lionel Elie Mamane and Alex 
Thurgood, it may be wiser to abandon my attempts to build LibreOffice and continue with easy 
hacks on my Linus machine? Or do you still wish me to have a running windows machine for testing 
this (and possible other) bugs/patches?

Winfried
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


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.