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


On Wed, Jul 10, 2013 at 02:42:44PM +0200, Petr Mladek wrote:

I get the following error when compiling master on linux:

It is related to the commit
http://cgit.freedesktop.org/libreoffice/core/commit/?id=f220c3913a167b0d9702aca2b623839abe8665f1

I am not that familiar with bison. Well, it seems that the flag "%
glr-parser" in connectivity/source/parse/sqlbison.y changed a lot. Most
code parts of the sqlbison.y are included in the generated sqlbison.hxx.

sqlbison.hxx apparently is (very?) different depending on Bison
version. I have bison 2.5 and it works for me, not even a warning. I
have a report that bison 2.4.1 also manages fine. I presume you have
bison 2.3?

It might help to remove the aEmptyString definition in
connectivity/source/parse/sqlflex.l but I am not sure.

This breaks it on my machine, because sqlbison.hxx does not contain
that aEmptyString... but renaming it should work. I committed that.

Our MacOS X tinderbox also has *another* *error* which is less obvious
to fix.

The whole new code looks strange now. There are many newcompiler
warnings,

Yes, they disappear with newer bison. Apparently "newer bison", where
"newer" means "from December 2008 or later" is a significant issue for
at least one platform (MacOS X).

What solution would you suggest, please?

The discussion is ongoing in the other thread.

-- 
Lionel

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.