Re: [liblo] liblo and OS X 10.8

It's actually more twisted than I initially thought.
I tried again on a clean liblo repository and it failed as initially described.
After uninstalling and reinstalling autoconf, automake and libtool, autogen.sh and configure worked again…  So it was not a version problem but something else.  At least I know how to run the autogen.sh script, but something is definitely broken with the tools.


On 2 oct. 2012, at 20:47, Stephen Sinclair <rad...@gm...> wrote:

> Okay, glad to know there is a solution.  I didn't know about removal
> of autotools from OS X.  Not relying on Apple for this stuff is either
> a good thing or a bad thing, I can't decide.  :)
> 
> Anyways, hopefully after 0.27 we can put together a nice brew formula for liblo!
> 
> Steve
> 
> On Mon, Oct 1, 2012 at 9:18 AM, Camille Troillard <ca...@os...> wrote:
>> OK, I found the solution, and its not a problem with liblo:
>> 
>> One thing not totally obvious with brew is that you need to "update" its definitions from time to time.  In fact this is a feature I like, but this time the autotools that were initially installed had the wrong versions.
>> 
>> So, running `brew update' and then `brew upgrade autoconf automake lib tool' fixed the problem and I can build liblo as before.
>> 
>> The page containing the information that led me to the solution was here:
>> https://github.com/mxcl/homebrew/issues/15077
>> 
>> 
>> Cam
>> 
>> 
>> 
>> 
>> On 1 oct. 2012, at 14:30, Camille Troillard <ca...@os...> wrote:
>> 
>>> Hi,
>>> 
>>> For some obscure reason, I can't get autogen.sh to properly run on my new work environment based on OS X 10.8.  It is awfully frustrating knowing that I am very bad at dealing with automake and autoconf issues.
>>> 
>>> Here's the problem: Xcode does not ship autotools anymore so you have to install them by hand.  Best approach is to install them using brew:
>>> $ brew install automake autoconf
>>> 
>>> Then in liblo source directory:
>>> $ ./autogen.sh
>>> 
>>> **Warning**: I am going to run `configure' with no arguments.
>>> If you wish to pass any to it, please specify them on the
>>> `./autogen.sh' command line.
>>> 
>>> processing .
>>> Running libtoolize...
>>> glibtoolize: putting auxiliary files in `.'.
>>> glibtoolize: copying file `./ltmain.sh'
>>> glibtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
>>> glibtoolize: rerunning glibtoolize, to keep the correct libtool macros in-tree.
>>> glibtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
>>> Running aclocal  ...
>>> Running autoheader...
>>> Running automake --gnu  ...
>>> configure.ac:41: error: required file './compile' not found
>>> configure.ac:39: error: required file './config.guess' not found
>>> configure.ac:39: error: required file './config.sub' not found
>>> configure.ac:23: error: required file './install-sh' not found
>>> configure.ac:23: error: required file './missing' not found
>>> examples/Makefile.am: error: required file './depcomp' not found
>>> Running autoconf ...
>>> Running ./configure --enable-maintainer-mode --enable-debug --disable-silent-rules ...
>>> configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.."
>>> 
>>> 
>>> I don't understand why the compile symbolic link and the other files (config.guess, etc.) are not created.  I would tend to suspect a conflict the m4 files shipped with the autotools I installed and this version of OS X.
>>> 
>>> I would really appreciate any kind of help on that matter.
>>> 
>>> 
>>> Thanks!
>>> Cam