Ah, so you want to change autogen.sh (in the future) to use that? I get the same error:
autoreconf: running: libtoolize --copy --force .ibtoolize: AC_CONFIG_MACRO_DIR([m4]) conflicts with ACLOCAL_AMFLAGS=-I m4 autoreconf: libtoolize failed with exit status: 1 -- Tom. On 09/09/12 09:45, Vincent Torri wrote: > On Sun, Sep 9, 2012 at 8:33 AM, Tom Hacohen <tom.haco...@samsung.com> wrote: >> Hey Vincent, >> >> Got any idea? > > i've proposed to launch autoreconf -vif instead of autogen.sh. I'm > still waiting for the answer... > > Vincent > >> >> -- >> Tom. >> >> >> On 06/09/12 17:54, Vincent Torri wrote: >>> >>> On Thu, Sep 6, 2012 at 4:49 PM, Tom Hacohen <tom.haco...@samsung.com> >>> wrote: >>>> >>>> On 06/09/12 17:38, Vincent Torri wrote: >>>>> >>>>> >>>>> On Thu, Sep 6, 2012 at 4:35 PM, Tom Hacohen <tom.haco...@samsung.com> >>>>> wrote: >>>>>> >>>>>> >>>>>> On 06/09/12 17:31, Vincent Torri wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Thu, Sep 6, 2012 at 2:45 PM, Tom Hacohen <tom.haco...@samsung.com> >>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 06/09/12 15:41, Vincent Torri wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Sep 6, 2012 at 1:40 PM, Tom Hacohen >>>>>>>>> <tom.haco...@samsung.com> >>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Look at the line before, it's actually failing the libtoolize call >>>>>>>>>> so >>>>>>>>>> it >>>>>>>>>> tries glibtoolize. I get the same thing, vtorri is supposed to be >>>>>>>>>> working on it. Autofoo is impossible to work with, but I hope >>>>>>>>>> vtorri >>>>>>>>>> will be able to fix it. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> i'll check that, but, iirc, i've just copied an autogen.sh of one >>>>>>>>> efl >>>>>>>>> into obj dir. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> I showed you the error, it's the INCLUDE thingie I had... >>>>>>>> >>>>>>> >>>>>>> what ? glibtoolize is only in autogen.sh : >>>>>>> >>>>>>> echo "Running libtoolize..." ; (libtoolize --copy --automake || >>>>>>> glibtoolize --automake) || exit 1 >>>>>>> >>>>>>> David : if you report a problem, be more precise... >>>>>>> >>>>>> >>>>>> Yeah, as you can see it tries libtoolize, and if that fails, it tries >>>>>> glibtoolize (the "||"). It fails on libtoolize here, although it >>>>>> shouldn't... That's the issue I reported the other day. >>>>> >>>>> >>>>> >>>>> eina's autogen.sh : >>>>> >>>>> echo "Running libtoolize..." ; (libtoolize --copy --automake || >>>>> glibtoolize --automake) || exit 1 >>>>> >>>>> so what's the problem ? The same line works for eina but not for eobj ? >>>> >>>> >>>> >>>> Because libtoolize fails, because of the issues I told you about the >>>> other >>>> day: >>>> .ibtoolize: AC_CONFIG_MACRO_DIR([m4]) conflicts with ACLOCAL_AMFLAGS=-I >>>> m4 >>>> >>>> This causes libtoolize to fail (a bad config in eo) that makes libtoolize >>>> return with an error and thus try to issue glibtoolize because of the >>>> autogen.sh. glibtoolize has nothing to do with it, it's just a >>>> side-effect. >>>> The problem is with the config and the error I pasted above. >>> >>> >>> let's try with embryo, then. It's configure.ac has: >>> >>> AC_CONFIG_MACRO_DIR([m4]) >>> >>> (line 24) and in top level Makefile.am, line 1 : >>> >>> ACLOCAL_AMFLAGS = -I m4 >>> >>> So it works for embryo but not for eobj ? >>> >>> ALL the EFL have AC_CONFIG_MACRO_DIR([m4]) and ACLOCAL_AMFLAGS=-I m4 >>> >>> Vincent >>> >> > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
