liblo-devel Mailing List for LibLO

On Tue, Nov 3, 2015 at 3:23 PM, Paul Keyes <sps...@gm...> wrote:
> ./autogen.sh CXX=dontuse CC=gcc-4.4.7  gives me the following errors:
>
> configure.ac:1: error: Autoconf version 2.69 or higher is required
> checking for gcc... gcc-4.4.7
> checking whether the C compiler works... no
> configure: error: C compiler cannot create executables
>
> If I don't set CC=gcc-4.4.7 it seem to work, but the make gives me:
>
> WARNING: 'aclocal-1.13' is missing on your system.
>          You should only need it if you modified 'acinclude.m4' or
>          'configure.ac' or m4 files included by 'configure.ac'.
>          The 'aclocal' program is part of the GNU Automake package:
>          <" rel="nofollow">http://www.gnu.org/software/automake>
>          It also requires GNU Autoconf, GNU m4 and Perl in order to run:
>          <" rel="nofollow">http://www.gnu.org/software/autoconf>
>          <" rel="nofollow">http://www.gnu.org/software/m4/>
>          <" rel="nofollow">http://www.perl.org/>
> make: *** [aclocal.m4] Error 127
>
> Again, I have aclocal-1.11 installed.

Try changing the first list of configure.ac to match your version of
autoconf, and see if it still works.  For reference, it was set to
2.68 in liblo release 0.26.

As a more general rule, you may need to change things to work with
whatever version of tools you have installed on that system.  Since
none of us have your computer in front of us, it may be hard to help
with every little change that is needed.

Anyway, as IOhannes points out, you can just run configure with those
arguments, if you are working from a tarball release.  No need to run
autoconf/automake yourself.

I can guarantee that it is possible for some version of liblo to be
compiled for that operating system, however, so if you have further
questions, don't hesitate.

regards,
Steve

On 11/03/2015 03:23 PM, Paul Keyes wrote:
> ./autogen.sh CXX=dontuse CC=gcc-4.4.7  gives me the following errors:

since the sole purpose of calling autogen.sh with the arguments is to
pass on the arguments to configure, how about running configure directly?

   ./configure CXX=dontuse

what autogen.sh usually does is to re-build the configure script.
since you don't need that (and it fails anyhow), you shouldn't do it.

fdmasr
IOhannes

On 11/3/2015 6:23 AM, Paul Keyes wrote:
>
> Again, I have aclocal-1.11 installed.

Any reason you haven't installed 1.13?

z!

./autogen.sh CXX=dontuse CC=gcc-4.4.7  gives me the following errors:

configure.ac:1: error: Autoconf version 2.69 or higher is required
checking for gcc... gcc-4.4.7
checking whether the C compiler works... no
configure: error: C compiler cannot create executables

If I don't set CC=gcc-4.4.7 it seem to work, but the make gives me:

WARNING: 'aclocal-1.13' is missing on your system.
         You should only need it if you modified 'acinclude.m4' or
         'configure.ac' or m4 files included by 'configure.ac'.
         The 'aclocal' program is part of the GNU Automake package:
         <" rel="nofollow">http://www.gnu.org/software/automake>
         It also requires GNU Autoconf, GNU m4 and Perl in order to run:
         <" rel="nofollow">http://www.gnu.org/software/autoconf>
         <" rel="nofollow">http://www.gnu.org/software/m4/>
         <" rel="nofollow">http://www.perl.org/>
make: *** [aclocal.m4] Error 127

Again, I have aclocal-1.11 installed.





On Tue, Nov 3, 2015 at 7:38 AM, Stephen Sinclair <rad...@gm...>
wrote:

> On Tue, Nov 3, 2015 at 12:57 AM, Paul Keyes <sps...@gm...> wrote:
> > So I tried to set CXX=ooo with version 0.28 and i get the same errors. I
> > tried version 0.26 and i get the following errors:
> > error: lo/lo_cpp.h: No such file or directory
> > error: 'lo' has not been declared
> >
> > Any suggestions? Thanks
>
> Hi, I find that unlikely since lo/lo_cpp.h did not exist in version
> 0.26.  The C++ wrapper was introduced in version 0.28rc.  Are you sure
> you're building against a clean directory?
>
> I don't know if it's comparable to your RH4.4 install, but I just did
> the following on my Ubuntu 14.04 box:
>
> $ apt-get install gcc-4.4
> $ cd projects/liblo
> $ git checkout 0.28
> $ git clean -xfd .
> $ ./autogen.sh CXX=dontuse CC=gcc-4.4
> $ make
>
> The software built without errors.  I also got no errors when I did,
>
> $ apt-get install g++-4.4
> $ git clean -xfd .
> $ ./autogen.sh CXX=dontuse CC=gcc-4.4
> $ make
>
> During the configure stage, it reports,
>
> checking whether C++11 lambdas are supported... no
>
> So perhaps my initial inclination that this was related to the problem
> is incorrect.
>
> Steve
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>

On Tue, Nov 3, 2015 at 12:57 AM, Paul Keyes <sps...@gm...> wrote:
> So I tried to set CXX=ooo with version 0.28 and i get the same errors. I
> tried version 0.26 and i get the following errors:
> error: lo/lo_cpp.h: No such file or directory
> error: 'lo' has not been declared
>
> Any suggestions? Thanks

Hi, I find that unlikely since lo/lo_cpp.h did not exist in version
0.26.  The C++ wrapper was introduced in version 0.28rc.  Are you sure
you're building against a clean directory?

I don't know if it's comparable to your RH4.4 install, but I just did
the following on my Ubuntu 14.04 box:

$ apt-get install gcc-4.4
$ cd projects/liblo
$ git checkout 0.28
$ git clean -xfd .
$ ./autogen.sh CXX=dontuse CC=gcc-4.4
$ make

The software built without errors.  I also got no errors when I did,

$ apt-get install g++-4.4
$ git clean -xfd .
$ ./autogen.sh CXX=dontuse CC=gcc-4.4
$ make

During the configure stage, it reports,

checking whether C++11 lambdas are supported... no

So perhaps my initial inclination that this was related to the problem
is incorrect.

Steve

> you could try ./autogen.sh --disable-tests --disable-examples
> and feel lucky (i think all the .cpp are tests and examples)
>
i remember it helped in some cases (similar error messages).
maybe that doesn't help for your case with gcc (GCC) 4.4.7 20120313 (Red
Hat 4.4.7-16).

you could try
./autogen.sh --disable-tests --disable-examples
and feel lucky
(i think all the .cpp are tests and examples)

On Tue, November 3, 2015 00:57, Paul Keyes wrote:
> So I tried to set CXX=ooo with version 0.28 and i get the same errors. I
> tried version 0.26 and i get the following errors: error: lo/lo_cpp.h: No
> such file or directory error: 'lo' has not been declared
>
>
> Any suggestions? Thanks
>

So I tried to set CXX=ooo with version 0.28 and i get the same errors. I
tried version 0.26 and i get the following errors:
error: lo/lo_cpp.h: No such file or directory
error: 'lo' has not been declared

Any suggestions? Thanks

On Mon, Nov 2, 2015 at 5:05 PM, Stephen Sinclair <rad...@gm...>
wrote:

> Yes of course!  Just set CXX to something, as I suggested. If it doesn't
> work, try an old version of liblo. (0.26 for example.)
> On Nov 2, 2015 21:47, "Paul Keyes" <sps...@gm...> wrote:
>
>> I'm using the newest gcc in the repository for my OS. I can't upgrade the
>> OS. I could maybe upgrade gcc without doing that but it would probably be a
>> lot of work and maybe not even possible...
>> Do you think I can get liblo working with this gcc?
>>
>> On Mon, Nov 2, 2015 at 4:32 PM, Stephen Sinclair <rad...@gm...>
>> wrote:
>>
>>> Yes, sorry for the typo!
>>> It's really an argument to configure, of course, since arguments to
>>> autogen.sh get passed on to configure. It will make the C++ tests fail,
>>> causing the C++ components to be excluded from the build.
>>>
>>> It was sort of an explicit but admittedly lazy decision to not handle
>>> this case so elegantly. Mostly i figured people would not be compiling
>>> brand new versions of liblo on old systems. Is there a reason you are using
>>> an outdated gcc? I'm just genuinely curious. I could fix configure to take
>>> this into account in future releases.
>>>
>>> Steve
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> liblo-devel mailing list
>>> lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> liblo-devel mailing list
>> lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>>
>>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>
>

Yes of course!  Just set CXX to something, as I suggested. If it doesn't
work, try an old version of liblo. (0.26 for example.)
On Nov 2, 2015 21:47, "Paul Keyes" <sps...@gm...> wrote:

> I'm using the newest gcc in the repository for my OS. I can't upgrade the
> OS. I could maybe upgrade gcc without doing that but it would probably be a
> lot of work and maybe not even possible...
> Do you think I can get liblo working with this gcc?
>
> On Mon, Nov 2, 2015 at 4:32 PM, Stephen Sinclair <rad...@gm...>
> wrote:
>
>> Yes, sorry for the typo!
>> It's really an argument to configure, of course, since arguments to
>> autogen.sh get passed on to configure. It will make the C++ tests fail,
>> causing the C++ components to be excluded from the build.
>>
>> It was sort of an explicit but admittedly lazy decision to not handle
>> this case so elegantly. Mostly i figured people would not be compiling
>> brand new versions of liblo on old systems. Is there a reason you are using
>> an outdated gcc? I'm just genuinely curious. I could fix configure to take
>> this into account in future releases.
>>
>> Steve
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> liblo-devel mailing list
>> lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>
>

I'm using the newest gcc in the repository for my OS. I can't upgrade the
OS. I could maybe upgrade gcc without doing that but it would probably be a
lot of work and maybe not even possible...
Do you think I can get liblo working with this gcc?

On Mon, Nov 2, 2015 at 4:32 PM, Stephen Sinclair <rad...@gm...>
wrote:

> Yes, sorry for the typo!
> It's really an argument to configure, of course, since arguments to
> autogen.sh get passed on to configure. It will make the C++ tests fail,
> causing the C++ components to be excluded from the build.
>
> It was sort of an explicit but admittedly lazy decision to not handle this
> case so elegantly. Mostly i figured people would not be compiling brand new
> versions of liblo on old systems. Is there a reason you are using an
> outdated gcc? I'm just genuinely curious. I could fix configure to take
> this into account in future releases.
>
> Steve
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>
>

Yes, sorry for the typo!
It's really an argument to configure, of course, since arguments to
autogen.sh get passed on to configure. It will make the C++ tests fail,
causing the C++ components to be excluded from the build.

It was sort of an explicit but admittedly lazy decision to not handle this
case so elegantly. Mostly i figured people would not be compiling brand new
versions of liblo on old systems. Is there a reason you are using an
outdated gcc? I'm just genuinely curious. I could fix configure to take
this into account in future releases.

Steve

./autogen.sh CXX=dontuse seems to work, but I get this when trying to make:

WARNING: 'aclocal-1.13' is missing on your system.

I have aclocal-1.11 installed.

Cheers

On Mon, Nov 2, 2015 at 1:22 PM, Paul Keyes <sps...@gm...> wrote:

> Did you mean
>
> ./autogen.sh CXX=dontuse
>
> I don't see autoget.sh
>
> On Mon, Nov 2, 2015 at 1:01 PM, Stephen Sinclair <rad...@gm...>
> wrote:
>
>> Hi,
>>
>> The C++ bindings require C++11 support.  The configure program tries
>> to detect whether the C++ compiler has C++11 support, so you should
>> see the following during configure:
>>
>> checking whether C++11 lambdas are supported... no
>>
>> If it says "yes", then it is a case of the compiler having C++11
>> support but doesn't actually completely support it.  I didn't put a
>> lot of effort into detect these cases, but it could be fixed with more
>> tests.  In the meantime, you can just disable C++ support explicitly,
>> but giving configure a non-sense value for CXX. I realize this isn't a
>> super clean solution but it should solve your problem:
>>
>> ./autoget.sh CXX=dontuse
>>
>>
>> Steve
>>
>>
>> On Mon, Nov 2, 2015 at 5:33 PM, Paul Keyes <sps...@gm...> wrote:
>> > Hi, I'm having trouble compiling liblo-0.28. Compiler version and
>> errors are
>> > blow. Any help is greatly appreciated!
>> >
>> > gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
>> > g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
>> >
>> > Errors:
>> > /usr/local/include/lo/lo_cpp.h:457: error: 'template<class H> const
>> typename
>> > std::enable_if<std::is_same::value, void>::type
>> > lo::Server::add_method(lo::string_type, lo::string_type, H&&)' cannot be
>> > overloaded
>> > /usr/local/include/lo/lo_cpp.h:454: error: with 'template<class H> const
>> > typename std::enable_if<std::is_same::value, void>::type
>> > lo::Server::add_method(lo::string_type, lo::string_type, H&&)'
>> > /usr/local/include/lo/lo_cpp.h:457: error: 'template<class H> const
>> typename
>> > std::enable_if<std::is_same::value, void>::type
>> > lo::Server::add_method(lo::string_type, lo::string_type, H&&)' cannot be
>> > overloaded
>> >
>> > ...followed by many more errors.
>> >
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > liblo-devel mailing list
>> > lib...@li...
>> > https://lists.sourceforge.net/lists/listinfo/liblo-devel
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> liblo-devel mailing list
>> lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>>
>
>

Did you mean

./autogen.sh CXX=dontuse

I don't see autoget.sh

On Mon, Nov 2, 2015 at 1:01 PM, Stephen Sinclair <rad...@gm...>
wrote:

> Hi,
>
> The C++ bindings require C++11 support.  The configure program tries
> to detect whether the C++ compiler has C++11 support, so you should
> see the following during configure:
>
> checking whether C++11 lambdas are supported... no
>
> If it says "yes", then it is a case of the compiler having C++11
> support but doesn't actually completely support it.  I didn't put a
> lot of effort into detect these cases, but it could be fixed with more
> tests.  In the meantime, you can just disable C++ support explicitly,
> but giving configure a non-sense value for CXX. I realize this isn't a
> super clean solution but it should solve your problem:
>
> ./autoget.sh CXX=dontuse
>
>
> Steve
>
>
> On Mon, Nov 2, 2015 at 5:33 PM, Paul Keyes <sps...@gm...> wrote:
> > Hi, I'm having trouble compiling liblo-0.28. Compiler version and errors
> are
> > blow. Any help is greatly appreciated!
> >
> > gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
> > g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
> >
> > Errors:
> > /usr/local/include/lo/lo_cpp.h:457: error: 'template<class H> const
> typename
> > std::enable_if<std::is_same::value, void>::type
> > lo::Server::add_method(lo::string_type, lo::string_type, H&&)' cannot be
> > overloaded
> > /usr/local/include/lo/lo_cpp.h:454: error: with 'template<class H> const
> > typename std::enable_if<std::is_same::value, void>::type
> > lo::Server::add_method(lo::string_type, lo::string_type, H&&)'
> > /usr/local/include/lo/lo_cpp.h:457: error: 'template<class H> const
> typename
> > std::enable_if<std::is_same::value, void>::type
> > lo::Server::add_method(lo::string_type, lo::string_type, H&&)' cannot be
> > overloaded
> >
> > ...followed by many more errors.
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> >
> > _______________________________________________
> > liblo-devel mailing list
> > lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/liblo-devel
> >
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>

Hi,

The C++ bindings require C++11 support.  The configure program tries
to detect whether the C++ compiler has C++11 support, so you should
see the following during configure:

checking whether C++11 lambdas are supported... no

If it says "yes", then it is a case of the compiler having C++11
support but doesn't actually completely support it.  I didn't put a
lot of effort into detect these cases, but it could be fixed with more
tests.  In the meantime, you can just disable C++ support explicitly,
but giving configure a non-sense value for CXX. I realize this isn't a
super clean solution but it should solve your problem:

./autoget.sh CXX=dontuse


Steve


On Mon, Nov 2, 2015 at 5:33 PM, Paul Keyes <sps...@gm...> wrote:
> Hi, I'm having trouble compiling liblo-0.28. Compiler version and errors are
> blow. Any help is greatly appreciated!
>
> gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
> g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
>
> Errors:
> /usr/local/include/lo/lo_cpp.h:457: error: 'template<class H> const typename
> std::enable_if<std::is_same::value, void>::type
> lo::Server::add_method(lo::string_type, lo::string_type, H&&)' cannot be
> overloaded
> /usr/local/include/lo/lo_cpp.h:454: error: with 'template<class H> const
> typename std::enable_if<std::is_same::value, void>::type
> lo::Server::add_method(lo::string_type, lo::string_type, H&&)'
> /usr/local/include/lo/lo_cpp.h:457: error: 'template<class H> const typename
> std::enable_if<std::is_same::value, void>::type
> lo::Server::add_method(lo::string_type, lo::string_type, H&&)' cannot be
> overloaded
>
> ...followed by many more errors.
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>

Hi, I'm having trouble compiling liblo-0.28. Compiler version and errors
are blow. Any help is greatly appreciated!

gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)

Errors:
/usr/local/include/lo/lo_cpp.h:457: error: 'template<class H> const
typename std::enable_if<std::is_same::value, void>::type
lo::Server::add_method(lo::string_type, lo::string_type, H&&)' cannot be
overloaded
/usr/local/include/lo/lo_cpp.h:454: error: with 'template<class H> const
typename std::enable_if<std::is_same::value, void>::type
lo::Server::add_method(lo::string_type, lo::string_type, H&&)'
/usr/local/include/lo/lo_cpp.h:457: error: 'template<class H> const
typename std::enable_if<std::is_same::value, void>::type
lo::Server::add_method(lo::string_type, lo::string_type, H&&)' cannot be
overloaded

...followed by many more errors.

Hi All, I'm getting the following compile errors. Any help greatly
appreciated.

Compiler versions are:
gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)

Errors:
/usr/local/include/lo/lo_cpp.h:457: error: 'template<class H> const
typename std::enable_if<std::is_same::value, void>::type
lo::Server::add_method(lo::string_type, lo::string_type, H&&)' cannot be
overloaded
/usr/local/include/lo/lo_cpp.h:454: error: with 'template<class H> const
typename std::enable_if<std::is_same::value, void>::type
lo::Server::add_method(lo::string_type, lo::string_type, H&&)'
/usr/local/include/lo/lo_cpp.h:457: error: 'template<class H> const
typename std::enable_if<std::is_same::value, void>::type
lo::Server::add_method(lo::string_type, lo::string_type, H&&)' cannot be
overloaded

... followed by many more lines