[ 
https://issues.apache.org/jira/browse/LOGCXX-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210831#comment-15210831
 ] 

Thorsten Schöning commented on LOGCXX-433:
------------------------------------------

I got the following output with only the patch applied:

{CODE}
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
{CODE}

This looks to me like the tool is suggesting another folder for the macros 
currently placed in the root dir of the project, which should be save if it is 
suggested and if it suggest to use the same tech like from the path. During the 
build some more *.m4 files are generated in the root folder and my test showed 
that with AC_CONFIG_MACRO_DIR those are placed in the provided dir as well. So 
I think it shoudl be save to move our m4 macros to another folder outside the 
root dir to make that a little less messy. Instead of using m4 directly, I 
preferred putting the m4 folder into the src dir, because simply most of the 
other sources are placed there, e.g. already support files for ANT.

> Autoconf 2.69 needs 'ACLOCAL_AMFLAGS= -I .'
> -------------------------------------------
>
>                 Key: LOGCXX-433
>                 URL: https://issues.apache.org/jira/browse/LOGCXX-433
>             Project: Log4cxx
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 0.11.0
>         Environment: openSUSE 13.1 / 64Bit, autoconf 2.69
>            Reporter: Christian Ehrlicher
>            Assignee: Thorsten Schöning
>            Priority: Minor
>             Fix For: 0.11.0
>
>         Attachments: logcxx-433.patch
>
>
> When trying to build current svn HEAD I need to add
> 'ACLOCAL_AMFLAGS= -I .' to Makefile.am - otherwise configure (created with 
> 'autoreconf -i --install' doesn't find find_apr.m4 and find_apu.m4



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to