On Thu, Jan 07, 2010 at 09:53:21AM +0100, Jaroslav Hajek wrote:
> On Thu, Jan 7, 2010 at 9:17 AM, Thomas Weber
> <[email protected]> wrote:
> > Hi,
> >
> > I'm currently faced with a (non-standard) bug report against octgrp in
> > Debian[1]. It fails to build on the sh4 architecture. This boils down to
> > an old autoconf used to build the configure script and should be fixed
> > from autoconf 2.63 onwards.
> >
> > However, octgrp ships it's own configure script in the archive. Is it
> > okay if I update it (I will need to change configure.in as well):
> >
> > $ autoreconf
> > configure.in:45: error: AC_SUBST: `FPICFLAG CPICFLAG' is not a valid
> > shell variable name
> > configure.in:45: the top level
> > autom4te: /usr/bin/m4 failed with exit status: 1
> > aclocal: /usr/bin/autom4te failed with exit status: 1
> > autoreconf: aclocal failed with exit status: 1
> >
> > Or should just the configure.in stay in the archive?
> >
>
> I believe configure must be present in the tarball that is used for
> installation; otherwise, Octave will fail to install because it
> doesn't run autoconf. I've put it into SVN as well because then it's
> easier to install straight from SVN.
Thanks, but my question still stands: are you fine with me putting a
newer configure script into SVN?
Thomas
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev
