[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-source-highlight] Support for Google Protocol Buffers protobuf

From: Lorenzo Bettini
Subject: Re: [Help-source-highlight] Support for Google Protocol Buffers protobuf language (.proto)
Date: Tue, 09 Mar 2010 22:55:23 +0100
User-agent: Thunderbird (X11/20090817)

Dear Joel

don't excuse yourself, it was my fault to leave around which is quite old and I haven't been using it for years myself: I'll remove it asap :)

and many thanks for your patch with proto language definition file. By the way, many compliments for the way you wrote the patch: together with all modifications to the configuration files and with the test for the test suite, well done indeed :)


Joel Smith wrote:
Sorry for replying to myself, but I figured out what was preventing my builds.

Joel Smith wrote:
Additionally, I wanted to mention that the code checked out of git wouldn't build for me until I added the following two lines to the


I'm not sure if there is something wrong with my installation or what, but without those, autoconf didn't expand macros properly and the resulting configure script wouldn't run.
Since I wrote my original message to the list, I noticed the docs say the following:

When you compile the sources that you get from the git repository, before running the |configure| and |make| commands, for the first time, you must run the command:

     autoreconf -i
This will run the autotools commands in the correct order, and also copy possibly missing files. You should have installed recent versions of |automake|, |autoconf| and |libtool| in order for this to succeed.

After checking out from git, I saw that there was an, so I just ran that, and ended up in the state where the boost m4 files weren't being included. Running "autoreconf -i" instead, as the docs say, works fine. So perhaps the script ought to be removed, or changed to run autoreconf instead so people won't end up in the same boat as me.

And in case anyone in the future is searching for the solution, perhaps the search engines will lead them to this message if I provide the error message I was getting:

./configure: line 15756: syntax error near unexpected token `1.33.1'
./configure: line 15756: `AX_BOOST_BASE(1.33.1)'

Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134     (GNU/Linux User # 158233)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]