[
https://issues.apache.org/jira/browse/AXIS2C-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838347#action_12838347
]
Olivier Mengué commented on AXIS2C-1436:
----------------------------------------
What is the problem?
Is it that Fedora 10 does not have autoconf 2.63, as it is what you committed ?
Is Fedora 10 support a strong requirement for Axis2/C developers (WSO2 ?) ?
If yes I understand that you do not want to commit that. But you could at least
do the autotools upgrade in the Fedora 10 environment and commit that.
And wouldn't it be possible to make your release build in an environment that
the highest version of autotools possible as it would help to avoid problems
for people who have to compile the source code on non Linux platforms where
installing autotools is not an easy solution?
On my side I'm using autoconf 2.64, automake 1.11 and libtool 2.2.6a in an
Ubuntu 9.10 virtual machine. I'm repackaging the source with this upgraded
autotools to make the build work on AIX 5.
> Upgrade autotools
> -----------------
>
> Key: AXIS2C-1436
> URL: https://issues.apache.org/jira/browse/AXIS2C-1436
> Project: Axis2-C
> Issue Type: Improvement
> Components: build system (Unix/Linux)
> Affects Versions: 1.6.0
> Reporter: Olivier Mengué
> Assignee: S.Uthaiyashankar
> Fix For: 1.7.0
>
>
> Upgrading autotools on the machine used to make releases would probably help
> to fix issues on non-Linux systems such as AIX.
> Here is a script to upgrade all configure.ac:
> for d in $( find . -name configure.ac | sed 's@/[^/]*$@@' )
> do
> echo autoreconf/autoupdate for $d
> ( cd $d ; autoreconf -i && autoupdate ) || exit 1
> done
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
