build problems

Showing 1-14 of 14 messages
build problems Peter Kümmel 6/9/12 1:11 AM
Hi,

I tried to build on Linux Mint 13 (should be the same as Ubuntu 12.04)
but have problems with the autotools.
Here is what I did:

$ git checkout -f
$ rm ../.gitignore
$ git clean -df
Removing aclocal.m4
Removing autom4te.cache/
Removing config.log
Removing configure
$ autoconf
configure.ac:12: error: possibly undefined macro: AM_INIT_AUTOMAKE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:17: error: possibly undefined macro: AM_PROG_LIBTOOL
configure.ac:24: error: possibly undefined macro: AC_CXX_COMPILE_STDCXX_0X
configure.ac:85: error: possibly undefined macro: AM_CONDITIONAL
$ aclocal
$ autoconf
configure.ac:24: error: possibly undefined macro: AC_CXX_COMPILE_STDCXX_0X
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
$ aclocal
$ ./configure
./configure: line 2484: syntax error near unexpected token `folly-config.h,'
./configure: line 2484: `AX_PREFIX_CONFIG_H(folly-config.h, folly, config.h)'
$

./configure: line 2484:
AX_PREFIX_CONFIG_H(folly-config.h, folly, config.h)


Any ideas what's going wrong?

Many thanks,
Peter
Re: build problems Stefano Dobrilla 6/10/12 1:27 PM
$ aclocal
$ autoconf
configure.ac:24: error: possibly undefined macro: AC_CXX_COMPILE_STDCXX_0X
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.


The same problem on Mac OS X 10.7.

Any suggestion?

Thanks,
Stefano




Re: [folly] build problems Tudor Bosman 6/10/12 2:12 PM
Hi Peter,

On Sat, Jun 9, 2012 at 1:11 AM, Peter Kümmel <synth...@gmx.net> wrote:
configure.ac:12: error: possibly undefined macro: AM_INIT_AUTOMAKE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:17: error: possibly undefined macro: AM_PROG_LIBTOOL
configure.ac:24: error: possibly undefined macro: AC_CXX_COMPILE_STDCXX_0X
configure.ac:85: error: possibly undefined macro: AM_CONDITIONAL

These seem to indicate that automake isn't installed.

-Tudor.
 
Re: [folly] Re: build problems Tudor Bosman 6/10/12 2:15 PM
Hi Stefano,

On Sun, Jun 10, 2012 at 1:27 PM, Stefano Dobrilla <stefano....@gmail.com> wrote:
$ aclocal
$ autoconf
configure.ac:24: error: possibly undefined macro: AC_CXX_COMPILE_STDCXX_0X
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.


The same problem on Mac OS X 10.7.

folly probably won't work on Mac OS X 10.7.  Mac OS X ships with clang, not gcc (and it shipped an ancient version of gcc before Lion).  Folly currently requires gcc 4.6.2 or higher, and I'm sure there are Linux-isms in there as well -- getting rid of Linux-isms would not be horribly hard, though.

We'll look at other platforms (32-bit versions of Linux, Mac OS X, and FreeBSD 9, in this order) in the near future, but if you (or anyone else) want to sink some time into this before we get to it, we'd welcome any patches.

-Tudor.
Re: [folly] build problems Peter Kümmel 6/10/12 2:26 PM
> On Sat, Jun 9, 2012 at 1:11 AM, Peter Kümmel <synth...@gmx.net <mailto:synth...@gmx.net>> wrote:
>
>     configure.ac:12 <http://configure.ac:12>: error: possibly undefined macro: AM_INIT_AUTOMAKE
>            If this token and others are legitimate, please use m4_pattern_allow.
>            See the Autoconf documentation.
>     configure.ac:17 <http://configure.ac:17>: error: possibly undefined macro: AM_PROG_LIBTOOL
>     configure.ac:24 <http://configure.ac:24>: error: possibly undefined macro: AC_CXX_COMPILE_STDCXX_0X
>     configure.ac:85 <http://configure.ac:85>: error: possibly undefined macro: AM_CONDITIONAL
>
>
> These seem to indicate that automake isn't installed.

Hi Tudor,

all dependencies are installed,

$ automake --version
automake (GNU automake) 1.11.3

and it could generate 'configure' after a aclocal call.

But I've installed gflags and glog from source
and not the packages. Could this be the reason?

Peter
Re: [folly] build problems Tudor Bosman 6/10/12 2:34 PM

On Sun, Jun 10, 2012 at 2:26 PM, Peter Kümmel <synth...@gmx.net> wrote:

These seem to indicate that automake isn't installed.

Hi Tudor,

all dependencies are installed,

$ automake --version
automake (GNU automake) 1.11.3

Indeed. My mistake; the AM_* macros were found during aclocal, so the only missing ones are AC_CXX_COMPILE_STDCXX_0X and AX_PREFIX_CONFIG_H.  A web search shows that both come from autoconf-archive, http://www.gnu.org/software/autoconf-archive/

(While you're at it, please confirm that the version of gcc that you have is at least 4.6.2, as folly won't build without it)

-Tudor.

Re: [folly] build problems Peter Kümmel 6/10/12 3:06 PM
On 10.06.2012 23:34, Tudor Bosman wrote:
>
> Indeed. My mistake; the AM_* macros were found during aclocal, so the only missing ones are AC_CXX_COMPILE_STDCXX_0X and
> AX_PREFIX_CONFIG_H.  A web search shows that both come from autoconf-archive, http://www.gnu.org/software/autoconf-archive/
>

Thanks, I didn't thought it is a missing package.

But it's not straight forward, therefore:

     https://github.com/facebook/folly/pull/10


> (While you're at it, please confirm that the version of gcc that you have is at least 4.6.2, as folly won't build
> without it)

$ gcc --version
gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3


Do you know if it works with clang/trunk?

Peter
Re: [folly] build problems Andrew Gallagher 6/10/12 3:07 PM
Does just "autoreconf -i" work?

Andrew  
Re: [folly] build problems Tudor Bosman 6/10/12 9:47 PM
On Sun, Jun 10, 2012 at 3:06 PM, Peter Kümmel <synth...@gmx.net> wrote:

Do you know if it works with clang/trunk?

I don't think so, but feel free to give it a shot. Patches welcome :)

-Tudor.

Re: build problems Hao Liu 6/12/12 4:14 AM
Hi

Same problem here, on Fedora 17, with gcc 4.7.0, automake 1.11.3.

I installed every package required through yum, don't know where the problem is. I have same output as you while building folly.

Hugo
Re: [folly] Re: build problems Peter Kümmel 6/12/12 5:47 AM
On 12.06.2012 13:14, Hao Liu wrote:
> Hi
>
> Same problem here, on Fedora 17, with gcc 4.7.0, automake 1.11.3.
>
> I installed every package required through yum, don't know where the problem is. I have same output as you while
> building folly.
>
> Hugo

Try 'autoreconf --install'.

Peter
Re: [folly] Re: build problems Hao Liu 6/23/12 4:41 AM
It works now, thanks Peter!

When I compile it under Fedora 17 with gcc 4.7, it shows me two errors in max() & min(), in FBString.cpp and Benchmark.cpp if I remember it right. It's between size_t and long unsigned int.

I have to cast the argument type manually so that it can compile successfully.

Hao
Re: [folly] Re: build problems Tudor Bosman 6/23/12 8:33 AM
Is this on a 32- or 64-bit Linux installation?

Folly currently only works on 64-bit.

-Tudor.

--

Re: [folly] Re: build problems Hao Liu 6/24/12 9:46 PM
Oh, forgot to mention that. 

It's 32 bit linux.

Hao


On Saturday, June 23, 2012 11:33:51 PM UTC+8, Tudor Bosman wrote:
Is this on a 32- or 64-bit Linux installation?

Folly currently only works on 64-bit.

-Tudor.


On Sat, Jun 23, 2012 at 4:41 AM, Hao Liu wrote:
It works now, thanks Peter!

When I compile it under Fedora 17 with gcc 4.7, it shows me two errors in max() & min(), in FBString.cpp and Benchmark.cpp if I remember it right. It's between size_t and long unsigned int.

I have to cast the argument type manually so that it can compile successfully.

Hao

On Tuesday, June 12, 2012 8:47:24 PM UTC+8, Peter Kümmel wrote:
On 12.06.2012 13:14, Hao Liu wrote:
> Hi
>
> Same problem here, on Fedora 17, with gcc 4.7.0, automake 1.11.3.
>
> I installed every package required through yum, don't know where the problem is. I have same output as you while
> building folly.
>
> Hugo

Try 'autoreconf --install'.

Peter

--